October 2009 - users-list

[MonetDB-users] Optimizer exception in Aug09-SP1
by Alex Bo. 06 Oct '09

06 Oct '09

Hi, I got this exception while running a not so special query: ExecuteReader failed: !SQLException:optimizer: 'multiplex' should be the last !SQLException:optimizer: 'deadcode' should be used at least once !SQLException:optimizer: pipeline set to 'inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex' I haven't been able to reproduce it since. What does it mean? Is it something to worry about? Thanks. -- View this message in context: http://www.nabble.com/Optimizer-exception-in-Aug09-SP1-tp25736590p25736590.… Sent from the monetdb-users mailing list archive at Nabble.com.

3 2

[MonetDB-users] gdk_single_user
by Matthew Jones 06 Oct '09

06 Oct '09

Is this option still required to keep the database from corrupting itself on shutdown? I've also noticed when running in this mode that I see a lot of duplicate tables and when attempting to drop a table it doesn't disappear from my table list... what gives? 73, Matthew W. Jones (KI4ZIB) http://matburt.net

2 2

[MonetDB-users] Unique constraint on char column
by Guillaume Theoret 06 Oct '09

06 Oct '09

Is the unique constraint supposed to work on a char column? I wanted to add a constraint such that a combination of two columns (date_added and hash_key) was always unique but although the constraint seems to have been added successfully, it seemingly has no effect: (please disregard timer measurements, I'm doing lots of concurrent inserts at the same time) sql>CREATE TABLE test.keytest ( more> date_added int NOT NULL, more> hash_key char(32) NOT NULL, more> dimension1 int NOT NULL, more> dimension2 int NOT NULL, more> metric1 int NOT NULL, more> metric2 int NOT NULL, more> more> CONSTRAINT key_test UNIQUE (hash_key,date_added) more>); Operation successful Timer 1855.919 msec 0 rows sql> 0 tuples Timer 368.076 msec 0 rows sql>select * from test.keytest; 0 tuples Timer 294.551 msec 0 rows sql>insert into test.keytest (date_added, hash_key, dimension1, dimension2, metric1, metric2) VALUES (1, a, 1, 1, 2, 2); !SELECT: identifier 'a' unknown 0 tuples Timer 22.811 msec 0 rows sql>insert into test.keytest (date_added, hash_key, dimension1, dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2); Rows affected 1 Timer 12.126 msec 0 rows sql>insert into test.keytest (date_added, hash_key, dimension1, dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2); Rows affected 1 Timer 18.345 msec 0 rows sql>select * from test.keytest; select * from test.keytest; +------------+----------------------------------+------------+------------+---------+---------+ | date_added | hash_key | dimension1 | dimension2 | metric1 | metric2 | +============+==================================+============+============+=========+=========+ | 1 | a | 1 | 1 | 2 | 2 | | 1 | a | 1 | 1 | 2 | 2 | +------------+----------------------------------+------------+------------+---------+---------+ 2 tuples Timer 1.997 msec 2 rows sql>CREATE UNIQUE INDEX unique_key_test ON test.keytest (date_added, hash_key); Operation successful Timer 25.904 msec 2 rows sql>insert into test.keytest (date_added, hash_key, dimension1, dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2); Rows affected 1 Timer 78.637 msec 2 rows sql>insert into test.keytest (date_added, hash_key, dimension1, dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2); Rows affected 1 Timer 31.788 msec 2 rows sql>select * from test.keytest; select * from test.keytest; +------------+----------------------------------+------------+------------+---------+---------+ | date_added | hash_key | dimension1 | dimension2 | metric1 | metric2 | +============+==================================+============+============+=========+=========+ | 1 | a | 1 | 1 | 2 | 2 | | 1 | a | 1 | 1 | 2 | 2 | | 1 | a | 1 | 1 | 2 | 2 | | 1 | a | 1 | 1 | 2 | 2 | +------------+----------------------------------+------------+------------+---------+---------+ 4 tuples Timer 18.083 msec 4 rows I can't seem to get monetdb to refuse to add the rows. I then tried: sql>CREATE TABLE test.keytest2 ( more> date_added int NOT NULL, more> key int NOT NULL, more> dimension1 int NOT NULL, more> dimension2 int NOT NULL, more> metric1 int NOT NULL, more> metric2 int NOT NULL, more> more> CONSTRAINT key_test2 UNIQUE (key,date_added) more>); Operation successful Timer 167.384 msec 0 rows sql>insert into test.keytest2 (date_added, key, dimension1, dimension2, metric1, metric2) VALUES (1, 1, 1, 1, 2, 2); Rows affected 1 Timer 1.693 msec 0 rows sql>insert into test.keytest2 (date_added, key, dimension1, dimension2, metric1, metric2) VALUES (1, 1, 1, 1, 2, 2); !SQLException:assert:INSERT INTO: UNIQUE constraint 'keytest2.key_test2' violated 0 tuples Timer 66.634 msec 0 rows sql>select * from test.keytest2; select * from test.keytest2; +------------+-------+------------+------------+---------+---------+ | date_added | key | dimension1 | dimension2 | metric1 | metric2 | +============+=======+============+============+=========+=========+ | 1 | 1 | 1 | 1 | 2 | 2 | +------------+-------+------------+------------+---------+---------+ 1 tuple Timer 140.707 msec 1 rows Which worked as expected. Is this a bug or is it by design? Thanks, Guillaume

2 2

[MonetDB-users] segmentation fault at startup
by Matthew Jones 06 Oct '09

06 Oct '09

After a spontaneous reboot while the database was idle, it now won't come back up due to a segmentation fault.... is there any way to recover from this? # /usr/bin/mserver5 --config=/etc/monetdb5.conf --dbname=qa-test-1 --dbinit="include sql;" --set monet_daemon=yes --set mapi_open=false --set mapi_autosense=true --set mapi_port=50001 --set monet_vault_key=/var/MonetDB5/dbfarm/qa-test-1/.vaultkey # MonetDB server v5.14.0, based on kernel v1.32.0 # Serving database 'qa-test-1', using 8 threads # Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked # Copyright (c) 1993-July 2008 CWI. # Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved # Visit http://monetdb.cwi.nl/ for further information # Listening for connection requests on mapi:monetdb://127.0.0.1:50002/ # MonetDB/SQL module v2.32.0 loaded Segmentation fault Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fe8592906e0 (LWP 5538)] 0x00007fe8582faa29 in strPut () from /usr/lib/libbat.so.1 (gdb) (gdb) bt #0 0x00007fe8582faa29 in strPut () from /usr/lib/libbat.so.1 #1 0x00007fe858259288 in BATappend () from /usr/lib/libbat.so.1 #2 0x00007fe858571e83 in ?? () from /usr/lib/libbat.so.1 #3 0x00007fe8585729e9 in ?? () from /usr/lib/libbat.so.1 #4 0x00007fe858573dc4 in logger_create () from /usr/lib/libbat.so.1 #5 0x00007fe84744f0c5 in ?? () from /usr/lib/MonetDB5/lib/lib_sql.so #6 0x00007fe847449245 in store_init () from /usr/lib/MonetDB5/lib/lib_sql.so #7 0x00007fe847415346 in mvc_init () from /usr/lib/MonetDB5/lib/lib_sql.so #8 0x00007fe8473d6b9b in SQLprelude () from /usr/lib/MonetDB5/lib/lib_sql.so #9 0x00007fe858d80ef1 in ?? () from /usr/lib/libmonetdb5.so.5 #10 0x00007fe858d8c471 in runMAL () from /usr/lib/libmonetdb5.so.5 #11 0x00007fe858d7aa74 in MALengine () from /usr/lib/libmonetdb5.so.5 #12 0x00007fe858d797b1 in callString () from /usr/lib/libmonetdb5.so.5 #13 0x0000000000402976 in main () 73, Matthew W. Jones (KI4ZIB) http://matburt.net

1 0

[MonetDB-users] 'deadcode' should be used at least once
by Guillaume Theoret 06 Oct '09

06 Oct '09

I was doing concurrent inserts (just running monetdb_query('INSERT INTO ...'); in a loop) with 2 workers. After ~172,000 inserts on the first worker I got this message: Error: SQLException:optimizer: 'deadcode' should be used at least once !SQLException:optimizer: pipeline set to 'inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex' And at the same time on the second worker I got: Error: SQLException:optimizer: 'multiplex' should be the last !SQLException:optimizer: 'deadcode' should be used at least once !SQLException:optimizer: pipeline set to 'inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex' Does anyone know what this might mean? At first I thought I may have made too big of a transaction but it seems monetdb runs in autocommit mode by default. Thanks, Guillaume

1 0

[MonetDB-users] loading RDF data in MonetDB
by Medha Atre 06 Oct '09

06 Oct '09

Hi, I intend to use MonetDB for some of my experimental work using RDF data. I was wondering if there is an easy way to load RDF data (in NTriples format) in MonetDB making use of the column-wise vertical partitioning of the RDF data, based on properties/predicates in the RDF data. Some pointers or help regarding this is much appreciated. I am sorry if this is not the correct forum to post this message. Thanks. Medha

2 1

[MonetDB-users] Download link broken?
by Guillaume Theoret 05 Oct '09

05 Oct '09

Hi, I tried to download the linux version of MonetDB/SQL on this page http://monetdb.cwi.nl/projects/monetdb//Download/ but both the lzma and bz2 links 404. I instead followed the Ubuntu instructions available here: http://monetdb.cwi.nl/downloads/Ubuntu/ and it worked fine but I thought I'd point out the above. Thanks, Guillaume

3 4

[MonetDB-users] Query time problem
by Chris Baros 05 Oct '09

05 Oct '09

Hi I am using Monetdb xquery in a Windows platform, I want to measure the timing in some queries. But every time I run a query, I see that the "Query time" increases. If I restart the server, then again at the first time the Query time is normall, and by the second and after, increases again.. Do you have any ideas whats the problem? _________________________________________________________________ Show them the way! Add maps and directions to your party invites. http://www.microsoft.com/windows/windowslive/products/events.aspx

2 2

[MonetDB-users] current_timestamp in windows is wrong
by Alex Bo. 04 Oct '09

04 Oct '09

Hi, I am running Feb09 and Aug09 on Windows. If I use CURRENT_TIMESTAMP / LOCALTIME / LOCALTIMESTAMP then I get the correct date but the time is 2 hours early. (I am running from time zone UTC +02:00) Is this a bug? -- View this message in context: http://www.nabble.com/current_timestamp-in-windows-is-wrong-tp25736255p2573… Sent from the monetdb-users mailing list archive at Nabble.com.

1 0