You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Date: 2018-01-03 16:44:18 +0100
From: @mlkersten
To: clients devs <>
Version: -- development
Last updated: 2018-08-31 13:23:28 +0200
Comment 26055
Date: 2018-01-03 16:44:18 +0100
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:57.0) Gecko/20100101 Firefox/57.0
Build Identifier:
When using the TRACE option, then the performance counter is shown twice the same value, derived from the generation of the trace table rendering.
It should report two different numbers corresponding to the actual query execution and the trace table rendering.
Date: 2018-01-03 16:44:18 +0100
From: @mlkersten
To: clients devs <>
Version: -- development
Last updated: 2018-08-31 13:23:28 +0200
Comment 26055
Date: 2018-01-03 16:44:18 +0100
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:57.0) Gecko/20100101 Firefox/57.0
Build Identifier:
When using the TRACE option, then the performance counter is shown twice the same value, derived from the generation of the trace table rendering.
It should report two different numbers corresponding to the actual query execution and the trace table rendering.
Reproducible: Always
Comment 26528
Date: 2018-06-29 10:50:43 +0200
From: MonetDB Mercurial Repository <>
Changeset bb0d2665ca06 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=bb0d2665ca06
Changeset description:
The text was updated successfully, but these errors were encountered: