Victor, could you please file a bug report about this one? Either the documentation or the respective code (or both) is (are) not good. Thanks! Stefan On Tue, Oct 18, 2011 at 06:02:37PM +0200, Viktor Rosenfeld wrote:
Hi,
I get errors, when I try to use the query history feature as described here: http://www.monetdb.org/Documentation/Cookbooks/SQLrecipies/History
After history is set to true, I get the following error message every time I execute a query:
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)
This only stops if I set history back to false.
I'm using the latest MonetDB 11.5.3 on OS X 10.6.
Below is an example session.
Cheers, Viktor
-----8< sample session >8-----
$ mclient -d demo -u monetdb password: Welcome to mclient, the MonetDB/SQL interactive terminal (Aug2011-SP1) Database: MonetDB v11.5.3, 'demo' Type \q to quit, \? for a list of available commands auto commit mode: on sql>set history=true; 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>select * from queryHistory; 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>set history=false; 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>select * from queryHistory; +---------+----------------------------+---------+-----------------------------+-------+----------+ | id | defined | name | query | parse | optimize | +=========+============================+=========+=============================+=======+==========+ | 1035769 | 2011-10-18 15:51:36.000000 | monetdb | select 1; | 236 | 208 | | 1035885 | 2011-10-18 15:51:47.000000 | monetdb | select * from queryhistory; | 300 | 860 | | 1036047 | 2011-10-18 15:51:50.000000 | monetdb | set history=false; | 130 | 466 | +---------+----------------------------+---------+-----------------------------+-------+----------+ 3 tuples (1.613ms) sql>
------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2d-oct _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
-- | Stefan.Manegold @ CWI.nl | DB Architectures (INS1) | | http://CWI.nl/~manegold/ | Science Park 123 (L321) | | Tel.: +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |