- developers-list - monetdb.org

Announcement: Release Candidate for Jan2014 Release
by Sjoerd Mullender 15 Jan '14

15 Jan '14

The MonetDB team at CWI/MonetDB BV is pleased to announce a release candidate for the upcoming Jan2014 feature release. Many things have changed in this release compared to the previous (Feb2013) release (that's why it took so long). For a smooth upgrade I would urge you to try out this release candidate and to provide feedback on our bug tracker (http://bugs.monetdb.org) The release candidate can be found at http://dev.monetdb.org/downloads/testing. -- Sjoerd Mullender

1 0

Segmentation fault on a query from table expression
by Alexander Shestakov 14 Jan '14

14 Jan '14

Hi, I am running MonetDB Database Server Toolkit v1.1 (Feb2013-SP6) , I have a table DailyData defined as follows. create table DailyData ( sym varchar(32), businessdate date, closePrice float, adjustedClosePrice float, openingPrice float, accVol float, unique(businessdate, sym) ); I make the following query. with dd as (select * from DailyData where businessdate > '2013-06-01'), r as (select t.businessdate, t.sym, 1 - t.adjustedcloseprice / y.adjustedcloseprice as ret from dd t left outer join dd y on t.businessdate = y.businessdate + (interval '1' day) and t.sym = y.sym), v as (select sym, stddev_samp(ret) as volatility from r group by sym) select * from v where v.sym like '%.L' limit 100; It results in a segmentation fault: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f5f17023700 (LWP 25178)] 0x0000003ee9327a9a in __strcmp_sse42 () from /lib64/libc.so.6 (gdb) where #0 0x0000003ee9327a9a in __strcmp_sse42 () from /lib64/libc.so.6 #1 0x00007f6f2d4ef6f8 in rel_use_index (changes=<value optimized out>, sql=0x7f5f08005470, rel=0x7f5f0850aa70) at rel_optimizer.c:4829 #2 0x00007f6f2d4ea225 in rewrite (sql=0x7f5f08005470, rel=0x7f5f0850aa70, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6106 #3 0x00007f6f2d4ea2bc in rewrite (sql=0x7f5f08005470, rel=0x7f5f0850cb40, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6093 #4 0x00007f6f2d4ea2bc in rewrite (sql=0x7f5f08005470, rel=0x7f5f0850ec30, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6093 #5 0x00007f6f2d4ea2bc in rewrite (sql=0x7f5f08005470, rel=0x7f5f0850ef50, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6093 #6 0x00007f6f2d4ea2bc in rewrite (sql=0x7f5f08005470, rel=0x7f5f08512a90, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6093 #7 0x00007f6f2d4ea2bc in rewrite (sql=0x7f5f08005470, rel=0x7f5f0850feb0, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6093 #8 0x00007f6f2d4ea2bc in rewrite (sql=0x7f5f08005470, rel=0x7f5f085101c0, rewriter=0x7f6f2d4ef610 <rel_use_index>, has_changes=0x7f5f17022cac) at rel_optimizer.c:6093 #9 0x00007f6f2d4ecf58 in _rel_optimizer (sql=0x7f5f08005470, rel=<value optimized out>, level=0) at rel_optimizer.c:6278 #10 0x00007f6f2d484369 in sql_symbol2relation (c=0x7f5f08005470, sym=<value optimized out>) at sql.mx:1755 #11 0x00007f6f2d454b2f in SQLparser (c=0x7f6f2df49308) at sql_scenario.c:1708 #12 0x00007f6f352ecdd3 in runPhase (c=0x7f6f2df49308) at mal_scenario.c:522 #13 runScenarioBody (c=0x7f6f2df49308) at mal_scenario.c:558 #14 0x00007f6f352ecf1f in runScenario (c=0x7f6f2df49308) at mal_scenario.c:586 #15 0x00007f6f352ed778 in MSserveClient (dummy=0x7f6f2df49308) at mal_session.c:446 #16 0x0000003ee9a07851 in start_thread () from /lib64/libpthread.so.0 #17 0x0000003ee92e890d in clone () from /lib64/libc.so.6 Apparently at rel_optimizer.c:4829 strcmp(exp_relname(nre) returns NULL which is not checked. If I rewrite the query in the following way it works if not very fast. with r as (select t.businessdate, t.sym, 1 - t.adjustedcloseprice / y.adjustedcloseprice as ret from DailyData t left outer join DailyData y on t.businessdate = y.businessdate + (interval '1' day) and t.sym = y.sym where t.businessdate > '2013-06-01'), v as (select sym, stddev_samp(ret) as volatility from r group by sym) select * from v where v.sym like '%.L' limit 100; Regards, Alex Shestakov.

2 2

user defnined function problem
by Niall Rooney 07 Jan '14

07 Jan '14

Hello, I am making the following adjustment to the user defined function template files . I am using MonetDB-11.15.15 built from source on Ubuntu 12.04. I have added to the following files in the ./sql/backends/monet5/UDF directory as shown: 80_udf.sql create function sumProb(prob1 double, prob2 double) returns double external name udf.sumProb; udf.mal module udf; command sumProb(prob1:dbl,prob2:dbl):dbl address UDFSumProb comment "sum two probabilities"; udf.c str UDFSumProb(dbl * res, dbl * prob1, dbl * prob2) { *res = *prob1 + *prob2; return MAL_SUCCEED; } udf.h udf_export str UDFSumProb(dbl * res, dbl * prob1, dbl * prob2); I did a configure/make/make install and tried the following call in mclient: declare a, b,c double; set a= 0.1; set b= 0.2; select c=jsdistance(a,b); and get the error: TypeException:user.s2_1[8]:'udf.sumprob' undefined in: _12:any := udf.sumprob(_8:dbl, _11:dbl) program contains errors

3 6

Create a table with FLOAT type
by Adnan Agbaria 05 Jan '14

05 Jan '14

Hello, I use MonetDB in Ubuntu. When I create a table with FLOAT type, MonetDB created it as DOUBLE type. Why does MonetDB decide to change FLOAT to DOUBLE? How can I fix this?

2 1

Segmentation faultin sql_optimizer
by Shestakov, Alex 02 Jan '14

02 Jan '14

Hi, I have a segmentation fault when running an SQL query against a specific table. I can execute queries like "select count(*) from <TABLE>" but the server crashes when I do "select * from <TABLE> where businessdate = '2013-12-18' limit 100". MonetDB version: MonetDB Database Server Toolkit v1.1 (Feb2013-SP5) Stack trace: #0 0x00007f7cf2987eb1 in GDKfilepath (path=0x7f6e44f0db5d "", dir=0x7f7ceb4c51d4 "bat", name=0x0, ext=0x0) at gdk_storage.c:51 #1 0x00007f7ceb3fbbd3 in BATlocation (fnme=0x7f6e44f0fbe0, bid=<value optimized out>) at sql_optimizer.c:77 #2 0x00007f7ceb3fc59a in SQLgetStatistics (c=0x7f7cebed6308) at sql_optimizer.c:160 #3 addQueryToCache (c=0x7f7cebed6308) at sql_optimizer.c:295 #4 0x00007f7ceb3fb7ed in backend_dumpproc (be=0x7f6e3809d5f0, c=0x7f7cebed6308, cq=0x7f6e383d4090, s=0x7f6e3837bd20) at sql_gencode.c:2431 #5 0x00007f7ceb3e2067 in SQLparser (c=0x7f7cebed6308) at sql_scenario.c:1755 #6 0x00007f7cf2f35b63 in runPhase (c=0x7f7cebed6308) at mal_scenario.c:522 #7 runScenarioBody (c=0x7f7cebed6308) at mal_scenario.c:558 #8 0x00007f7cf2f35caf in runScenario (c=0x7f7cebed6308) at mal_scenario.c:586 #9 0x00007f7cf2f36508 in MSserveClient (dummy=0x7f7cebed6308) at mal_session.c:446 #10 0x0000003ee9a07851 in start_thread () from /lib64/libpthread.so.0 #11 0x0000003ee92e890d in clone () from /lib64/libc.so.6 The problem is that it tries to de-reference null pointer 'name'. The pointer is calculated in BATLocation as (b->T->heap.filename ? b->T->heap.filename: b->H->heap.filename). The column in question has type real so as far as I understand there is no heap file for it. I don't know if heap.filename should contain NULL or something else. Regards, Alex Shestakov. ________________________________ This email and any files transmitted with it contain confidential and proprietary information and is solely for the use of the intended recipient. If you are not the intended recipient please return the email to the sender and delete it from your computer and you must not use, disclose, distribute, copy, print or rely on this email or its contents. This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. Any comments or statements made herein do not necessarily reflect those of GSA Capital. GSA Capital Partners LLP is authorised and regulated by the Financial Conduct Authority and is registered in England and Wales at Stratton House, 5 Stratton Street, London W1J 8LA, number OC309261. GSA Capital Services Limited is registered in England and Wales at the same address, number 5320529.

1 1

about the monetdb jdbc problem
by 少湖 30 Dec '13

30 Dec '13

An exception(see the bottom stack) was thrown when I use the JDBC driver(monetdb-jdbc-2.10.jar, MonetDB Database Server v1.7 (Feb2013-SP4) ) on linux(Linux *** 2.6.18-164.11.1.el5 #1 SMP Wed Jan 6 13:26:04 EST 2010 x86_64 x86_64 x86_64 GNU/Linux), but with the same code no exceptions are thrown on windows7 When DML SQL is executed by preparestatement(or Statement) I Just got the exception on linux, can anyone tell me what happened. Exception in thread "main" java.lang.IndexOutOfBoundsException at java.nio.StringCharBuffer.subSequence(StringCharBuffer.java:92) at nl.cwi.monetdb.mcl.parser.StartOfHeaderParser.getNextAsString(StartOfHeaderP arser.java:146) at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnectio n.java:2394) at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnectio n.java:2284) at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508) at nl.cwi.monetdb.jdbc.MonetStatement.internalBatch(MonetStatement.java:261) at nl.cwi.monetdb.jdbc.MonetStatement.executeBatch(MonetStatement.java:230) at MonetdbBenchmark.insert(MonetdbBenchmark.java:50) at MonetdbBenchmark.main(MonetdbBenchmark.java:19)

2 2

Skyline Queries and MonetDB
by Stephen P. Morgan 17 Dec '13

17 Dec '13

Hello, Has anyone out there done any work on extending MonetDB to support skyline queries natively? I may be interested in work along these lines but I'd rather not reinvent the wheel. If anyone has preceded me, I'd love to hear about your work. Thanks, Steve Morgan

1 0

Query Time
by Sebastian Kielmann 12 Dec '13

12 Dec '13

HI, We are using monetdb for some statistical analysis. The queries are very fast (0.2 sec), but some times (not regularly) the queries get peeks of up to 32 sec for the same query. CPU and RAM don't change and are way higher than actually needed. Does any one have this same situation? Any idea what could be doing this? Best regards and thanks to any help. sebastian

3 5

Re: MonetDB: Jan2014 - Merge with Jan2014 branch.
by Stefan Manegold 10 Dec '13

10 Dec '13

> Changeset: 1a2184860d3e for MonetDB > URL: http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1a2184860d3e [...] > Branch: Jan2014 > Log Message: > > Merge with Jan2014 branch. ^^^^^^^ SORRY --- shoudl of course read "Merge with Feb2013 branch." S. -- | Stefan.Manegold(a)CWI.nl | DB Architectures (DA) | | www.CWI.nl/~manegold/ | Science Park 123 (L321) | | +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |

1 0

Announcement: New Feb2013-SP6 Bugfix release of MonetDB suite
by Sjoerd Mullender 03 Dec '13

03 Dec '13

The MonetDB team at CWI/MonetDB BV is pleased to announce the Feb2013-SP6 bugfix release of the MonetDB suite of programs. More information about MonetDB can be found on our website at <http://www.monetdb.org/>. For details on this release, please see the release notes at <http://www.monetdb.org/Downloads/ReleaseNotes>. As usual, the download location is <http://dev.monetdb.org/downloads/>. Feb 2013-SP6 bugfix release MonetDB5 Server * Fixed a possible buffer overflow in the COPY INTO code. * Fixed a problem that when the server is using all available threads for a query, it was not possible to attach another client and have it execute even the smallest query. This is fixed by creating extra threads for each client entering the fray at the cost of having more threads that execute queries. But at least there is guaranteed progress for all clients (modulo the operating system scheduler). See bug #3258. Merovingian * monetdbd(1) now refuses to startup if it cannot read the properties from the dbfarm, bug #3398 Client Package * mclient: Fixed a bug where the -H option only worked if the readline history file already existed. Now we properly create and use the history file. * ODBC: Fixed interpretation SQL_C_SLONG/SQL_C_ULONG/SQL_C_LONG to refer to a 32 bit integer always (i.e. "int" on 64 bit architectures despite the name and the Microsoft documentation). This seems to be the consensus. * ODBC: Fixed transaction level: MonetDB only supports the highest level (SQL_TXN_SERIALIZABLE), so setting the transaction level can be accepted and ignored. MonetDB Common * Stopped using the deprecated sbrk() system call. * Fixed a problem when reverse sorting a sorted column. * Fixed bugs that deal with problems that could possibly occur when transactions are aborted and the server is restarted. See bug #3243. * A bug was fixed in the handling of grouped aggregates when all values in a group are null. See bug #3388. SQL * Fixed a bug where the server at some point stopped saving compiled queries in the SQL query cache. Bug Fixes * 3243: Segmentation fault (possible data corruption) after clean shutdown * 3258: Scheduling issues * 3368: BAT sortedness info ignored on ORDER BY and TOPN * 3374: UNIQUE constraint does not set tkey property on the corresponding BAT * 3382: Response to PREPARE emtpy if query contains a LIMIT * 3385: Simple query fails with 'identifier not found' * 3387: mclient does not properly double quote schema names when using autofill tab * 3388: case statement in "order by" clause doesn't work when used together with "group by" * 3389: median function with "group by" - SIGSEGV * 3392: ODBC datatype conversion for INTEGER not working properly * 3394: "Cannot find column type" error in temporary tables in functions * 3395: error occurred during a query: "'CASE WHEN" sentence * 3396: Improper UDF expansion * 3397: Error in ODBC-Driver when using Prepared Statements * 3398: Cannot stop monetdbd after erroneously starting an uninitialized dbfarm

1 0