Date: 2020-04-16 07:43:35 +0200
From: @mlkersten
To: MonetDB5 devs <>
Version: -- development
CC: @yzchang

Last updated: 2020-06-03 16:58:53 +0200

Comment 27663

Date: 2020-04-16 07:43:35 +0200
From: @mlkersten

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:74.0) Gecko/20100101 Firefox/74.0
Build Identifier:

The purpose of the idle timestamp in the client record is to detect connections that haven't been used for a long time.

The property is not properly set.

Reproducible: Always

Steps to Reproduce:

start two independent mclient sessions
one should see that the other one is idle using
select * from sys.sessions()

no additional test file included

Comment 27664

Date: 2020-04-16 10:06:21 +0200
From: @yzchang

I tried the new sys.sessions() in Jun2020 yesterday, it actually did show me that the other other connection is idle since :

sql>select * from sessions();
+-----------+----------+----------------------------+----------------------------+--------------+----------------+--------------+-------------+-------------+
| sessionid | username | login | idle | optimizer | sessiontimeout | querytimeout | workerlimit | memorylimit |
+===========+==========+============================+============================+==============+================+==============+=============+=============+
| 0 | monetdb | 2020-04-15 21:30:21.000000 | 2020-04-15 21:30:23.000000 | default_pipe | 0 | 0 | 0 | 0 |
| 1 | monetdb | 2020-04-15 21:30:30.000000 | null | default_pipe | 0 | 0 | 0 | 0 |
+-----------+----------+----------------------------+----------------------------+--------------+----------------+--------------+-------------+-------------+
2 tuples

Comment 27665

Date: 2020-04-16 10:10:57 +0200
From: @mlkersten

In the June branch indeed it was set in the sql.execute() code.
It should (also) be managed lower, because MAL sessions also exist.