Date: 2012-08-23 17:32:35 +0200
From: Christian Braun <>
To: clients devs <>
Version: 11.11.7 (Jul2012-SP1)

Last updated: 2012-09-21 11:51:25 +0200

Comment 17649

Date: 2012-08-23 17:32:35 +0200
From: Christian Braun <>

User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build Identifier:

Welcome to mclient, the MonetDB/SQL interactive terminal (Jul2012-SP1)
Database: MonetDB v11.11.7 (Jul2012-SP1), 'mapi:monetdb://makalu:50000/db'
Type \q to quit, ? for a list of available commands
auto commit mode: on
sql>select 1;
+--------------+
| single_value |
+==============+
| 1 |
+--------------+
1 tuple (0.468ms)
sql>set history=true;
operation successful (0.482ms)
sql>select 1;
invalid/unknown response from server, ignoring output
? = 0:0 profiler.setFootprintFlag();
? = 0:0 profiler.setMemoryFlag();
? = 0:0 inblock := profiler.getDiskReads();
? = 0:0 oublock := profiler.getDiskWrites();
? = 0:0 xtime := alarm.usec();
(remaining output omitted, use \fraw to examine in detail)
sql>\fraw
sql>select 1;
0:0 profiler.setFootprintFlag();
0:0 profiler.setMemoryFlag();
0:0 inblock := profiler.getDiskReads();
0:0 oublock := profiler.getDiskWrites();
0:0 xtime := alarm.usec();
0:0 X_43 := alarm.usec();
0:0 xtime := calc.-(X_43=17795913294:lng,xtime=2:lng);
0:0 rtime := alarm.usec();
% . table_name
% single_value name
% tinyint type
% 1 length
[ 1 ]
0:0 sql.exportValue(1,".","single_value","tinyint",8,0,6,A0=1:bte,"");
0:0 X_47 := alarm.usec();
0:0 rtime := calc.-(X_47=17795913322:lng,rtime=16:lng);
foot := profiler.getFootprint();
sql>

Reproducible: Always

Comment 17701

Date: 2012-08-24 16:09:19 +0200
From: @sjoerdmullender

Changeset 0901d759538f made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.

For complete details, see http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0901d759538f

Changeset description:

Only print runtimeTiming information when in the (mdb) debugger.
This fixes bugs 3117 and 3145.

Comment 17703

Date: 2012-08-24 16:12:02 +0200
From: @sjoerdmullender

This is essentially the same as bug #3117.
The extra output was timing information for each MAL statement being executed, but it's only really useful for debugging purposes, so I've disabled the output.