- developers-list - monetdb.org

Did not initialise the sql scenario
by Nitul Halder 04 Nov '14

04 Nov '14

I am getting the error (highlighted)when try to start the database demo. I am puzzled . What I can do..Please suggest anyone. Thank you all Nitul 2014-11-04 09:28:26 MSG demo[26510]: arguments: /usr/local/bin/mserver5 --dbpath=/RAID/main_dbfarm/demo --set merovingian_uri=mapi:monetdb://bdserver:50000/demo --set mapi_open=false --set mapi_port=0 --set mapi_usock=/RAID/main_dbfarm/demo/.mapi.sock --set monet_vault_key=/RAID/main_dbfarm/demo/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2014-11-04 09:28:26 MSG demo[26510]: # MonetDB 5 server v11.15.3 "Feb2013-SP1" 2014-11-04 09:28:26 MSG demo[26510]: # Serving database 'demo', using 4 threads 2014-11-04 09:28:26 MSG demo[26510]: # Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked 2014-11-04 09:28:26 MSG demo[26510]: # Found 3.496 GiB available main-memory. 2014-11-04 09:28:26 MSG demo[26510]: # Copyright (c) 1993-July 2008 CWI. 2014-11-04 09:28:26 MSG demo[26510]: # Copyright (c) August 2008-2013 MonetDB B.V., all rights reserved 2014-11-04 09:28:26 MSG demo[26510]: # Visit http://www.monetdb.org/ for further information 2014-11-04 09:28:26 MSG demo[26510]: # Listening for UNIX domain connection requests on mapi:monetdb:///RAID/main_dbfarm/demo/.mapi.sock 2014-11-04 09:28:26 MSG merovingian[26485]: database 'demo' (26510) has exited with exit status 0 2014-11-04 09:28:26 MSG merovingian[26485]: database 'demo' has shut down *2014-11-04 09:28:26 ERR control[26485]: (local): failed to fork mserver: database 'demo' did not initialise the sql scenario*

1 0

Problems with comments in SQL code
by Robert Koch 04 Nov '14

04 Nov '14

SELECT * FROM sys.storage WHERE 1=1 AND "schema" = 'sapsr3' AND "table" = 'dfkkop' ; works in mclient and DBVisualizer (via JDBC) SELECT * FROM sys.storage WHERE 1=1 AND "schema" = 'sapsr3' --AND "table" = 'dfkkop' ; works in mclient, but does not work in DBVisualizer. error message: 11:23:37 [SELECT - 0 row(s), 0.000 secs] 1) [Error Code: 0, SQL State: 42000] syntax error, unexpected $end, expecting SCOLON in: "select. 2) [Error Code: 0, SQL State: 22000] *. 3) [Error Code: 0, SQL State: 22000] from. 4) [Error Code: 0, SQL State: 22000] sys.storage. 5) [Error Code: 0, SQL State: 22000] where 1=1. 6) [Error Code: 0, SQL State: 22000] and "schema" = 'sapsr3'. 7) [Error Code: 0, SQL State: 22000] --AND "table" = 'dfkkop';" ... 1 statement(s) executed, 0 row(s) affected, exec/fetch time: 0.000/0.000 sec [0 successful, 0 warnings, 1 errors] I also noticed this problem (handling comments) in other statements, especially when comments appear before the semicolon. I am not sure, if this is a problem in JDBC driver or DBVisualizer. To see, what is received by monetdb server, I would like to see log files of SQL queries. I found a directory named "/sql_logs/sql", but it consits of 2 files nearly empty. Where can I enable logging?

2 2

Re: MonetDB error while restarting the database
by Ashish Kumar Singh 31 Oct '14

31 Oct '14

Thanks Dimitar, Yes we are restarting the data base and as part of that we are seeing this error. I am more worried about the error below: 2014-10-27 09:01:26 ERR merovingian[23583]: unknown state: 42014-10-27 09:01:26 ERR pbsworksdb[6351]: #GDKexit: killing thread On java client side it says monetdbd: internal error while starting mserver, please refer to the logs Regards, Ashish -----Original Message----- From: Dimitar Nedev <D.G.Nedev(a)cwi.nl> Reply-To: "users-list(a)monetdb.org" <users-list(a)monetdb.org> Date: Monday, 27 October 2014 8:15 pm To: "users-list(a)monetdb.org" <users-list(a)monetdb.org> Subject: Re: MonetDB error while restarting the database >Hi Ashish, > >The exit timeout only tells monetdbd how long should it wait when trying >to gracefully shut down a mserver process. According to the log, the >mserver process was shut down within the limit, since there are no >messages like "timeout of <exittimeout> seconds expired, sending process ><PID> the KILL signal". > >Now, the interesting entry in the log is the control process message: >2014-10-27 09:01:26 MSG control[23583]: (local): stopped database >'pbsworksdb' > >This one would indicate that someone (or something) gracefully stopped >the database using the monetdbd client. Probably with the following >command line call like: 'monetdb stop pbsworksdb'. >Do not be confused by the order of logged events - monetdbd will first >stop the process and later log that the call to stop the a database has >been successful. > >Best regards, >Dimitar > > >> On 2014-Oct-27, at 14:49 , Ashish Kumar Singh >><ashishkumar.singh(a)altair.com> wrote: >> >> Thanks! >> >> >> Appreciate your response so there are few more people getting the same >>error :). >> Any suggestions from dev team on this issue? Can monetdbd exittimeout >>be also in picture for this? >> >> >> Regards, >> Ashish >> >> >> >> From: Pierre-Adrien Coustillas <pcoustillas(a)1g6.biz> >> Date: Monday, 27 October 2014 6:51 pm >> To: "users-list(a)monetdb.org" <users-list(a)monetdb.org> >> Cc: "developers-list(a)monetdb.org" <developers-list(a)monetdb.org>, Ashish >>Singh <ashishkumar.singh(a)altair.com> >> Subject: Re: MonetDB error while restarting the database >> >>> Hello >>> >>> (google translate) >>> >>> I receive this error when there is no specific spacedisk. >>> Monetdb sometimes uses a lot of temporary diskspace (500GBisnormalfor >>>1TBof data), which arereleasedat the end oftreatment or after acrash >>> >>> Error last week : >>> 2014-10-22 22:51:46 MSG merovingian[18865]: sending process 30608 >>>(database 'lemonde') the TERM signal >>> 2014-10-22 22:51:46 ERR merovingian[18865]: unknown state: 42014-10-22 >>>22:51:46 ERR lemonde[30608]: #GDKexit: killing thread >>> >>> Pierre >>> >>> -- >>> 1G6 >>> 52 route de bischwiller >>> 67300 Schiltigheim >>> Société de Services et de Formations en Logiciels Libres >>> http://1g6.biz >>> Tél : 06 64 63 70 35 >>> >>> De: "Ashish Kumar Singh" <ashishkumar.singh(a)altair.com> >>> À: "Ashish Kumar Singh" <ashishkumar.singh(a)altair.com>, >>>users-list(a)monetdb.org >>> Cc: developers-list(a)monetdb.org >>> Envoyé: Lundi 27 Octobre 2014 13:49:19 >>> Objet: Re: MonetDB error while restarting the database >>> >>> Guys, >>> >>> Any help with this will be really helpful for us? >>> >>> >>> >>> Regards, >>> Ashish >>> >>> From: Ashish Singh <ashishkumar.singh(a)altair.com> >>> Date: Monday, 27 October 2014 4:06 pm >>> To: "users-list(a)monetdb.org" <users-list(a)monetdb.org> >>> Subject: MonetDB error while restarting the database >>> >>>> >>>> All, >>>> >>>> >>>> >>>> We are facing a new issue with monetdb where monetdb connections and >>>>process is being killed very frequently. Is this a known issue or any >>>>suggestion in getting more details will be helpful. >>>> >>>> >>>> >>>> Regards, >>>> Ashish >>>> >>>> Mervogian.log: >>>> >>>> >>>> >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: arguments: >>>>/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/bin/mserver5 >>>>--dbpath=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbswor >>>>ksdata/pbsworksdb --set >>>>merovingian_uri=mapi:monetdb://blrec12-vm6:9200/pbsworksdb --set >>>>mapi_open=false --set mapi_port=0 --set >>>>mapi_usock=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsw >>>>orksdata/pbsworksdb/.mapi.sock --set >>>>monet_vault_key=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb >>>>/pbsworksdata/pbsworksdb/.vaultkey --set gdk_nr_threads=4 --set >>>>max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # MonetDB 5 server >>>>v11.17.17 "Jan2014-SP2" >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Serving database >>>>'pbsworksdb', using 4 threads >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Compiled for >>>>x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Found 15.675 GiB >>>>available main-memory. >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Copyright (c) 1993-July >>>>2008 CWI. >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Copyright (c) August >>>>2008-2014 MonetDB B.V., all rights reserved >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Visit >>>>http://www.monetdb.org/ for further information >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Listening for UNIX domain >>>>connection requests on >>>>mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/ >>>>pbsworksdata/pbsworksdb/.mapi.sock >>>> 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # MonetDB/SQL module loaded >>>> 2014-10-27 09:01:00 MSG control[23583]: (local): started 'pbsworksdb' >>>> 2014-10-27 09:01:00 MSG merovingian[23583]: proxying client >>>>localhost.localdomain:53844 for database 'pbsworksdb' to >>>>mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/ >>>>pbsworksdata/pbsworksdb/.mapi.sock?database=pbsworksdb >>>> 2014-10-27 09:01:00 MSG merovingian[23583]: target connection is on >>>>local UNIX domain socket, passing on filedescriptor instead of proxying >>>> 2014-10-27 09:01:26 MSG control[23583]: (local): served status list >>>> 2014-10-27 09:01:26 MSG merovingian[23583]: sending process 6351 >>>>(database 'pbsworksdb') the TERM signal >>>> 2014-10-27 09:01:26 ERR merovingian[23583]: unknown state: >>>>42014-10-27 09:01:26 ERR pbsworksdb[6351]: #GDKexit: killing thread >>>> 2014-10-27 09:01:26 MSG merovingian[23583]: database 'pbsworksdb' >>>>(6351) has exited with exit status 0 >>>> 2014-10-27 09:01:26 MSG merovingian[23583]: database 'pbsworksdb' has >>>>shut down >>>> 2014-10-27 09:01:26 MSG control[23583]: (local): stopped database >>>>'pbsworksdb' >>>> 2014-10-27 09:01:26 MSG control[23583]: (local): served status list >>>> 2014-10-27 09:01:26 MSG merovingian[23583]: starting database >>>>'pbsworksdb', up min/avg/max: 5s/14m/1h, crash average: 0.00 0.00 0.00 >>>>(648-648=0) >>>> 2014-10-27 09:01:27 MSG pbsworksdb[6575]: arguments: >>>>/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/bin/mserver5 >>>>--dbpath=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbswor >>>>ksdata/pbsworksdb --set >>>>merovingian_uri=mapi:monetdb://blrec12-vm6:9200/pbsworksdb --set >>>>mapi_open=false --set mapi_port=0 --set >>>>mapi_usock=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsw >>>>orksdata/pbsworksdb/.mapi.sock --set >>>>monet_vault_key=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb >>>>/pbsworksdata/pbsworksdb/.vaultkey --set gdk_nr_threads=4 --set >>>>max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # MonetDB 5 server >>>>v11.17.17 "Jan2014-SP2" >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Serving database >>>>'pbsworksdb', using 4 threads >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Compiled for >>>>x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Found 15.675 GiB >>>>available main-memory. >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Copyright (c) 1993-July >>>>2008 CWI. >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Copyright (c) August >>>>2008-2014 MonetDB B.V., all rights reserved >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Visit >>>>http://www.monetdb.org/ for further information >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Listening for UNIX domain >>>>connection requests on >>>>mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/ >>>>pbsworksdata/pbsworksdb/.mapi.sock >>>> 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # MonetDB/SQL module loaded >>>> 2014-10-27 09:01:32 MSG merovingian[23583]: proxying client >>>>localhost.localdomain:53853 for database 'pbsworksdb' to >>>>mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/ >>>>pbsworksdata/pbsworksdb/.mapi.sock?database=pbsworksdb >>>> 2014-10-27 09:01:32 MSG merovingian[23583]: target connection is on >>>>local UNIX domain socket, passing on filedescriptor instead of proxying >>>> 2014-10-27 09:01:32 MSG c >>>> >>>> >>>> >>>> >>>> >>> >>> _______________________________________________ >>> users-list mailing list >>> users-list(a)monetdb.org >>> https://www.monetdb.org/mailman/listinfo/users-list >>> >> _______________________________________________ >> developers-list mailing list >> developers-list(a)monetdb.org >> https://www.monetdb.org/mailman/listinfo/developers-list > >_______________________________________________ >users-list mailing list >users-list(a)monetdb.org >https://www.monetdb.org/mailman/listinfo/users-list

3 4

Re: MonetDB error while restarting the database
by Ashish Kumar Singh 27 Oct '14

27 Oct '14

Guys, Any help with this will be really helpful for us? Regards, Ashish From: Ashish Singh <ashishkumar.singh(a)altair.com<mailto:ashishkumar.singh@altair.com>> Date: Monday, 27 October 2014 4:06 pm To: "users-list(a)monetdb.org<mailto:users-list@monetdb.org>" <users-list(a)monetdb.org<mailto:users-list@monetdb.org>> Subject: MonetDB error while restarting the database All, We are facing a new issue with monetdb where monetdb connections and process is being killed very frequently. Is this a known issue or any suggestion in getting more details will be helpful. Regards, Ashish Mervogian.log: 2014-10-27 09:01:00 MSG pbsworksdb[6351]: arguments: /opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/bin/mserver5 --dbpath=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb --set merovingian_uri=mapi:monetdb://blrec12-vm6:9200/pbsworksdb --set mapi_open=false --set mapi_port=0 --set mapi_usock=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.mapi.sock --set monet_vault_key=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # MonetDB 5 server v11.17.17 "Jan2014-SP2" 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Serving database 'pbsworksdb', using 4 threads 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Found 15.675 GiB available main-memory. 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Copyright (c) 1993-July 2008 CWI. 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Visit http://www.monetdb.org/ for further information 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # Listening for UNIX domain connection requests on mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.mapi.sock 2014-10-27 09:01:00 MSG pbsworksdb[6351]: # MonetDB/SQL module loaded 2014-10-27 09:01:00 MSG control[23583]: (local): started 'pbsworksdb' 2014-10-27 09:01:00 MSG merovingian[23583]: proxying client localhost.localdomain:53844 for database 'pbsworksdb' to mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.mapi.sock?database=pbsworksdb 2014-10-27 09:01:00 MSG merovingian[23583]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2014-10-27 09:01:26 MSG control[23583]: (local): served status list 2014-10-27 09:01:26 MSG merovingian[23583]: sending process 6351 (database 'pbsworksdb') the TERM signal 2014-10-27 09:01:26 ERR merovingian[23583]: unknown state: 42014-10-27 09:01:26 ERR pbsworksdb[6351]: #GDKexit: killing thread 2014-10-27 09:01:26 MSG merovingian[23583]: database 'pbsworksdb' (6351) has exited with exit status 0 2014-10-27 09:01:26 MSG merovingian[23583]: database 'pbsworksdb' has shut down 2014-10-27 09:01:26 MSG control[23583]: (local): stopped database 'pbsworksdb' 2014-10-27 09:01:26 MSG control[23583]: (local): served status list 2014-10-27 09:01:26 MSG merovingian[23583]: starting database 'pbsworksdb', up min/avg/max: 5s/14m/1h, crash average: 0.00 0.00 0.00 (648-648=0) 2014-10-27 09:01:27 MSG pbsworksdb[6575]: arguments: /opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/bin/mserver5 --dbpath=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb --set merovingian_uri=mapi:monetdb://blrec12-vm6:9200/pbsworksdb --set mapi_open=false --set mapi_port=0 --set mapi_usock=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.mapi.sock --set monet_vault_key=/opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.vaultkey --set gdk_nr_threads=4 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # MonetDB 5 server v11.17.17 "Jan2014-SP2" 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Serving database 'pbsworksdb', using 4 threads 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Found 15.675 GiB available main-memory. 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Copyright (c) 1993-July 2008 CWI. 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Visit http://www.monetdb.org/ for further information 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # Listening for UNIX domain connection requests on mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.mapi.sock 2014-10-27 09:01:32 MSG pbsworksdb[6575]: # MonetDB/SQL module loaded 2014-10-27 09:01:32 MSG merovingian[23583]: proxying client localhost.localdomain:53853 for database 'pbsworksdb' to mapi:monetdb:///opt/pbsworks/12.4_rc3.1_live/portal/thirdparty/monetdb/pbsworksdata/pbsworksdb/.mapi.sock?database=pbsworksdb 2014-10-27 09:01:32 MSG merovingian[23583]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying 2014-10-27 09:01:32 MSG c

2 2

Re: MonetDB: default - Merge with Oct2014 branch.
by Lefteris 27 Oct '14

27 Oct '14

tab space = 8 for gdk? On Mon, Oct 27, 2014 at 11:02 AM, Sjoerd Mullender <commits(a)monetdb.org> wrote: > Changeset: dfe9b28b23db for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dfe9b28b23db > Modified Files: > gdk/gdk_imprints.c > gdk/gdk_select.c > Branch: default > Log Message: > > Merge with Oct2014 branch. > > > diffs (108 lines): > > diff --git a/gdk/gdk_imprints.c b/gdk/gdk_imprints.c > --- a/gdk/gdk_imprints.c > +++ b/gdk/gdk_imprints.c > @@ -453,12 +453,12 @@ do { > \ > } \ > GETBIN##B(bin,col[i]); \ > mask = IMPSsetBit(B,mask,bin); \ > - if (col[i] != nil) { /* do not count nils */ > \ > - if (!cnt_bins[bin]++) { > \ > - min_bins[bin] = max_bins[bin] = i; > \ > - } else { > \ > - if (col[i] < col[min_bins[bin]]) > min_bins[bin] = i; \ > - if (col[i] > col[max_bins[bin]]) > max_bins[bin] = i; \ > + if (col[i] != nil) { /* do not count nils */ \ > + if (!cnt_bins[bin]++) { \ > + min_bins[bin] = max_bins[bin] = i; \ > + } else { \ > + if (col[i] < col[min_bins[bin]]) > min_bins[bin] = i; \ > + if (col[i] > col[max_bins[bin]]) > max_bins[bin] = i; \ > } \ > } \ > } \ > diff --git a/gdk/gdk_select.c b/gdk/gdk_select.c > --- a/gdk/gdk_select.c > +++ b/gdk/gdk_select.c > @@ -341,27 +341,27 @@ do { > \ > } \ > } while (0) > > -#define checkMINMAX(B) > \ > -do { > \ > - int ii; > \ > - BUN *imp_cnt = (BUN *) (((oid *)imprints->stats)+128); > \ > - imp_min = imp_max = nil; > \ > - for (ii = 0; ii < B; ii++) { > \ > - if ((imp_min == nil) && (imp_cnt[ii])) { > \ > - imp_min = src[((oid *)imprints->stats)[ii]]; > \ > - } > \ > - if ((imp_max == nil) && (imp_cnt[B-1-ii])) { > \ > - imp_max = src[(((oid > *)imprints->stats)+64)[B-1-ii]]; \ > - } > \ > - } > \ > - assert((imp_min != nil) && (imp_max != nil)); > \ > - if (!s && !VIEWtparent(b)) { /* no candidate list and no views*/ > \ > - if ((vl > imp_max || vh < imp_min) || > \ > - (anti && (vl < imp_min && vh > imp_max))) { > \ > - return 0; > \ > - } > \ > - } > \ > -} while (0) > \ > +#define checkMINMAX(B) \ > +do { \ > + int ii; \ > + BUN *imp_cnt = (BUN *) (((oid *)imprints->stats)+128); \ > + imp_min = imp_max = nil; \ > + for (ii = 0; ii < B; ii++) { \ > + if ((imp_min == nil) && (imp_cnt[ii])) { \ > + imp_min = src[((oid *)imprints->stats)[ii]]; \ > + } \ > + if ((imp_max == nil) && (imp_cnt[B-1-ii])) { \ > + imp_max = src[(((oid > *)imprints->stats)+64)[B-1-ii]]; \ > + } \ > + } \ > + assert((imp_min != nil) && (imp_max != nil)); \ > + if (!s && !VIEWtparent(b)) { /* no candidate list and no views*/ \ > + if ((vl > imp_max || vh < imp_min) || \ > + (anti && (vl < imp_min && vh > imp_max))) { \ > + return 0; \ > + } \ > + } \ > +} while (0) > > /* choose number of bits */ > #define bitswitch(CAND,TEST) \ > @@ -374,10 +374,10 @@ do { > \ > s && BATtdense(s) ? "(dense)" : "", \ > anti, #TEST); \ > switch (imprints->bits) { \ > - case 8: checkMINMAX(8); impsmask(CAND,TEST,8); break; > \ > - case 16: checkMINMAX(16); impsmask(CAND,TEST,16); break; > \ > - case 32: checkMINMAX(32); impsmask(CAND,TEST,32); break; > \ > - case 64: checkMINMAX(64); impsmask(CAND,TEST,64); break; > \ > + case 8: checkMINMAX(8); impsmask(CAND,TEST,8); break; \ > + case 16: checkMINMAX(16); impsmask(CAND,TEST,16); break; \ > + case 32: checkMINMAX(32); impsmask(CAND,TEST,32); break; \ > + case 64: checkMINMAX(64); impsmask(CAND,TEST,64); break; \ > default: assert(0); break; \ > } \ > } while (0) > @@ -484,13 +484,13 @@ NAME##_##TYPE (BAT *b, BAT *s, BAT *bn, > { \ > TYPE vl = *(const TYPE *) tl; \ > TYPE vh = *(const TYPE *) th; \ > - TYPE imp_min; > \ > - TYPE imp_max; > \ > - TYPE v; > \ > - TYPE nil = TYPE##_nil; > \ > + TYPE imp_min; \ > + TYPE imp_max; \ > + TYPE v; \ > + TYPE nil = TYPE##_nil; \ > TYPE minval = MINVALUE##TYPE; \ > TYPE maxval = MAXVALUE##TYPE; \ > - const TYPE *src = (const TYPE *) Tloc(b, 0); \ > + const TYPE *src = (const TYPE *) Tloc(b, 0); \ > oid o; \ > BUN w, p = r; \ > BUN pr_off = 0; \ > _______________________________________________ > checkin-list mailing list > checkin-list(a)monetdb.org > https://www.monetdb.org/mailman/listinfo/checkin-list >

2 1

useless WHERE conditions
by gms_xy＠gmx.de 17 Oct '14

17 Oct '14

To have a human-readable SQL code, I am used in following code formatting: SELECT a FROM tbl WHERE 1=1 --<<-- absolutely useless, but nice for formatting AND col1 = 1 AND col2 = 2 AND col3 = 3 Instead of "1=1", some other databases accept "TRUE". When I have multiple OR-conditions, I start with "1=0" or "FALSE". Writing statements this way I noticed long execution times in MonetDB. Omitting the logical where-condition "1=1" results in very fast execution time. So I guess, MonetDB is really checking on every row, if 1=1.

2 1

Partitioning
by Robert Koch 17 Oct '14

17 Oct '14

Are there plans to implement a (manual) SQL-based (multilevel) partitioning? I saw great accelerations with partitions in other databases. Is there any internal/automatic partitioning? If so, can I check it?

2 1

Abort multiline input in mclient
by Robert Koch 17 Oct '14

17 Oct '14

Is there any way to abort multiline input in mclient without leaving mclient? If I press Ctrl-C, mclient exits.

2 1

CASE/WHEN syntax in UPDATE/SET clauses
by Robert Koch 17 Oct '14

17 Oct '14

CASE/WHEN syntax would be useful for UPDATE/SET clauses. Example: UPDATE tbl1 SET col1 = CASE WHEN ... THEN ... ELSE ... END ; I am not sure if this is conform to ANSI SQL. I would find it useful. Today I have to write multiple UPDATE queries with different WHERE conditions.

1 0

Large intermediate results dureing columns update
by Robert Koch 17 Oct '14

17 Oct '14

Given a column defined as bigint (int64) with 1 billion rows. Storage size of this column is 8 GB. Values range in space of int (int32). UPDATE sapsr3.dfkkop SET vkont_int32 = vkont_int64 ; This query takes very long (minutes). During execution the data directory grows by 40 GB (!). I would expect the data cells do be converted an written into the new column directly. Even if MonetDB would materialize the whole source column as "intermediate result", I would expect not to exceed 8 GB for "intermediates" and 4 GB for the target column.

1 0