issue_owner_repo listlengths 2 2 | issue_body stringlengths 0 261k ⌀ | issue_title stringlengths 1 925 | issue_comments_url stringlengths 56 81 | issue_comments_count int64 0 2.5k | issue_created_at stringlengths 20 20 | issue_updated_at stringlengths 20 20 | issue_html_url stringlengths 37 62 | issue_github_id int64 387k 2.46B | issue_number int64 1 127k |
|---|---|---|---|---|---|---|---|---|---|
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-19 10:30:02 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.17.13 (Jan2014-SP1)
CC: @njnes
Last updated: 2015-11-03 10:18:24 +0100
## Comment 21271
Date: 2015-09-19 10:30:02 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:40.0) Gecko/20100101 Firefox/40.0
Build Identifier:
There are now two ways to gather statistics for different purposes. The analyze statement and the analyze command. They should he simplified and unified in the next release.
Reproducible: Always
## Comment 21272
Date: 2015-09-19 16:10:41 +0200
From: @njnes
the analyze statement is the only correct way. When using the analyze command directly, the api should be documented. sys.analyze(samplesize, minmax-only, schemaname, tablename, columnname); And also with on or 2 arguments less, which do a full table/schema at once.
## Comment 21442
Date: 2015-11-03 10:18:24 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| Fix statistics gathering | https://api.github.com/repos/MonetDB/MonetDB/issues/3810/comments | 0 | 2020-11-30T13:17:19Z | 2024-06-27T12:08:47Z | https://github.com/MonetDB/MonetDB/issues/3810 | 753,470,613 | 3,810 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-10 15:20:43 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.21.5 (Jul2015)
CC: @njnes, vijayakrishna55
Last updated: 2016-04-05 12:09:20 +0200
## Comment 21261
Date: 2015-09-10 15:20:43 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
The following query on 24 tables with join conditions in the WHERE clause:
SELECT x20,x47,x38,x18,x10,x22,x37,x3,x63,x8,x30,x43,x54,x9,x21,x25,x2,x61,x55,x32,x52,x29,x50,x12
FROM t9,t20,t63,t54,t32,t22,t52,t25,t47,t29,t12,t18,t10,t21,t43,t37,t2,t61,t55,t3,t38,t50,t30,t8
WHERE b3=a18
AND a25=b38
AND a54=b8
AND a61=b47
AND a43=b29
AND b18=a12
AND b32=a30
AND a22=b43
AND a29=b21
AND a10=b25
AND a12=4
AND b22=a32
AND a20=b55
AND b30=a9
AND a2=b61
AND a38=b52
AND a55=b9
AND a21=b50
AND a37=b54
AND b10=a3
AND a52=b2
AND a50=b63
AND a8=b20
AND a47=b37;
fails to execute and aborts with:
GDK reported error.
HEAPalloc: Insufficient space for HEAP of 400000000 bytes.
Please note: this is only one example query. There are many more and even larger ones (up to 64 tables joined) in select5.test.sql
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5 (MonetDB 5 server v11.21.6) compiled with --enable-assert
2. Start mclient
3. Run SQL script to create the 64 tables with each 10 rows, see: create_64_tables_with_10_rows_each.sql
4. Run SQL query:
SELECT x20,x47,x38,x18,x10,x22,x37,x3,x63,x8,x30,x43,x54,x9,x21,x25,x2,x61,x55,x32,x52,x29,x50,x12
FROM t9,t20,t63,t54,t32,t22,t52,t25,t47,t29,t12,t18,t10,t21,t43,t37,t2,t61,t55,t3,t38,t50,t30,t8
WHERE b3=a18
AND a25=b38
AND a54=b8
AND a61=b47
AND a43=b29
AND b18=a12
AND b32=a30
AND a22=b43
AND a29=b21
AND a10=b25
AND a12=4
AND b22=a32
AND a20=b55
AND b30=a9
AND a2=b61
AND a38=b52
AND a55=b9
AND a21=b50
AND a37=b54
AND b10=a3
AND a52=b2
AND a50=b63
AND a8=b20
AND a47=b37;
5. to cleanup tables, run SQL script: drop_64_tables.sql
### Actual Results:
builtin opt gdk_dbpath = /export/scratch1/dinther/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt embedded_r = true
cmdline opt mapi_port = 41000
cmdline opt gdk_debug = 10
MonetDB 5 server v11.21.6
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs and 128bit integers dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:41000/
MonetDB/GIS module loaded
Start processing logs sql/sql_logs version 52200
Finished processing logs sql/sql_logs
MonetDB/SQL module loaded
MonetDB/R module loaded
> SQL catalog created, loading sql scripts once
bash-4.2$ mclient -p41000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.21.6 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT x20,x47,x38,x18,x10,x22,x37,x3,x63,x8,x30,x43,x54,x9,x21,x25,x2,x61,x55,x32,x52,x29,x50,x12
more> FROM t9,t20,t63,t54,t32,t22,t52,t25,t47,t29,t12,t18,t10,t21,t43,t37,t2,t61,t55,t3,t38,t50,t30,t8
more> WHERE b3=a18
more> AND a25=b38
more> AND a54=b8
more> AND a61=b47
more> AND a43=b29
more> AND b18=a12
more> AND b32=a30
more> AND a22=b43
more> AND a29=b21
more> AND a10=b25
more> AND a12=4
more> AND b22=a32
more> AND a20=b55
more> AND b30=a9
more> AND a2=b61
more> AND a38=b52
more> AND a55=b9
more> AND a21=b50
more> AND a37=b54
more> AND b10=a3
more> AND a52=b2
more> AND a50=b63
more> AND a8=b20
more> AND a47=b37
more>;
GDK reported error.
HEAPalloc: Insufficient space for HEAP of 400000000 bytes.
sql>
### Expected Results:
No HEAPalloc error.
The plan generator (or optimizer) should try to generate joins instead of crossproducts (see plan below).
If crossproducts are not avoidable (so when no equality condition for the table exists) do them after the joins have been completed and not before the joins. It will result in smaller initial intermediates, less large intermediate results and hence faster and potentially successful (no GDK HEAPalloc error) execution.
The plan contains many crossproduct() calls which are computed first and thus produce very large intermediate results and very long execution time or abort with HEAPalloc error.
rel
project (
| join (
| | join (
| | | join (
| | | | join (
| | | | | join (
| | | | | | join (
| | | | | | | join (
| | | | | | | | join (
| | | | | | | | | join (
| | | | | | | | | | join (
| | | | | | | | | | | join (
| | | | | | | | | | | | join (
| | | | | | | | | | | | | join (
| | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | | | | | | crossproduct (
| | | | | | | | | | | | | | | | | | | | | | | join (
| | | | | | | | | | | | | | | | | | | | | | | | table(sys.t18) [ t18.a18 NOT NULL HASHCOL , t18.b18, t18.x18 ] COUNT ,
| | | | | | | | | | | | | | | | | | | | | | | | select (
| | | | | | | | | | | | | | | | | | | | | | | | | table(sys.t12) [ t12.a12 NOT NULL HASHCOL , t12.x12 ] COUNT
| | | | | | | | | | | | | | | | | | | | | | | | ) [ t12.a12 NOT NULL HASHCOL = int "4" ]
| | | | | | | | | | | | | | | | | | | | | | | ) [ t18.b18 = t12.a12 NOT NULL HASHCOL ],
| | | | | | | | | | | | | | | | | | | | | | | table(sys.t22) [ t22.a22 NOT NULL HASHCOL , t22.b22, t22.x22 ] COUNT
| | | | | | | | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | | | | | | | table(sys.t32) [ t32.a32 NOT NULL HASHCOL , t32.b32, t32.x32 ] COUNT
| | | | | | | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | | | | | | table(sys.t54) [ t54.a54 NOT NULL HASHCOL , t54.b54, t54.x54 ] COUNT
| | | | | | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | | | | | table(sys.t63) [ t63.a63 NOT NULL HASHCOL , t63.b63, t63.x63 ] COUNT
| | | | | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | | | | table(sys.t20) [ t20.a20 NOT NULL HASHCOL , t20.b20, t20.x20 ] COUNT
| | | | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | | | table(sys.t9) [ t9.a9 NOT NULL HASHCOL , t9.b9, t9.x9 ] COUNT
| | | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | | table(sys.t52) [ t52.a52 NOT NULL HASHCOL , t52.b52, t52.x52 ] COUNT
| | | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | | table(sys.t25) [ t25.a25 NOT NULL HASHCOL , t25.b25, t25.x25 ] COUNT
| | | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | | table(sys.t47) [ t47.a47 NOT NULL HASHCOL , t47.b47, t47.x47 ] COUNT
| | | | | | | | | | | | | | ) [ ],
| | | | | | | | | | | | | | table(sys.t29) [ t29.a29 NOT NULL HASHCOL , t29.b29, t29.x29 ] COUNT
| | | | | | | | | | | | | ) [ t22.b22 = t32.a32 NOT NULL HASHCOL ],
| | | | | | | | | | | | | table(sys.t55) [ t55.a55 NOT NULL HASHCOL , t55.b55, t55.x55 ] COUNT
| | | | | | | | | | | | ) [ t20.a20 NOT NULL HASHCOL = t55.b55, t55.a55 NOT NULL HASHCOL = t9.b9 ],
| | | | | | | | | | | | table(sys.t43) [ t43.a43 NOT NULL HASHCOL , t43.b43, t43.x43 ] COUNT
| | | | | | | | | | | ) [ t43.a43 NOT NULL HASHCOL = t29.b29, t22.a22 NOT NULL HASHCOL = t43.b43 ],
| | | | | | | | | | | table(sys.t61) [ t61.a61 NOT NULL HASHCOL , t61.b61, t61.x61 ] COUNT
| | | | | | | | | | ) [ t61.a61 NOT NULL HASHCOL = t47.b47 ],
| | | | | | | | | | table(sys.t2) [ t2.a2 NOT NULL HASHCOL , t2.b2, t2.x2 ] COUNT
| | | | | | | | | ) [ t2.a2 NOT NULL HASHCOL = t61.b61, t52.a52 NOT NULL HASHCOL = t2.b2 ],
| | | | | | | | | table(sys.t38) [ t38.a38 NOT NULL HASHCOL , t38.b38, t38.x38 ] COUNT
| | | | | | | | ) [ t25.a25 NOT NULL HASHCOL = t38.b38, t38.a38 NOT NULL HASHCOL = t52.b52 ],
| | | | | | | | table(sys.t30) [ t30.a30 NOT NULL HASHCOL , t30.b30, t30.x30 ] COUNT
| | | | | | | ) [ t32.b32 = t30.a30 NOT NULL HASHCOL , t30.b30 = t9.a9 NOT NULL HASHCOL ],
| | | | | | | table(sys.t37) [ t37.a37 NOT NULL HASHCOL , t37.b37, t37.x37 ] COUNT
| | | | | | ) [ t37.a37 NOT NULL HASHCOL = t54.b54, t47.a47 NOT NULL HASHCOL = t37.b37 ],
| | | | | | table(sys.t50) [ t50.a50 NOT NULL HASHCOL , t50.b50, t50.x50 ] COUNT
| | | | | ) [ t50.a50 NOT NULL HASHCOL = t63.b63 ],
| | | | | table(sys.t21) [ t21.a21 NOT NULL HASHCOL , t21.b21, t21.x21 ] COUNT
| | | | ) [ t21.a21 NOT NULL HASHCOL = t50.b50, t29.a29 NOT NULL HASHCOL = t21.b21 ],
| | | | table(sys.t10) [ t10.a10 NOT NULL HASHCOL , t10.b10, t10.x10 ] COUNT
| | | ) [ t10.a10 NOT NULL HASHCOL = t25.b25 ],
| | | table(sys.t3) [ t3.a3 NOT NULL HASHCOL , t3.b3, t3.x3 ] COUNT
| | ) [ t10.b10 = t3.a3 NOT NULL HASHCOL , t3.b3 = t18.a18 NOT NULL HASHCOL ],
| | table(sys.t8) [ t8.a8 NOT NULL HASHCOL , t8.b8, t8.x8 ] COUNT
| ) [ t54.a54 NOT NULL HASHCOL = t8.b8, t8.a8 NOT NULL HASHCOL = t20.b20 ]
) [ t20.x20, t47.x47, t38.x38, t18.x18, t10.x10, t22.x22, t37.x37, t3.x3, t63.x63, t8.x8, t30.x30, t43.x43, t54.x54, t9.x9, t21.x21, t25.x25, t2.x2, t61.x61, t55.x55, t32.x32, t52.x52, t29.x29, t50.x50, t12.x12 ]
## Comment 21262
Date: 2015-09-10 15:22:48 +0200
From: Martin van Dinther <<martin.van.dinther>>
Created attachment 351
create_64_tables_with_10_rows_each.sql
> Attached file: [create_64_tables_with_10_rows_each.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3809_create_64_tables_with_10_rows_each.sql_351) (application/sql, 34794 bytes)
> Description: create_64_tables_with_10_rows_each.sql
## Comment 21263
Date: 2015-09-10 15:23:19 +0200
From: Martin van Dinther <<martin.van.dinther>>
Created attachment 352
drop_64_tables.sql
> Attached file: [drop_64_tables.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3809_drop_64_tables.sql_352) (application/sql, 1042 bytes)
> Description: drop_64_tables.sql
## Comment 21269
Date: 2015-09-17 16:45:39 +0200
From: Martin van Dinther <<martin.van.dinther>>
Created attachment 354
explain_query_3809.out
Also adding the explain output of the query
> Attached file: [explain_query_3809.out](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3809_explain_query_3809.out_354) (text/plain, 45025 bytes)
> Description: explain_query_3809.out
## Comment 21270
Date: 2015-09-17 17:20:17 +0200
From: Martin van Dinther <<martin.van.dinther>>
Additional issue is that after getting the
GDK reported error.
HEAPalloc: Insufficient space for HEAP of 8000000000 bytes.
the server does NOT remove/purge the already created karge intermediate bat files and thus the disk remains full after running this query.
In my case the file monetdb5/dbfarm/demo/bat/20 is 7.3 GB !
Even after disconnecting from the mserver5 and stopping mserver5 process the large file(s) still remains on disk.
Only after restarting mserver5 again it seems to purge the large obsolete data file(s).
This server error handling should be improved (IMHO) by purging all the for this MAL plan created intermediate files from disk, as when the query would have been executed successfully and the query resultset was closed.
## Comment 21275
Date: 2015-09-20 21:46:04 +0200
From: @njnes
cleanout empty select operators more agressively. This results in a large join tree being reordered fully, solving the crossproducts.
## Comment 21276
Date: 2015-09-20 22:05:28 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [b35df980282e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b35df980282e) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b35df980282e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b35df980282e)
Changeset description:
remove empty select during join_reorder, solves bug #3809
## Comment 21458
Date: 2015-11-03 10:18:52 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
## Comment 22010
Date: 2016-04-05 12:09:20 +0200
From: Vijay Krishna <<vijayakrishna55>>
Is this issue and the below one same or related? The below issue is from 2014 releases and till July 2015-SP3.
https://www.monetdb.org/bugzilla/show_bug.cgi?id=3972
| Inefficient plan is generated for queries with many (>= 24) joined tables which take a long time or an HEAPalloc error. I get Error: GDK reported error. HEAPalloc: Insufficient space for HEAP of 400000000 bytes. | https://api.github.com/repos/MonetDB/MonetDB/issues/3809/comments | 0 | 2020-11-30T13:17:17Z | 2024-06-27T12:08:46Z | https://github.com/MonetDB/MonetDB/issues/3809 | 753,470,588 | 3,809 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-10 04:33:25 +0200
From: Dann Corbit <<dcorbit>>
To: SQL devs <<bugs-sql>>
Version: 11.25.15 (Dec2016-SP3)
CC: castro8583bennett, @hannesmuehleisen, @PedroTadim, @sstalin
Last updated: 2019-10-30 13:47:46 +0100
## Comment 21258
Date: 2015-09-10 04:33:25 +0200
From: Dann Corbit <<dcorbit>>
User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:25.7) Gecko/20150824 Firefox/31.9 PaleMoon/25.7.0
Build Identifier:
For timestamp and time columns (did not try any others) the precision specifier allows values from 0 to 7 (I checked the column definition from the columns system table) but no more than 3 digits of precision are stored.
sql>CREATE TABLE TT7 ( A TIMESTAMP(7));
operation successful (9.160ms)
sql>insert into TT7 values ('2015-12-12 12:30:59.1111111');
1 affected row (3.103ms)
sql>select * from TT7;
+----------------------------+
| a |
+============================+
| 2015-12-12 12:30:59.111000 |
+----------------------------+
1 tuple (1.554ms)
Reproducible: Always
### Steps to Reproduce:
sql>CREATE TABLE TT7 ( A TIMESTAMP(7));
operation successful (9.160ms)
sql>insert into TT7 values ('2015-12-12 12:30:59.1111111');
1 affected row (3.103ms)
sql>select * from TT7;
+----------------------------+
| a |
+============================+
| 2015-12-12 12:30:59.111000 |
+----------------------------+
1 tuple (1.554ms)
### Actual Results:
Precision is truncated
### Expected Results:
Precision is correct (up to 1 digit for precision of 1 through 7 digits for precision of 7)
current_timestamp() time function is only accurate to seconds. (That's broken too)
Hence, it is not useful for testing functionality.
## Comment 21259
Date: 2015-09-10 04:41:13 +0200
From: Dann Corbit <<dcorbit>>
Via SQL Server:
CREATE TABLE TT7 ( A datetime2(7));
insert into TT7 values ('2015-12-12 12:30:59.1111111');
select * from TT7;
Gives this result:
2015-12-12 12:30:59.1111111
Similarly for PostgreSQL:
CREATE TABLE TT7 ( A TIMESTAMP(7));
insert into TT7 values ('2015-12-12 12:30:59.1111111');
select * from TT7;
Gives this result (The allowed range of p is from 0 to 6 when eight-byte integer storage is used, or from 0 to 10 when floating-point storage is used. This server is using 8 byte storage):
"2015-12-12 12:30:59.111111"
## Comment 21260
Date: 2015-09-10 10:12:43 +0200
From: @hannesmuehleisen
See also https://www.monetdb.org/bugzilla/show_bug.cgi?id=3807
## Comment 21339
Date: 2015-10-14 19:02:13 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c8cb4c4f476c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c8cb4c4f476c) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c8cb4c4f476c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c8cb4c4f476c)
Changeset description:
added test for fractional precision limitation bug #3808
## Comment 25270
Date: 2017-04-28 12:58:06 +0200
From: @sstalin
Reproduced on macOS Sierra as well
## Comment 25271
Date: 2017-04-28 12:58:33 +0200
From: @sstalin
Reproduced on macOS Sierra as well
## Comment 27361
Date: 2019-10-14 05:13:17 +0200
From: Castro B <<castro8583bennett>>
Any estimation for this fix? It's kinda critical. ,https://www.maxvisits.com/
## Comment 27362
Date: 2019-10-14 15:17:33 +0200
From: @PedroTadim
For the upcoming Nov2019 release we now allow timestamps up to microsecond precision (i.e. 6 digits). However in the report, the compiler parses timestamp strings with 7 digits, which we must disallow.
## Comment 27384
Date: 2019-10-30 13:47:46 +0100
From: @sjoerdmullender
(In reply to Pedro Ferreira from comment 7)
> For the upcoming Nov2019 release we now allow timestamps up to microsecond
> precision (i.e. 6 digits). However in the report, the compiler parses
> timestamp strings with 7 digits, which we must disallow.
Absolutely not. We must allow parsing more than the specified precision, but we must do that correctly (I just fixed a bug in the upcoming release when the specified precision is less than 6).
What I can imagine is that we disallow specifying a type with a larger precision than what we actually support, i.e. no TIMESTAMP(7) but only up to TIMESTAMP(6).
Note that the value 7 in the sys.columns table (column type_digits) is not the maximum precision. It's a system table and it needs specialized knowledge to interpret any value in any system table. In this case, it's one more than the maximum precision.
The maximum precision is 6 in the upcoming Nov2019 release (it was 3 for older releases).
| Fractional seconds precision is broken for any precision larger than 3 | https://api.github.com/repos/MonetDB/MonetDB/issues/3808/comments | 0 | 2020-11-30T13:17:14Z | 2024-06-28T07:19:47Z | https://github.com/MonetDB/MonetDB/issues/3808 | 753,470,554 | 3,808 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-09 15:17:42 +0200
From: @hannesmuehleisen
To: SQL devs <<bugs-sql>>
Version: 11.19.3 (Oct2014)
CC: @njnes
Last updated: 2015-09-23 09:27:49 +0200
## Comment 21257
Date: 2015-09-09 15:17:42 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.85 Safari/537.36
Build Identifier:
%f formatting flag is not supported...
Reproducible: Always
### Steps to Reproduce:
select cast('2015-08-28 00:00:00.023000' as timestamp) - str_to_timestamp('2015-08-28 00:00:00.023000', '%Y-%m-%d %H:%M:%S.%f');
### Actual Results:
0.023
### Expected Results:
0.0
Python does support this:
>>> datetime.datetime.strptime('2015-08-28 00:00:00.023000', '%Y-%m-%d %H:%M:%S.%f')
datetime.datetime(2015, 8, 28, 0, 0, 0, 23000)
## Comment 21277
Date: 2015-09-23 09:27:49 +0200
From: @njnes
str_to_timestamp is mapped to strptime, which indeed doesn't support %f.
| str_to_timestamp does not support sub-second accuracy, yet cast does | https://api.github.com/repos/MonetDB/MonetDB/issues/3807/comments | 0 | 2020-11-30T13:17:12Z | 2024-06-28T07:19:47Z | https://github.com/MonetDB/MonetDB/issues/3807 | 753,470,527 | 3,807 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-06 19:21:32 +0200
From: Marcus Klaas <<mail>>
To: SQL devs <<bugs-sql>>
Version: 11.21.5 (Jul2015)
CC: martin.van.dinther, @njnes
Last updated: 2015-09-23 10:06:58 +0200
## Comment 21253
Date: 2015-09-06 19:21:32 +0200
From: Marcus Klaas <<mail>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Build Identifier:
Only possible to store integers in the range [-2^31 + 1, 2^31 - 1]. Tested this with mclient.
Reproducible: Always
### Steps to Reproduce:
1. create dummy table: `create table test (a int);`
2. try to insert (-2^31): `insert into test (a) values (-2147483648);`
### Actual Results:
Error message: overflow in conversion of -2147483648 to int.
### Expected Results:
Stored the integer without overflow.
There may be good reasons for you to not store integers in two's complement format internally, but this isn't documented, as far as I can see.
## Comment 21264
Date: 2015-09-10 17:03:12 +0200
From: Martin van Dinther <<martin.van.dinther>>
Updated the documentation, see
https://www.monetdb.org/Documentation/Manuals/SQLreference/BuiltinTypes
## Comment 21278
Date: 2015-09-23 10:06:58 +0200
From: @njnes
indeed the -2^31 is used a the NULL value
| Cannot store -2^31 in int | https://api.github.com/repos/MonetDB/MonetDB/issues/3806/comments | 0 | 2020-11-30T13:17:10Z | 2024-06-28T07:19:47Z | https://github.com/MonetDB/MonetDB/issues/3806 | 753,470,496 | 3,806 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-04 11:11:21 +0200
From: Endre Palatinus <<palatinus>>
To: clients devs <<bugs-clients>>
Version: 11.21.5 (Jul2015)
CC: castro8583bennett
Last updated: 2019-11-19 19:45:12 +0100
## Comment 21252
Date: 2015-09-04 11:11:21 +0200
From: Endre Palatinus <<palatinus>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/600.8.9 (KHTML, like Gecko) Version/7.1.8 Safari/537.85.17
Build Identifier:
I have tried using unixODBC (version 2.3.2) and the MonetDB ODBC client (version 11.21.5) on both Mac OS X 10.9 and Debian 8, but cannot connect through ODBC using isql on client machines to a MonetDB server running on Debian 8, although it works fine from the server machine.
Please find all details on StackOverflow:
http://stackoverflow.com/questions/32385908/connecting-to-monetdb-using-odbc
Reproducible: Always
### Steps to Reproduce:
1. Install MonetDB on a Debian 8 server.
2. Create the voc sample database on the server.
3. Install unixODBC (version 2.3.2) and the MonetDB ODBC client (version 11.21.5) on either Mac OS X 10.9 (from the DMG image), or Debian 8 (as a Debian package)
4. Create the necessary .odbc.ini file on the client.
5. Try to connect from another machine (either a MacBook or another Debian server machine) to the server: isql -v voc
### Actual Results:
[08001][unixODBC][MonetDB][ODBC Driver 11.21.5]Client unable to establish connection
[ISQL]ERROR: Could not SQLConnect
### Expected Results:
Successful connection, SQL prompt appearing.
Please find all details on StackOverflow:
http://stackoverflow.com/questions/32385908/connecting-to-monetdb-using-odbc
## Comment 21267
Date: 2015-09-14 17:10:55 +0200
From: @sjoerdmullender
I haven't been able to reproduce the problem.
Can you try the ODBC client with debugging enabled? In order to enable debugging, start the client process with an extra environment variable ODBCDEBUG whose value is the name of the file where you want the debug information to end up. Something like:
ODBCDEBUG=/tmp/odbclog isql test
You can then attach the log file to this bug report (but make sure it doesn't contain information you don't want to divulge).
## Comment 21280
Date: 2015-09-24 14:38:10 +0200
From: Endre Palatinus <<palatinus>>
Created attachment 355
isql debug log
> Attached file: [odbclog](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3805_odbclog_355) (text/plain, 2629 bytes)
> Description: isql debug log
## Comment 21281
Date: 2015-09-24 14:42:50 +0200
From: Endre Palatinus <<palatinus>>
The debug log of isql revealed the problem: the MonetDB ODBC driver has ignored the Servername parameter in my config file.
.odbc.ini:
Servername = <<LEFT OUT>>
Log:
SQLConnect: DSN=voc UID=monetdb PWD=monetdb host=localhost port=50000 database=voc.
It is quite unfortunate, that most ODBC drivers use a different name for specifying the server's hostname or IP-address: Servername, Host, or even Server (See: http://www.unixodbc.org/odbcinst.html)
## Comment 21367
Date: 2015-10-21 15:13:07 +0200
From: @sjoerdmullender
(In reply to Endre Palatinus from comment 3)
> The debug log of isql revealed the problem: the MonetDB ODBC driver has
> ignored the Servername parameter in my config file.
>
> .odbc.ini:
> Servername = <<LEFT OUT>>
>
> Log:
> SQLConnect: DSN=voc UID=monetdb PWD=monetdb host=localhost port=50000
> database=voc.
>
> It is quite unfortunate, that most ODBC drivers use a different name for
> specifying the server's hostname or IP-address: Servername, Host, or even
> Server (See: http://www.unixodbc.org/odbcinst.html)
Not only is there a difference in how the server system is identified, there is also a difference in how the username and password are specified. The MonetDB ODBC driver uses HOST, UID, and PWD. There are also PORT, DATABASE, and LOGFILE that can be set.
I can imagine that we would recognize multiple ways of specifying these connection attributes, but that would be a quite low priority
| Connecting to MonetDB using ODBC fails | https://api.github.com/repos/MonetDB/MonetDB/issues/3805/comments | 0 | 2020-11-30T13:17:07Z | 2024-06-28T07:19:47Z | https://github.com/MonetDB/MonetDB/issues/3805 | 753,470,465 | 3,805 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-03 21:09:12 +0200
From: John Thomas <<john>>
To: Merovingian devs <<bugs-merovingian>>
Version: 11.21.5 (Jul2015)
Last updated: 2015-11-03 10:18:45 +0100
## Comment 21247
Date: 2015-09-03 21:09:12 +0200
From: John Thomas <<john>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36
Build Identifier:
We've been experiencing some intermittent mserver crashes (which I'm investigating and will file a separate bug report for if needed) recently. And it seems that any time one of our databases goes down and is in the middle of restarting, running the command `monetdb status <db>` results in a monetdb crash with SIGSEGV.
The problem is in the `abbreviateString` function in `tools/merovingian/utils/utils.c`, which does not properly handle small desired widths. In this particular case, the width parameter is always 0 (for whatever reason, which I believe to also be a bug), and this results in an attempted memcpy of length 18446744073709551614, which obviously dies a terrible death.
Reproducible: Always
### Steps to Reproduce:
1. Start a database
2. While the database is still in process of starting up, run `monetdb status <db>`
3. Observe crash
### Actual Results:
monetdb crashes
### Expected Results:
monetdb doesn't crash
Note: This problem was found using Feb2013 SP6 but confirmed to still exist in Jul2015.
## Comment 21248
Date: 2015-09-03 22:45:11 +0200
From: @sjoerdmullender
I can't reproduce this problem.
What system are you running this on? Did you compile yourself or are you using a pre-built package?
It looks like you can handle a debugger. What is the stack trace when the crash happens? What is the value of TERMWIDTH (that's a variable, despite the all-caps name).
## Comment 21249
Date: 2015-09-03 23:01:13 +0200
From: John Thomas <<john>>
There's a clear logic error in the source:
inline void
abbreviateString(char *ret, const char *in, size_t width)
{
size_t len;
size_t off;
if ((len = strlen(in)) > width) {
/* position abbreviation dots in the middle (Mac style, iso
* Windows style) */
memcpy(ret, in, (width / 2) - 2); // <--- if width < 4, this crashes
memcpy(ret + (width / 2) - 2, "...", 3);
off = len - (width - ((width / 2) - 2) - 3);
memcpy(ret + (width / 2) + 1, in + off, (len - off) + 1);
} else {
sprintf(ret, "%s", in);
}
}
You may have better ideas of how to fix it, but here's the workaround I'm using in my build now:
inline void
abbreviateString(char *ret, const char *in, size_t width)
{
size_t len;
size_t off;
if ((len = strlen(in)) > width) {
if (width >= 4) {
/* position abbreviation dots in the middle (Mac style, iso
* Windows style) */
memcpy(ret, in, (width / 2) - 2);
memcpy(ret + (width / 2) - 2, "...", 3);
off = len - (width - ((width / 2) - 2) - 3);
memcpy(ret + (width / 2) + 1, in + off, (len - off) + 1);
} else {
sprintf(ret, "%.*s", width, in);
}
} else {
sprintf(ret, "%s", in);
}
}
Now as to why in this particular case it is being passed width = 0, I'm not sure. But fixing this function at least keeps it from crashing.
## Comment 21250
Date: 2015-09-03 23:05:06 +0200
From: @sjoerdmullender
(In reply to John Thomas from comment 2)
> There's a clear logic error in the source:
I understand that. What I was after is where the width=0 comes from.
## Comment 21251
Date: 2015-09-03 23:16:08 +0200
From: John Thomas <<john>>
Backtrace (note this was captured from Feb2013 SP6):
(gdb) bt
0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:116
1 0x0000000000408abb in memcpy (__len=18446744073709551614, __src=0x7ffc9b18bf10, __dest=0xf2b180) at /usr/include/x86_64-linux-gnu/bits/string3.h:51
2 abbreviateString (ret=0xf2b180 "starting up since 2015-09-03 17", in=0x7ffc9b18bf10 "starting up since 2015-09-03 17", width=0) at utils.c:294
3 0x0000000000405205 in printStatus (uriwidth=0, dbwidth=5, mode=1, stats=0xf2a850) at monetdb.c:333
4 command_status (argv=<optimized out>, argc=<optimized out>) at monetdb.c:855
5 main (argc=<optimized out>, argv=<optimized out>) at monetdb.c:1762
(gdb) p TERMWIDTH
$1 = 0
Another piece of info that might help, the status command is being run via shell out from another program, as opposed a command line prompt. I imagine that's why TERMWIDTH is 0.
## Comment 21254
Date: 2015-09-07 15:45:41 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [23074865b5cf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=23074865b5cf) 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=23074865b5cf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=23074865b5cf)
Changeset description:
Always use minimum width of 32 for URI in monetdb status command.
This hopefully fixes bug #3804.
## Comment 21299
Date: 2015-09-29 14:06:09 +0200
From: @sjoerdmullender
I'm closing this since I believe I fixed this.
If it turns out the bug is still there, please reopen.
## Comment 21453
Date: 2015-11-03 10:18:45 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| `monetdb status` command crashes under certain conditions | https://api.github.com/repos/MonetDB/MonetDB/issues/3804/comments | 0 | 2020-11-30T13:17:04Z | 2024-06-27T12:08:41Z | https://github.com/MonetDB/MonetDB/issues/3804 | 753,470,420 | 3,804 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-03 18:32:00 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.21.5 (Jul2015)
CC: @njnes
Last updated: 2015-11-03 10:18:24 +0100
## Comment 21246
Date: 2015-09-03 18:32:00 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
CREATE TABLE t1(a INTEGER, b INTEGER, c INTEGER, d INTEGER, e INTEGER);
SELECT a, e, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, a-b FROM t1 ORDER BY 2,4,3,1;
returns ERROR = !SELECT: identifier 'a' ambiguous
See many more examples in the Steps to Reproduce section.
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5 (MonetDB 5 server v11.21.6)
2. Start mclient
3. Run following SQL commands:
CREATE TABLE t1(a INTEGER, b INTEGER, c INTEGER, d INTEGER, e INTEGER);
INSERT INTO t1(e,c,b,d,a) VALUES(103,102,100,101,104);
INSERT INTO t1(a,c,d,e,b) VALUES(107,106,108,109,105);
INSERT INTO t1(e,d,b,a,c) VALUES(110,114,112,111,113);
INSERT INTO t1(d,c,e,a,b) VALUES(116,119,117,115,118);
INSERT INTO t1(c,d,b,e,a) VALUES(123,122,124,120,121);
INSERT INTO t1(a,d,b,e,c) VALUES(127,128,129,126,125);
INSERT INTO t1(e,c,a,d,b) VALUES(132,134,131,133,130);
INSERT INTO t1(a,d,b,e,c) VALUES(138,136,139,135,137);
SELECT CASE a+1 WHEN b THEN 111 WHEN c THEN 222 WHEN d THEN 333 WHEN e THEN 444 ELSE 555 END, CASE WHEN a<b-3 THEN 111 WHEN a<=b THEN 222 WHEN a<b+3 THEN 333 ELSE 444 END, a+b*2+c*3+d*4, a+b*2+c*3, c, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, abs(b-c) FROM t1 WHERE EXISTS(SELECT 1 FROM t1 AS x WHERE x.b<t1.b) OR b>c OR d NOT BETWEEN 110 AND 150 ORDER BY 4,1,5,2,6,3,7;
-- ERROR = !SELECT: identifier 'c' ambiguous
SELECT a, a+b*2+c*3+d*4+e*5, c-d, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, b-c, a+b*2 FROM t1 ORDER BY 6,2,4,5,3,1;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT a+b*2+c*3+d*4+e*5, CASE WHEN a<b-3 THEN 111 WHEN a<=b THEN 222 WHEN a<b+3 THEN 333 ELSE 444 END, a, abs(b-c), a+b*2, d, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END FROM t1 WHERE (e>c OR e<d) OR a>b ORDER BY 4,5,3,7,1,6,2;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT a, e, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, a-b FROM t1 ORDER BY 2,4,3,1;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT d, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, abs(b-c), a+b*2+c*3+d*4+e*5, CASE WHEN a<b-3 THEN 111 WHEN a<=b THEN 222 WHEN a<b+3 THEN 333 ELSE 444 END, d-e FROM t1 ORDER BY 1,6,2,3,5,4;
-- ERROR = !SELECT: identifier 'd' ambiguous
SELECT a+b*2+c*3+d*4+e*5, a, abs(a), a-b, d-e, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END FROM t1 WHERE EXISTS(SELECT 1 FROM t1 AS x WHERE x.b<t1.b) AND b>c ORDER BY 4,6,3,1,5,2;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT CASE WHEN a<b-3 THEN 111 WHEN a<=b THEN 222 WHEN a<b+3 THEN 333 ELSE 444 END, a+b*2+c*3+d*4+e*5, a, CASE a+1 WHEN b THEN 111 WHEN c THEN 222 WHEN d THEN 333 WHEN e THEN 444 ELSE 555 END, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, (SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d<t1.d), d FROM t1 WHERE a>b AND (e>a AND e<b) ORDER BY 7,2,4,6,1,3,5;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT e, (SELECT count(*) FROM t1 AS x WHERE x.b<t1.b), CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, CASE a+1 WHEN b THEN 111 WHEN c THEN 222 WHEN d THEN 333 WHEN e THEN 444 ELSE 555 END, a-b, (SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d<t1.d) FROM t1 WHERE a>b AND (c<=d-2 OR c>=d+2) AND c>d ORDER BY 6,5,4,2,3,1;
-- ERROR = !SELECT: identifier 'e' ambiguous
SELECT b, a-b, c, abs(b-c), d-e, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, b-c FROM t1 WHERE EXISTS(SELECT 1 FROM t1 AS x WHERE x.b<t1.b) ORDER BY 1,6,4,5,2,7,3;
-- ERROR = !SELECT: identifier 'b' ambiguous
SELECT (SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d<t1.d), b, a, a+b*2+c*3+d*4+e*5, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, CASE a+1 WHEN b THEN 111 WHEN c THEN 222 WHEN d THEN 333 WHEN e THEN 444 ELSE 555 END, a+b*2+c*3 FROM t1 WHERE a>b AND (e>c OR e<d) ORDER BY 3,7,2,5,6,4,1;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT c-d, a-b, b, b-c, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, c, a+b*2 FROM t1 ORDER BY 1,5,4,3,2,6,7;
-- ERROR = !SELECT: identifier 'b' ambiguous
SELECT a+b*2+c*3+d*4, a, c-d, abs(b-c), b, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END FROM t1 WHERE (e>c OR e<d) OR (c<=d-2 OR c>=d+2) ORDER BY 4,3,2,5,1,6;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT a, a+b*2+c*3+d*4+e*5, b, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, e, a-b FROM t1 ORDER BY 1,4,5,3,6,2;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT d, d-e, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, a+b*2, a+b*2+c*3+d*4+e*5, CASE WHEN a<b-3 THEN 111 WHEN a<=b THEN 222 WHEN a<b+3 THEN 333 ELSE 444 END, a+b*2+c*3 FROM t1 ORDER BY 3,2,4,5,7,1,6;
-- ERROR = !SELECT: identifier 'd' ambiguous
SELECT a, CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, (SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d<t1.d), a+b*2+c*3+d*4, b FROM t1 WHERE c>d OR d>e ORDER BY 2,5,1,3,4;
-- ERROR = !SELECT: identifier 'a' ambiguous
SELECT c, (SELECT count(*) FROM t1 AS x WHERE x.c>t1.c AND x.d<t1.d), CASE WHEN c>(SELECT avg(c) FROM t1) THEN a*2 ELSE b*10 END, a+b*2+c*3+d*4 FROM t1 WHERE b>c OR (e>c OR e<d) OR d NOT BETWEEN 110 AND 150 ORDER BY 3,2,1,4;
-- ERROR = !SELECT: identifier 'c' ambiguous
DROP TABLE t1;
### Actual Results:
All the SELECT queries have a CASE .. END in the select list and all return an Error like "!SELECT: identifier 'x' ambiguous".
### Expected Results:
No parse errors.
The SELECT queries are valid and accepted by other RDBMS.
## Comment 21273
Date: 2015-09-19 17:33:39 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0bec27aa6d8e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0bec27aa6d8e) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0bec27aa6d8e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0bec27aa6d8e)
Changeset description:
fixed bug #3803, ie make sure we add only not yet added projection columns
## Comment 21274
Date: 2015-09-19 19:27:25 +0200
From: @njnes
fixed. complex subqueries require a projection of al inner columns, but except those already projected.
## Comment 21443
Date: 2015-11-03 10:18:24 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| SQL query parser fails to parse valid SELECT query with a CASE .. END in it. It fails with parser error: identifier 'x' ambiguous | https://api.github.com/repos/MonetDB/MonetDB/issues/3803/comments | 0 | 2020-11-30T13:17:02Z | 2024-06-27T12:08:40Z | https://github.com/MonetDB/MonetDB/issues/3803 | 753,470,400 | 3,803 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-09-01 13:52:20 +0200
From: anthonin.bonnefoy
To: SQL devs <<bugs-sql>>
Version: 11.21.5 (Jul2015)
CC: guillaume.savary, @njnes, @yzchang
Last updated: 2015-11-03 10:18:42 +0100
## Comment 21245
Date: 2015-09-01 13:52:20 +0200
From: anthonin.bonnefoy
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 Iceweasel/41.0
Build Identifier:
When a table is created and filled in the same commit, a logical ref will continue to point to the bats after the table has been dropped, preventing the bat to be unlink.
On restart, the bat is correctly unlinked.
Reproducible: Always
### Steps to Reproduce:
1.Create a csv with enough lines to trigger a flush.
seq 1000000 > /tmp/test.csv
2.Create tables with this script:
-- First table, with commit create and copy inside the same commit
CREATE TABLE "test" ("test" CHARACTER LARGE OBJECT);
COPY INTO "test" FROM '/tmp/test.csv';
COMMIT;
-- Second table, with commit after create
CREATE TABLE "test2" ("test" CHARACTER LARGE OBJECT);
COMMIT;
COPY INTO "test2" FROM '/tmp/test.csv';
COMMIT;
SELECT location FROM storage where table like 'test%';
DROP TABLE "test";
DROP TABLE "test2";
COMMIT;
-- Third table, just for flushing
CREATE TABLE "test3" ("test" CHARACTER LARGE OBJECT);
COMMIT;
COPY INTO "test3" FROM '/tmp/test.csv';
COMMIT;
### Actual Results:
After waiting 30 secondes for the flush to occur, the bats from test1 table are still present.
I have the following location from storage:
+----------+
| location |
+==========+
| 2 |
| 50 |
+----------+
A ls bat/ give me this:
01 02 03 04 05 06 07 10 11 12 13 14 15 16 17 20 23 2.tail 2.theap 3.tail 3.theap 4.tail 4.theap 5.tail 6.tail BACKUP LEFTOVERS
Looking the bbp stats with "mdb.start(); bbp.get();", I have
[2] tmp_2 count=1000000 lrefs=1 refs=0 loaded tmp
### Expected Results:
The bat of the dropped table should be unlinked.
## Comment 21336
Date: 2015-10-14 18:46:01 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [773e781c6a1b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=773e781c6a1b) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=773e781c6a1b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=773e781c6a1b)
Changeset description:
fixed bat leak (Bug #3802), in case of new columns don't overwrite the delta
structure but use the copy of the sub-transaction.
## Comment 21393
Date: 2015-10-23 23:08:10 +0200
From: @yzchang
Reopen this bug, as it seems that the problem still exists with long running tests.
## Comment 21395
Date: 2015-10-23 23:26:00 +0200
From: @yzchang
Just add a cross-reference: see also this bug report: https://www.monetdb.org/bugzilla/show_bug.cgi?id=3835
## Comment 21405
Date: 2015-10-25 09:37:19 +0100
From: @njnes
the scenario described in this bug report is fixed. Please report new leaks, with a new bug report, including a scenario which could be used to reproduce the leak consistently.
## Comment 21452
Date: 2015-11-03 10:18:42 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| Disk space never freed: a logical ref is keeped on a deleted BATs | https://api.github.com/repos/MonetDB/MonetDB/issues/3802/comments | 0 | 2020-11-30T13:16:59Z | 2024-06-27T12:08:39Z | https://github.com/MonetDB/MonetDB/issues/3802 | 753,470,359 | 3,802 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-31 17:47:48 +0200
From: @yzchang
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2015-09-29 14:08:26 +0200
## Comment 21243
Date: 2015-08-31 17:47:48 +0200
From: @yzchang
Since March 2015, MonetDB License has been upgraded to Mozilla Public License Version 2.0. Therefore, the license page in the website: https://www.monetdb.org/Legal/MonetDBLicense should be upgraded accordingly.
## Comment 21300
Date: 2015-09-29 14:08:26 +0200
From: @sjoerdmullender
No, it should not. The page is still perfectly valid for older releases and should remain. The new license points to a different page.
It could be that there are still pointers to this page in the website that should be updated. But that would be a different bug.
| MonetDB License should be upgraded to Mozilla Public License Version 2.0 | https://api.github.com/repos/MonetDB/MonetDB/issues/3801/comments | 0 | 2020-11-30T13:16:57Z | 2024-06-28T07:19:46Z | https://github.com/MonetDB/MonetDB/issues/3801 | 753,470,331 | 3,801 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-31 16:14:18 +0200
From: Frédéric Jolliton <<frederic.jolliton+monetdb>>
To: SQL devs <<bugs-sql>>
Version: 11.21.5 (Jul2015)
Last updated: 2015-11-03 10:18:13 +0100
## Comment 21240
Date: 2015-08-31 16:14:18 +0200
From: Frédéric Jolliton <<frederic.jolliton+monetdb>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Build Identifier:
Hi everyone,
We found that backslashes (\) and various others characters are not properly escaped when a LIKE pattern is translated to PCRE.
Reproducible: Always
### Steps to Reproduce:
It seems that the sql2pcre function in monetdb5/modules/mal/pcre.c is missing several characters to escape.
The charaters to escape are:
. + ? * ( ) [ ] { } | ^ $ \
However, MonetDB currently only matches a subset of them!
So, we have the following broken pattern:
SELECT '\\a' LIKE '\\\\a'; => False, but should be True
SELECT '\\a' LIKE '\\\\\\\\a'; => True, but should be False
SELECT 'xa' LIKE '_a{1}'; => True, but should be False
SELECT 'xa$b' LIKE '_a$b'; => False, but should be True
Some raw examples:
CREATE FUNCTION sql2pcre(pat TEXT, esc TEXT) RETURNS TEXT EXTERNAL NAME pcre.sql2pcre;
OK: SELECT sql2pcre('a', '\\'); => NULL
OK: SELECT sql2pcre('_', '\\'); => '^.$'
OK: SELECT sql2pcre('%', '\\'); => '^.*$'
WRONG: SELECT sql2pcre('_??', '?'); => '^.?$' (correct: '^.\?$')
WRONG: SELECT sql2pcre('_{', '\\'); => '^.{$' (correct: '^.\{$')
WRONG: SELECT sql2pcre('%^%', '\\'); => '^.*^.*$' (correct: '^.*\^.*$')
Both strchr() in sql2pcre should rely on the same exception list, and this list should be:
".+?*()[]{}|^$\\"
## Comment 21241
Date: 2015-08-31 16:42:59 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [adf405e7edb0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=adf405e7edb0) 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=adf405e7edb0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=adf405e7edb0)
Changeset description:
Properly escape all PCRE special characters.
This fixes bug #3800.
## Comment 21242
Date: 2015-08-31 16:43:51 +0200
From: @sjoerdmullender
Good catch, and thanks for the fix.
## Comment 21244
Date: 2015-09-01 11:15:48 +0200
From: Frédéric Jolliton <<frederic.jolliton+monetdb>>
Wonderful. Thanks for your reactivity. Much appreciated.
## Comment 21437
Date: 2015-11-03 10:18:13 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| LIKE is broken for many patterns | https://api.github.com/repos/MonetDB/MonetDB/issues/3800/comments | 0 | 2020-11-30T13:16:54Z | 2024-06-27T12:08:36Z | https://github.com/MonetDB/MonetDB/issues/3800 | 753,470,301 | 3,800 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-27 16:41:48 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.21.1 (Jul2015)
CC: @njnes
Last updated: 2015-12-10 15:02:30 +0100
## Comment 21170
Date: 2015-08-27 16:41:48 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
CREATE TABLE t8 (a8 INTEGER, b8 INTEGER, c8 INTEGER, d8 INTEGER, e8 VARCHAR(30) );
CREATE INDEX t8asc ON t8(e8, d8 ASC, c8 ASC, b8);
CREATE INDEX t8desc ON t8(e8, d8 DESC, c8 DESC, b8);
CREATE INDEX t8descandasc ON t8(e8 DESC, d8 ASC, c8 DESC, b8 ASC, a8 DESC);
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5 ()
2. Start mclient
3. run SQL commands:
CREATE TABLE t8 (a8 INTEGER, b8 INTEGER, c8 INTEGER, d8 INTEGER, e8 VARCHAR(30) );
CREATE INDEX t8asc ON t8(e8, d8 ASC, c8 ASC, b8);
CREATE INDEX t8desc ON t8(e8, d8 DESC, c8 DESC, b8);
CREATE INDEX t8all ON t8(e8, d8, c8, b8, a8);
CREATE INDEX t8descandasc ON t8(e8 DESC, d8 ASC, c8 DESC, b8 ASC, a8 DESC);
DROP TABLE t8;
### Actual Results:
bash-4.2$ ./start_INSTALL_mserver5.sh
builtin opt gdk_dbpath = /export/scratch1/dinther/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt embedded_r = true
cmdline opt mapi_port = 41000
cmdline opt gdk_debug = 10
MonetDB 5 server v11.21.4
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs and 128bit integers dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:41000/
MonetDB/GIS module loaded
Start processing logs sql/sql_logs version 52200
Start reading the write-ahead log 'sql_logs/sql/log.3'
Finished reading the write-ahead log 'sql_logs/sql/log.3'
Finished processing logs sql/sql_logs
MonetDB/SQL module loaded
MonetDB/R module loaded
> SQL catalog created, loading sql scripts once
loading sql script: 09_like.sql
loading sql script: 10_math.sql
loading sql script: 11_times.sql
loading sql script: 12_url.sql
loading sql script: 13_date.sql
loading sql script: 14_inet.sql
loading sql script: 15_querylog.sql
loading sql script: 16_tracelog.sql
loading sql script: 17_temporal.sql
loading sql script: 20_vacuum.sql
loading sql script: 21_dependency_functions.sql
loading sql script: 22_clients.sql
loading sql script: 23_skyserver.sql
loading sql script: 24_zorder.sql
loading sql script: 25_debug.sql
loading sql script: 26_sysmon.sql
loading sql script: 27_rejects.sql
loading sql script: 39_analytics.sql
loading sql script: 39_analytics_hge.sql
loading sql script: 40_geom.sql
loading sql script: 40_json.sql
loading sql script: 40_json_hge.sql
loading sql script: 41_md5sum.sql
loading sql script: 45_uuid.sql
loading sql script: 46_gsl.sql
loading sql script: 51_sys_schema_extension.sql
loading sql script: 72_fits.sql
loading sql script: 74_netcdf.sql
loading sql script: 75_storagemodel.sql
loading sql script: 80_statistics.sql
loading sql script: 80_udf.sql
loading sql script: 80_udf_hge.sql
loading sql script: 85_bam.sql
loading sql script: 90_generator.sql
loading sql script: 90_generator_hge.sql
loading sql script: 99_system.sql
>
bash-4.2$ mclient -p 41000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.21.4 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TABLE t8 (a8 INTEGER, b8 INTEGER, c8 INTEGER, d8 INTEGER, e8 VARCHAR(30) );
operation successful (1.782ms)
sql>CREATE INDEX t8asc ON t8(e8, d8 ASC, c8 ASC, b8);
syntax error, unexpected ASC, expecting ')' or ',' in: "create index t8asc on t8(e8, d8 asc"
sql>CREATE INDEX t8desc ON t8(e8, d8 DESC, c8 DESC, b8);
syntax error, unexpected DESC, expecting ')' or ',' in: "create index t8desc on t8(e8, d8 desc"
sql>CREATE INDEX t8all ON t8(e8, d8, c8, b8, a8);
operation successful (3.937ms)
sql>CREATE INDEX t8descandasc ON t8(e8 DESC, d8 ASC, c8 DESC, b8 ASC, a8 DESC);
syntax error, unexpected DESC, expecting ')' or ',' in: "create index t8descandasc on t8(e8 desc"
sql>DROP TABLE t8;
operation successful (1.935ms)
sql>\q
### Expected Results:
For SQL compliance the ASC and DESC keywords should be accepted
and preferably also recorded in the data dictionary sys.objects such that the original CREATE INDEX can be reconstructed if desired.
## Comment 21174
Date: 2015-08-28 11:17:28 +0200
From: @njnes
INDEX isn't part of the SQL standard.
## Comment 21654
Date: 2015-12-10 15:02:30 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [010eb51544f7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=010eb51544f7) made by Martin van Dinther <martin.van.dinther@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=010eb51544f7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=010eb51544f7)
Changeset description:
Added START TRANASCTION; and ROLLBACK; to the .sql scripts such that a Timeouted execution does not leave tables with the same table name.
Disabled a failing CREATE INDEX statement (see also Bug #3799) as it created a problem in the TRANSACTION handling: request to ROLLBACK the work, which is not what we want in this script.
Extended timeout factor for selec3.test as on Win2012 (on default branch) is requires just a little bit more time.
| CREATE INDEX does not recognise the ASC or DESC keyword. It fails with a syntax error | https://api.github.com/repos/MonetDB/MonetDB/issues/3799/comments | 0 | 2020-11-30T13:16:51Z | 2024-06-28T13:13:33Z | https://github.com/MonetDB/MonetDB/issues/3799 | 753,470,261 | 3,799 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-27 16:09:55 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.21.1 (Jul2015)
CC: @njnes
Last updated: 2015-11-03 10:18:10 +0100
## Comment 21168
Date: 2015-08-27 16:09:55 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
mserver5: ../../dev/gdk/gdk_bat.c:2847: BATassertHeadProps: Assertion `b->H->sorted' failed.
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5 (MonetDB 5 server v11.21.4)
2. download and save attached select4a.test.sql file
3. Mtest.py select4a.test
### Actual Results:
bash-4.2$ Mtest.py select4a.test
Running in sql/test
15:56:44> select4a.test 0.621s ABORTED
!ERROR: Testing FAILED SIGNIFICANTLY (1 out of 1 tests failed)
1 out of 1 tests caused an abort (assertion failure)
sql/test/SQLite_sqllogictest/select4a.test
Output of select4a.test.err:
Statistics about stderr of test 'select4a.test` in directory 'sql/test`:
6 lines, 31 words, 297 chars in lines not matching '^$|^|^=`
= 6 lines, 31 words, 297 chars in lines not matching '^$|^`
24 lines, 92 words, 923 chars in all lines
stderr of test 'select4a.test` in directory 'sql/test` itself:
15:56:44 >
15:56:44 > "mserver5" "--debug=10" "--set" "gdk_nr_threads=0" "--set" "mapi_open=true" "--set" "mapi_port=34472" "--set" "mapi_usock=/var/tmp/mtest-9212/.s.monetdb.34472" "--set" "monet_prompt=" "--forcemito" "--set" "mal_listing=2" "--dbpath=/export/scratch1/dinther/INSTALL/var/MonetDB/mTests_sql_test" "--set" "mal_listing=0" "--set" "embedded_r=yes"
15:56:44 >
mserver5: ../../dev/gdk/gdk_bat.c:2847: BATassertHeadProps: Assertion `b->H->sorted' failed.
Aborted
15:56:44 >
15:56:44 > "mclient" "-lsql" "-ftest" "-Eutf-8" "-i" "-e" "--host=/var/tmp/mtest-9212" "--port=34472"
15:56:44 >
~ MAPI = (monetdb) /var/tmp/mtest-9212/.s.monetdb.34472
ACTION= mapi_query_done
QUERY = -- 9 values hashing to 0242ff524f6efe4a8115ad23f4d8659a
ERROR = !write error on stream
15:56:45 >
15:56:45 > "Done."
15:56:45 >
### Expected Results:
No assertion failure.
The problem is somewhere in the INTERSECT part of the query as without it, it does not fail.
## Comment 21169
Date: 2015-08-27 16:12:13 +0200
From: Martin van Dinther <<martin.van.dinther>>
Created attachment 347
sql test file
> Attached file: [select4a.test.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3798_select4a.test.sql_347) (application/sql, 57662 bytes)
> Description: sql test file
## Comment 21173
Date: 2015-08-28 11:05:01 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8491714d157c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8491714d157c) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8491714d157c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8491714d157c)
Changeset description:
fixed bug #3798, ie properly set the bat properties in ALGgroupby
## Comment 21175
Date: 2015-08-28 11:18:19 +0200
From: @njnes
intersect group by code is fixed
## Comment 21436
Date: 2015-11-03 10:18:10 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| SELECT query with INTERSECT causes assertion failure | https://api.github.com/repos/MonetDB/MonetDB/issues/3798/comments | 0 | 2020-11-30T13:16:49Z | 2024-06-27T12:08:34Z | https://github.com/MonetDB/MonetDB/issues/3798 | 753,470,233 | 3,798 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-27 08:16:32 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.17.13 (Jan2014-SP1)
Last updated: 2015-11-03 10:18:02 +0100
## Comment 21167
Date: 2015-08-27 08:16:32 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
Lines with an incorrect number of columns should simply be skipped and added to the rejects table. It currently stops the best effort sequence when insufficient columns are provided.
A test has been added.
Reproducible: Always
## Comment 21171
Date: 2015-08-27 22:36:41 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [1e216af13eec](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1e216af13eec) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1e216af13eec](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1e216af13eec)
Changeset description:
Add test for bug #3797
## Comment 21172
Date: 2015-08-27 22:38:31 +0200
From: @mlkersten
- ignore lines with less/more values then needed
- provide proper error messages
- fix post error fixing in the columns returned
## Comment 21433
Date: 2015-11-03 10:18:02 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| COPY INTO with incorrect number columns | https://api.github.com/repos/MonetDB/MonetDB/issues/3797/comments | 0 | 2020-11-30T13:16:47Z | 2024-06-27T12:08:33Z | https://github.com/MonetDB/MonetDB/issues/3797 | 753,470,200 | 3,797 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-25 17:03:14 +0200
From: @jrvosse
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
CC: martin.van.dinther
Last updated: 2015-09-10 18:41:00 +0200
## Comment 21166
Date: 2015-08-25 17:03:14 +0200
From: @jrvosse
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.37 Safari/537.36
Build Identifier:
https://www.monetdb.org/Documentation/SQLreference/Temporal
claims support for DAYTIME, which monetdb apparently does not support
Reproducible: Always
## Comment 21265
Date: 2015-09-10 18:41:00 +0200
From: Martin van Dinther <<martin.van.dinther>>
Thanks for reporting.
The documentation has been updated.
| SQL DAYTIME wrongly documented | https://api.github.com/repos/MonetDB/MonetDB/issues/3796/comments | 0 | 2020-11-30T13:16:44Z | 2024-06-27T12:08:32Z | https://github.com/MonetDB/MonetDB/issues/3796 | 753,470,172 | 3,796 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-20 15:50:25 +0200
From: @mlkersten
To: GDK devs <<bugs-common>>
Version: 11.21.1 (Jul2015)
Last updated: 2015-08-24 15:28:59 +0200
## Comment 21161
Date: 2015-08-20 15:50:25 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
The context is the profiler branch derived from default, which generate json profiler events at high speed.
The branch state is frozen, because it is possible to generate a GDB trace where two updates are applied concurrently on the same (string) BAT within a block of instructions guarded by a system lock (mal_profiler_lock).
Depending on the run you may see a double free, an access within an block already freeed, or a GDKextend failure. Assertions get triggeed in in_int_free called from GDKupgradevarheap.
Reproducible: Always
### Steps to Reproduce:
1. Start mserver -d sf10
2. Start tachograph -d sf10
3. Start mclient -d sf10
\<02.sql (from tpch)
## Comment 21163
Date: 2015-08-24 14:25:39 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [b74228236831](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b74228236831) 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=b74228236831](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b74228236831)
Changeset description:
When you unset a lock, you first have to set it.
This probably fixes bug #3795.
## Comment 21164
Date: 2015-08-24 15:28:59 +0200
From: @mlkersten
A typical case of misaligned lock/unlock pairs.
| Suspicious concurrency issue in MAL/GDK | https://api.github.com/repos/MonetDB/MonetDB/issues/3795/comments | 0 | 2020-11-30T13:16:42Z | 2024-06-27T12:08:32Z | https://github.com/MonetDB/MonetDB/issues/3795 | 753,470,152 | 3,795 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-20 13:41:35 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.21.1 (Jul2015)
CC: akkaran046, @njnes
Last updated: 2019-02-12 13:58:57 +0100
## Comment 21160
Date: 2015-08-20 13:41:35 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
Querying the sys.rejects view or sys.rejects() function results in error message:
Error: No reject table available
SQLState: 22000
This is not expected for a metadata view or function. It should return a (possibly empty) resultset.
Also note that the error message is incorrect as it mentions table: reject while we are querying the rejects (with an s at the end) view and function.
Maybe this is a hardcoded error message string?
Reproducible: Always
### Steps to Reproduce:
1. Start mserver5 (MonetDB 5 server v11.21.4: compiled from Jul2015 branch with assertions enabled)
2. Start mclient
3. run SQL queries:
select * from "sys"."rejects";
select * from sys.rejects;
select * from rejects;
select * from "sys"."tables" where name = 'rejects';
select * from "sys"."rejects"();
select * from sys.rejects();
select * from rejects();
select * from "sys"."functions" where name = 'rejects';
### Actual Results:
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.21.4 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select * from "sys"."rejects";
No reject table available
sql>select * from sys.rejects;
No reject table available
sql>select * from rejects;
No reject table available
sql>select * from "sys"."tables" where name = 'rejects';
+------+---------+---------+---------------------------------------------------------+------+--------+----------+--------+----------+
| id | name | schema_ | query | type | system | commit_a | access | temporar |
: : : id : : : : ction : : y :
+======+=========+=========+=========================================================+======+========+==========+========+==========+
| 6292 | rejects | 2000 | create view sys.rejects as select * from sys.rejects(); | 11 | true | 0 | 0 | 0 |
+------+---------+---------+---------------------------------------------------------+------+--------+----------+--------+----------+
1 tuple (3.859ms)
sql>select * from "sys"."rejects"();
No reject table available
sql>select * from sys.rejects();
No reject table available
sql>select * from rejects();
No reject table available
sql>select * from "sys"."functions" where name = 'rejects';
+------+---------+--------------------------------------------------------------+------+------+------+-------+-------+-------+------+
| id | name | func | mod | lang | type | side_ | varre | varar | sche |
: : : : : uage : : effec : s : g : ma_i :
: : : : : : : t : : : d :
+======+=========+==============================================================+======+======+======+=======+=======+=======+======+
| 6282 | rejects | -- This Source Code Form is subject to the terms of the Mozi | sql | 1 | 5 | false | false | false | 2000 |
: : : lla Public : : : : : : : :
: : : -- License, v. 2.0. If a copy of the MPL was not distribute : : : : : : : :
: : : d with this : : : : : : : :
: : : -- file, You can obtain one at http://mozilla.org/MPL/2.0/. : : : : : : : :
: : : -- : : : : : : : :
: : : -- Copyright 2008-2015 MonetDB B.V. : : : : : : : :
: : : : : : : : : : :
: : : -- COPY into reject management : : : : : : : :
: : : : : : : : : : :
: : : create function sys.rejects() : : : : : : : :
: : : returns table( : : : : : : : :
: : : rowid bigint, : : : : : : : :
: : : fldid int, : : : : : : : :
: : : "message" string, : : : : : : : :
: : : "input" string : : : : : : : :
: : : ) : : : : : : : :
: : : external name sql.copy_rejects; : : : : : : : :
+------+---------+--------------------------------------------------------------+------+------+------+-------+-------+-------+------+
1 tuple (1.288ms)
sql>
### Expected Results:
No error message. It should return a (possibly empty) resultset.
Alternatively if this view and function does not exist permanently, exclude it from the metadata tables: sys.tables and sys.functions
## Comment 21279
Date: 2015-09-23 11:20:46 +0200
From: @njnes
fixed by always creating the bats (when used).
## Comment 21457
Date: 2015-11-03 10:18:50 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| table function sys.rejects() and view sys.rejects() are listed are metadata objects but give an (incorrect) error when they are queried | https://api.github.com/repos/MonetDB/MonetDB/issues/3794/comments | 0 | 2020-11-30T13:16:39Z | 2024-06-27T12:08:30Z | https://github.com/MonetDB/MonetDB/issues/3794 | 753,470,112 | 3,794 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-20 12:37:20 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.21.1 (Jul2015)
Last updated: 2015-09-29 14:13:45 +0200
## Comment 21159
Date: 2015-08-20 12:37:20 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
WARNING To speedup user.columnsize a bulk operator implementation is needed
X_65:bat[:oid,:lng] := mal.multiplex("user":str,"columnsize":str,X_45:bat[:oid,:str],X_57:bat[:oid,:lng],X_64:bat[:oid,:lng]);
WARNING To speedup user.heapsize a bulk operator implementation is needed
X_75:bat[:oid,:lng] := mal.multiplex("user":str,"heapsize":str,X_45:bat[:oid,:str],X_64:bat[:oid,:lng],X_74:bat[:oid,:int]);
WARNING To speedup user.hashsize a bulk operator implementation is needed
X_86:bat[:oid,:lng] := mal.multiplex("user":str,"hashsize":str,X_85:bat[:oid,:bit],X_57:bat[:oid,:lng]);
WARNING To speedup user.imprintsize a bulk operator implementation is needed
X_88:bat[:oid,:lng] := mal.multiplex("user":str,"imprintsize":str,X_57:bat[:oid,:lng],X_45:bat[:oid,:str]);
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB 5 server v11.21.4: compiled from Jul2015 branch with assertions enabled)
2. start mclient
3. run SQL query:
select * from sys.tablestoragemodel;
or alternatively:
select * from sys.storagemodel();
### Actual Results:
builtin opt gdk_dbpath = /export/scratch1/dinther/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt embedded_r = true
cmdline opt mapi_port = 41000
cmdline opt gdk_debug = 10
MonetDB 5 server v11.21.4
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs and 128bit integers dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:41000/
MonetDB/GIS module loaded
Start processing logs sql/sql_logs version 52200
Start reading the write-ahead log 'sql_logs/sql/log.3'
Finished reading the write-ahead log 'sql_logs/sql/log.3'
Finished processing logs sql/sql_logs
MonetDB/SQL module loaded
MonetDB/R module loaded
>WARNING To speedup user.columnsize a bulk operator implementation is needed
X_65:bat[:oid,:lng] := mal.multiplex("user":str,"columnsize":str,X_45:bat[:oid,:str],X_57:bat[:oid,:lng],X_64:bat[:oid,:lng]);
WARNING To speedup user.heapsize a bulk operator implementation is needed
X_75:bat[:oid,:lng] := mal.multiplex("user":str,"heapsize":str,X_45:bat[:oid,:str],X_64:bat[:oid,:lng],X_74:bat[:oid,:int]);
WARNING To speedup user.hashsize a bulk operator implementation is needed
X_86:bat[:oid,:lng] := mal.multiplex("user":str,"hashsize":str,X_85:bat[:oid,:bit],X_57:bat[:oid,:lng]);
WARNING To speedup user.imprintsize a bulk operator implementation is needed
X_88:bat[:oid,:lng] := mal.multiplex("user":str,"imprintsize":str,X_57:bat[:oid,:lng],X_45:bat[:oid,:str]);
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.21.4 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select * from sys.tablestoragemodel;
+--------+-------+-------+------------+----------+--------+----------+-----------+
| schema | table | count | columnsize | heapsize | hashes | imprints | auxiliary |
+========+=======+=======+============+==========+========+==========+===========+
+--------+-------+-------+------------+----------+--------+----------+-----------+
0 tuples (11.923ms)
sql>
### Expected Results:
No WARNINGS in the mserver5 console window
## Comment 21301
Date: 2015-09-29 14:13:45 +0200
From: @sjoerdmullender
This only happens when you build with assertions enabled. Since that is not the normal mode of operation in a production environment (or at least, it shouldn't be), this is not really a problem.
If anything, these warnings are a reminder to the developers that there is a potential for speedup.
| mserver5 shows speedup WARNINGS in console window when querying sys.tablestoragemodel table | https://api.github.com/repos/MonetDB/MonetDB/issues/3793/comments | 0 | 2020-11-30T13:16:37Z | 2024-06-28T13:13:32Z | https://github.com/MonetDB/MonetDB/issues/3793 | 753,470,085 | 3,793 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-18 13:42:09 +0200
From: @hannesmuehleisen
To: Merovingian devs <<bugs-merovingian>>
Version: 11.21.19 (Jul2015-SP4)
Last updated: 2016-04-11 11:24:28 +0200
## Comment 21158
Date: 2015-08-18 13:42:09 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:
monetdbd has a configuration setting for the optimizer pipeline,
$ monetdb get all testing
name prop source value
testing name - testing
testing type default database
testing shared default yes
testing nthreads local 4
testing optpipe local default_pipe
testing readonly default no
testing embedr local yes
testing nclients default 64
if I set this using the monetdb tool
monetdb set optpipe=sequential_pipe testing
the configuration flag changes, e.g.
testing optpipe local default_pipe
But when mserver5 is started, the command line looks like this:
[...] --set sql_optimizer=default_pipe [...] --set optpipe=sequential_pipe [...]
Since mserver5 ignores the optpipe setting, this will lead to the default pipe being used. This is confirmed by running an
explain select * from somelargetable;
and seeing
X_350:bat[:oid,:str] := sql.bind(X_2,"sys","foo","bar",0,1,4);
Clearly mitosis at work here. I think the problem is in forkmserver.c line 303ff, but this actually looks fine to me.
Reproducible: Always
## Comment 21302
Date: 2015-09-29 14:27:14 +0200
From: @sjoerdmullender
I can't reproduce this. See here (with some editing of the output to protect the innocent):
$ monetdb create testing
created database in maintenance mode: testing
$ monetdb get all testing
name prop source value
testing name - testing
testing type default database
testing shared default yes
testing nthreads default 8
testing optpipe default default_pipe
testing readonly default no
testing embedr default no
testing nclients default 64
$ monetdb set optpipe=sequential_pipe testing
$ monetdb get all testing
name prop source value
testing name - testing
testing type default database
testing shared default yes
testing nthreads default 8
testing optpipe local sequential_pipe
testing readonly default no
testing embedr default no
testing nclients default 64
$ monetdb release testing
taken database out of maintenance mode: testing
$ monetdb start testing
starting database 'testing'... done
$ grep mserver5.*testing $PREFIX/var/monetdb5/dbfarm/merovingian.log
2015-09-29 14:21:04 MSG testing[23440]: arguments: $PREFIX/bin/mserver5 --dbpath=$PREFIX/var/monetdb5/dbfarm/testing --set merovingian_uri=mapi:monetdb://$HOSTNAME:50012/testing --set mapi_open=false --set mapi_port=0 --set mapi_usock=$PREFIX/var/monetdb5/dbfarm/testing/.mapi.sock --set monet_vault_key=$PREFIX/var/monetdb5/dbfarm/testing/.vaultkey --set gdk_nr_threads=8 --set max_clients=64 --set sql_optimizer=sequential_pipe --set monet_daemon=yes
I also wonder about the second "get all" output you quote. It still says "default_pipe".
| monetdbd sets wrong property for optimizer pipeline | https://api.github.com/repos/MonetDB/MonetDB/issues/3792/comments | 0 | 2020-11-30T13:16:35Z | 2024-06-28T13:14:45Z | https://github.com/MonetDB/MonetDB/issues/3792 | 753,470,064 | 3,792 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-14 14:57:12 +0200
From: @swingbit
To: GDK devs <<bugs-common>>
Version: 11.21.1 (Jul2015)
CC: @drstmane
Last updated: 2015-08-28 13:41:28 +0200
## Comment 21148
Date: 2015-08-14 14:57:12 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36
Build Identifier:
This join fails trying to allocate 2.2TB
sql>START TRANSACTION;
auto commit mode: off
sql>CREATE TABLE all_termDict_unstemmed_tmp AS
more>SELECT termID, term, prob
more>FROM termDict
more>WHERE termID IN (SELECT termID FROM all_tc_unstemmed)
more>WITH DATA;
Object not found
GDKsave: failed name=25/2503, ext=tail, mode 0
GDKsave: failed name=25/2504, ext=tail, mode 0
GDKsave: failed name=25/2520, ext=tail, mode 0
HEAPextend: failed to extend to 2420077101056 for 03/322.tail: GDKmremap() failed
More info:
CREATE TABLE "spinque"."termdict" (
"termid" INTEGER NOT NULL,
"term" CHARACTER LARGE OBJECT NOT NULL,
"prob" DOUBLE NOT NULL DEFAULT 1.000000,
CONSTRAINT "termdict_termid_pkey" PRIMARY KEY ("termid"),
CONSTRAINT "termdict_term_unique" UNIQUE ("term")
);
sql>\d all_tc_unstemmed
CREATE TABLE "spinque"."all_tc_unstemmed" (
"termid" INTEGER NOT NULL,
"objid" INTEGER NOT NULL,
"prob" DOUBLE NOT NULL,
CONSTRAINT "all_tc_unstemmed_objid_fkey" FOREIGN KEY ("objid") REFERENCES "spinque"."dict" ("id"),
CONSTRAINT "all_tc_unstemmed_termid_fkey" FOREIGN KEY ("termid") REFERENCES "spinque"."all_termdict_unstemmed" ("termid")
);
sql>select count(*) from termDict;
+--------+
| L1 |
+========+
| 679338 |
+--------+
sql> select count(*) from all_tc_unstemmed;
auto commit mode: on
+----------+
| L1 |
+==========+
| 51956929 |
+----------+
Reproducible: Always
$ ./mserver5 --version
MonetDB 5 server v11.21.2 (64-bit, 64-bit oids, 128-bit integers)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.37 2015-04-28 (compiled with 8.37)
openssl: OpenSSL 1.0.1k 8 Jan 2015 (compiled with OpenSSL 1.0.1k-fips 8 Jan 2015)
libxml2: 2.9.2 (compiled with 2.9.2)
Compiled by: roberto@spinque02.spinque.com (x86_64-unknown-linux-gnu)
Compilation: gcc -O3 -pipe -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code -D_FORTIFY_SOURCE=2
Linking : /usr/bin/ld -m elf_x86_64
## Comment 21149
Date: 2015-08-14 15:29:28 +0200
From: @drstmane
What about the messages before the failing HEAPextend:
Object not found
GDKsave: failed name=25/2503, ext=tail, mode 0
GDKsave: failed name=25/2504, ext=tail, mode 0
GDKsave: failed name=25/2520, ext=tail, mode 0
?
Does one of the following work?
CREATE TABLE all_termDict_unstemmed_tmp AS
SELECT termID, term, prob
FROM termDict
WHERE termID IN (SELECT distinct termID FROM all_tc_unstemmed)
WITH DATA;
CREATE TABLE all_termDict_unstemmed_tmp AS
SELECT termDict.termID, termDict.term, termDict.prob
FROM termDict
JOIN (SELECT distinct termID FROM all_tc_unstemmed) as atu
ON termDict.termID = atu.termID
WITH DATA;
Could you provide an explain of your original query?
## Comment 21150
Date: 2015-08-14 15:38:59 +0200
From: @swingbit
There is no message before those errors. I guess the repeated errors come from different threads.
Both the queries with distinct work, good catch!
Explain of the original query:
sql>explain CREATE TABLE all_termDict_unstemmed_tmp AS
more>SELECT termID, term, prob
more>FROM termDict
more>WHERE termID IN (SELECT termID FROM all_tc_unstemmed)
more>WITH DATA;
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| mal |
+========================================================================================================================================================================================================================+
| function user.s2_33{autoCommit=true}():void; |
| X_52:void := querylog.define("explain create table all_termdict_unstemmed_tmp as\nselect termid, term, prob\nfrom termdict\nwhere termid in (select termid from all_tc_unstemmed)\nwith data;","default_pipe",75); |
| X_2 := sql.mvc(); |
| sql.catalog(24,"spinque",nil,0); |
| barrier X_130 := language.dataflow(); |
| X_8:bat[:oid,:oid] := sql.tid(X_2,"spinque","termdict"); |
| X_10:bat[:oid,:int] := sql.bind(X_2,"spinque","termdict","termid",0); |
| (X_12,r1_15) := sql.bind(X_2,"spinque","termdict","termid",2); |
| X_15:bat[:oid,:int] := sql.bind(X_2,"spinque","termdict","termid",1); |
| X_17 := sql.delta(X_10,X_12,r1_15,X_15); |
| X_18 := algebra.leftfetchjoin(X_8,X_17); |
| X_19 := bat.mirror(X_18); |
| X_73:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",0,8); |
| X_88:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,0,8); |
| X_96 := algebra.leftfetchjoin(X_73,X_88); |
| (X_104,X_105) := algebra.subjoin(X_18,X_96,nil:BAT,nil:BAT,false,nil:lng); |
| X_75:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",1,8); |
| X_89:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,1,8); |
| X_97 := algebra.leftfetchjoin(X_75,X_89); |
| (X_106,X_107) := algebra.subjoin(X_18,X_97,nil:BAT,nil:BAT,false,nil:lng); |
| X_77:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",2,8); |
| X_90:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,2,8); |
| X_98 := algebra.leftfetchjoin(X_77,X_90); |
| (X_108,X_109) := algebra.subjoin(X_18,X_98,nil:BAT,nil:BAT,false,nil:lng); |
| X_79:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",3,8); |
| X_91:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,3,8); |
| X_99 := algebra.leftfetchjoin(X_79,X_91); |
| (X_110,X_111) := algebra.subjoin(X_18,X_99,nil:BAT,nil:BAT,false,nil:lng); |
| X_81:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",4,8); |
| X_92:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,4,8); |
| X_100 := algebra.leftfetchjoin(X_81,X_92); |
| (X_112,X_113) := algebra.subjoin(X_18,X_100,nil:BAT,nil:BAT,false,nil:lng); |
| X_83:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",5,8); |
| X_93:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,5,8); |
| X_101 := algebra.leftfetchjoin(X_83,X_93); |
| (X_114,X_115) := algebra.subjoin(X_18,X_101,nil:BAT,nil:BAT,false,nil:lng); |
| X_85:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",6,8); |
| X_94:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,6,8); |
| X_102 := algebra.leftfetchjoin(X_85,X_94); |
| (X_116,X_117) := algebra.subjoin(X_18,X_102,nil:BAT,nil:BAT,false,nil:lng); |
| X_87:bat[:oid,:oid] := sql.tid(X_2,"spinque","all_tc_unstemmed",7,8); |
| X_95:bat[:oid,:int] := sql.bind(X_2,"spinque","all_tc_unstemmed","termid",0,7,8); |
| X_103 := algebra.leftfetchjoin(X_87,X_95); |
| (X_118,X_119) := algebra.subjoin(X_18,X_103,nil:BAT,nil:BAT,false,nil:lng); |
| X_121 := mat.packIncrement(X_104,8); |
| X_122 := mat.packIncrement(X_121,X_106); |
| X_123 := mat.packIncrement(X_122,X_108); |
| X_124 := mat.packIncrement(X_123,X_110); |
| X_125 := mat.packIncrement(X_124,X_112); |
| X_126 := mat.packIncrement(X_125,X_114); |
| X_127 := mat.packIncrement(X_126,X_116); |
| X_21 := mat.packIncrement(X_127,X_118); |
| X_25 := algebra.tinter(X_19,X_21); |
| X_26 := algebra.leftfetchjoin(X_25,X_18); |
| language.pass(X_18); |
| exit X_130; |
| X_27 := sql.append(X_2,"spinque","all_termdict_unstemmed_tmp","termid",X_26); |
| barrier X_133 := language.dataflow(); |
| X_29:bat[:oid,:str] := sql.bind(X_27,"spinque","termdict","term",0); |
| (X_32,r1_40) := sql.bind(X_27,"spinque","termdict","term",2); |
| X_34:bat[:oid,:str] := sql.bind(X_27,"spinque","termdict","term",1); |
| X_35 := sql.delta(X_29,X_32,r1_40,X_34); |
| X_36:bat[:oid,:str] := algebra.leftfetchjoinPath(X_25,X_8,X_35); |
| exit X_133; |
| X_37 := sql.append(X_27,"spinque","all_termdict_unstemmed_tmp","term",X_36); |
| barrier X_136 := language.dataflow(); |
| X_38:bat[:oid,:dbl] := sql.bind(X_37,"spinque","termdict","prob",0); |
| (X_42,r1_52) := sql.bind(X_37,"spinque","termdict","prob",2); |
| X_45:bat[:oid,:dbl] := sql.bind(X_37,"spinque","termdict","prob",1); |
| X_47 := sql.delta(X_38,X_42,r1_52,X_45); |
| X_48:bat[:oid,:dbl] := algebra.leftfetchjoinPath(X_25,X_8,X_47); |
| exit X_136; |
| sql.append(X_37,"spinque","all_termdict_unstemmed_tmp","prob",X_48); |
| sql.exportOperation(""); |
| end user.s2_33; |
+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
75 tuples (6.635ms)
Debug of the original query:
sql>debug CREATE TABLE all_termDict_unstemmed_tmp AS
more>SELECT termID, term, prob
more>FROM termDict
more>WHERE termID IN (SELECT termID FROM all_tc_unstemmed)
more>WITH DATA;
mdb>mdb.start();
mdb>
mdb>X_2=0@0:void := user.s3_33();
mdb>
mdb>X_51=0@0:void := querylog.define("debug create table all_termdict_unstemmed_tmp as\nselect termid, term, prob\nfrom termdict\nwhere termid in (select termid from all_tc_unstemmed)\nwith data;","default_pipe",75);
mdb>
mdb>X_1=0 := sql.mvc();
mdb>
mdb>sql.catalog(24,"spinque",nil,0);
mdb>
mdb>barrier X_153=false := language.dataflow();
mdb>
mdb>X_7=nil:bat[:oid,:oid] := sql.tid(X_1=0,"spinque","termdict");
mdb>
mdb>X_9=nil:bat[:oid,:int] := sql.bind(X_1=0,"spinque","termdict","termid",0);
mdb>
mdb>(X_11=nil:bat[:oid,:oid],r1_14=nil:bat[:oid,:int]) := sql.bind(X_1=0,"spinque","termdict","termid",2);
mdb>
mdb>X_14=nil:bat[:oid,:int] := sql.bind(X_1=0,"spinque","termdict","termid",1);
mdb>
mdb>X_16=nil:bat[:oid,:int] := sql.delta(X_9=<tmp_1604>[679338],X_11=<tmp_2540>[0],r1_14=<tmp_2334>[0],X_14=<tmp_2334>[0]);
mdb>
mdb>X_17=nil:bat[:oid,:int] := algebra.leftfetchjoin(X_7=<tmp_14260>[679338],X_16=<tmp_1604>[679338]);
mdb>
mdb>X_18=nil:bat[:oid,:oid] := bat.mirror(X_17=<tmp_12726>[679338]);
mdb>
mdb>X_80=nil:bat[:oid,:oid] := sql.tid(X_1=0,"spinque","all_tc_unstemmed",0,8);
mdb>
mdb>X_95=nil:bat[:oid,:int] := sql.bind(X_1=0,"spinque","all_tc_unstemmed","termid",0,0,8);
mdb>
mdb>X_104=nil:bat[:oid,:int] := algebra.leftfetchjoin(X_80=<tmp_14226>[6494616],X_95=<tmp_14334>[6494616]);
mdb>
mdb>(X_113=nil:bat[:oid,:oid],X_114=nil:bat[:oid,:oid]) := algebra.subjoin(X_17=<tmp_12726>[679338],X_104=<tmp_10232>[6494616],nil:BAT,nil:BAT,false,nil:lng);
mdb>
ERROR: MALException:algebra.subjoin:Object not found
ERROR: HEAPextend: failed to extend to 2420077101056 for 01/43/14334.tail: GDKmremap() failed
mdb>
## Comment 21151
Date: 2015-08-14 17:06:25 +0200
From: @sjoerdmullender
Can you run the query with a C debugger and find out exactly which call to BATextend (which calls HEAPextend) it is that is failing? And moreover, can you also report the values of all relevant variables around that call?
## Comment 21152
Date: 2015-08-17 11:29:49 +0200
From: @swingbit
Here are some more details.
It seems to be a BATextend on the right side of a mergejoin.
Note that the heap reallocation mentioned here is lower than the one reported initially (but it still fails). I guess it can be because 1) I am running the debug session on a different machine. 2) in the debug session a different thread with different chunk sizes could come first?
Breakpoint 1, HEAPextend (h=0x7ff0380039a8, size=10696196096, mayshare=0) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_heap.c:204
204 failure = "GDKmremap() failed";
0 HEAPextend (h=0x7ff0380039a8, size=10696196096, mayshare=0) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_heap.c:204
1 0x00007ff054617d7f in BATextend (b=0x7ff038003880, newcap=1337017706) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_bat.c:472
2 0x00007ff05480e3a6 in mergejoin (r1=0x7ff0380030f0, r2=0x7ff038003880, l=0x7ff020003360, r=0x7ff038003640, sl=0x0, sr=0x0, nil_matches=0, nil_on_miss=0, semi=0, must_match=0) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_join.c:1545
3 0x00007ff05481e122 in BATsubjoin (r1p=0x7ff04ae01738, r2p=0x7ff04ae01740, l=0x7ff020003360, r=0x7ff038003640, sl=0x0, sr=0x0, nil_matches=0, estimate=9223372036854775807) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_join.c:2952
(gdb) up
1 0x00007ff054617d7f in BATextend (b=0x7ff038003880, newcap=1337017706) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_bat.c:472
472 HEAPextend(&b->T->heap, theap_size, b->batRestricted == BAT_READ) != GDK_SUCCEED)
(gdb) p theap_size
$1 = 10696141648
(gdb) up
2 0x00007ff05480e3a6 in mergejoin (r1=0x7ff0380030f0, r2=0x7ff038003880, l=0x7ff020003360, r=0x7ff038003640, sl=0x0, sr=0x0, nil_matches=0, nil_on_miss=0, semi=0, must_match=0) at /opt/spinque/MonetDBServer/MonetDB.Spinque_Jul2015/src/gdk/gdk_join.c:1545
1545 BATextend(r2, newcap) != GDK_SUCCEED) {
(gdb) p newcap
$2 = 1337017706
(gdb) p nl
$3 = 1
(gdb) p nr
$4 = 413554
(gdb) p lcand
$5 = (const oid *) 0x0
(gdb) p rcand
$6 = (const oid *) 0x0
(gdb) p *l->H
$11 = {id = 0x7ff054872488 "h", width = 0, type = 0 '\000', shift = 0 '\000', varsized = 1, key = 1, dense = 1, nonil = 1, nil = 0, sorted = 1, revsorted = 0, align = 1052347, nokey = {0, 0}, nosorted = 0, norevsorted = 0, nodense = 0, seq = 0, heap = {free = 0, size = 0,
base = 0x0, filename = 0x0, copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM, newstorage = STORE_MEM, dirty = 0 '\000', farmid = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0, imprints = 0x0, props = 0x0}
(gdb) p *l->T
$12 = {id = 0x7ff05487248a "t", width = 4, type = 5 '\005', shift = 2 '\002', varsized = 0, key = 1, dense = 0, nonil = 1, nil = 0, sorted = 1, revsorted = 0, align = 1052054, nokey = {0, 0}, nosorted = 0, norevsorted = 0, nodense = 0, seq = 0, heap = {free = 2717352,
size = 2717352, base = 0x7ff04a15e000 "\022", filename = 0x7ff03c1005a0 "16/1604.tail", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MMAP, newstorage = STORE_MMAP, dirty = 0 '\000', farmid = 0 '\000', parentid = -900}, vheap = 0x0, hash = 0x0, imprints = 0x0,
props = 0x0}
(gdb) p *l->S
$13 = {tid = 140670022981377, stamp = 923, copiedtodisk = 0, dirty = 1, dirtyflushed = 0, descdirty = 1, restricted = 1, persistence = 1, role = 1, unused = 0, sharecnt = 0, map_head = 0 '\000', map_tail = 0 '\000', map_hheap = 0 '\000', map_theap = 0 '\000', deleted = 0,
first = 0, inserted = 0, count = 679338, capacity = 679338}
(gdb) p *r->H
$14 = {id = 0x7ff054872488 "h", width = 0, type = 0 '\000', shift = 0 '\000', varsized = 1, key = 1, dense = 1, nonil = 1, nil = 0, sorted = 1, revsorted = 0, align = 0, nokey = {0, 0}, nosorted = 0, norevsorted = 0, nodense = 0, seq = 12989232, heap = {free = 0, size = 0,
base = 0x0, filename = 0x0, copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM, newstorage = STORE_MEM, dirty = 0 '\000', farmid = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0, imprints = 0x0, props = 0x0}
(gdb) p *r->T
$15 = {id = 0x7ff05487248a "t", width = 4, type = 5 '\005', shift = 2 '\002', varsized = 0, key = 0, dense = 0, nonil = 1, nil = 0, sorted = 1, revsorted = 0, align = 1053124, nokey = {0, 0}, nosorted = 0, norevsorted = 0, nodense = 0, seq = 0, heap = {free = 25978464,
size = 25978464, base = 0x7ff012b4ccc0 "\346\002", filename = 0x7ff03c101230 "16/1617.tail", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MMAP, newstorage = STORE_MMAP, dirty = 0 '\000', farmid = 0 '\000', parentid = -911}, vheap = 0x0, hash = 0x0, imprints = 0x0,
props = 0x0}
(gdb) p *r->S
$16 = {tid = 140670025082625, stamp = 944, copiedtodisk = 0, dirty = 1, dirtyflushed = 0, descdirty = 1, restricted = 1, persistence = 1, role = 1, unused = 0, sharecnt = 0, map_head = 0 '\000', map_tail = 0 '\000', map_hheap = 0 '\000', map_theap = 0 '\000', deleted = 0,
first = 0, inserted = 0, count = 6494616, capacity = 6494616}
(gdb) p *r1->H
$20 = {id = 0x7ff054872488 "h", width = 0, type = 0 '\000', shift = 0 '\000', varsized = 1, key = 1, dense = 0, nonil = 1, nil = 0, sorted = 1, revsorted = 1, align = 0, nokey = {0, 0}, nosorted = 0, norevsorted = 0, nodense = 0, seq = 0, heap = {free = 0, size = 0, base = 0x0,
filename = 0x0, copied = 0, hashash = 0, forcemap = 0, storage = STORE_MEM, newstorage = STORE_MEM, dirty = 0 '\000', farmid = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0, imprints = 0x0, props = 0x0}
(gdb) p *r1->T
$21 = {id = 0x7ff05487248a "t", width = 8, type = 6 '\006', shift = 3 '\003', varsized = 0, key = 0, dense = 0, nonil = 1, nil = 0, sorted = 1, revsorted = 0, align = 1093780, nokey = {0, 0}, nosorted = 0, norevsorted = 0, nodense = 0, seq = 0, heap = {free = 5265408,
size = 10696196096, base = 0x7fed916b0000 "\b\002", filename = 0x7ff038003450 "02/273.tail", copied = 0, hashash = 0, forcemap = 0, storage = STORE_MMAP, newstorage = STORE_MMAP, dirty = 0 '\000', farmid = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0, imprints = 0x0,
props = 0x0}
(gdb) p *r1->S
$22 = {tid = 140670025082625, stamp = 945, copiedtodisk = 0, dirty = 1, dirtyflushed = 0, descdirty = 1, restricted = 0, persistence = 1, role = 1, unused = 0, sharecnt = 0, map_head = 0 '\000', map_tail = 0 '\000', map_hheap = 0 '\000', map_theap = 0 '\000', deleted = 0,
first = 0, inserted = 0, count = 658176, capacity = 1337017706}
## Comment 21153
Date: 2015-08-17 18:08:31 +0200
From: @sjoerdmullender
Ok. I understand now what's happening. I just have to come up with a solution.
The problem is that you have a pretty skewed situation: the first couple of hundred values in the left input match a large number of values in the right input. I use extrapolation over the left input only to estimate the total result size, but because of the skew, the calculation misfires. And in this case, since the left input is key, I can even know that the result is never going to be larger than the right input.
## Comment 21154
Date: 2015-08-18 12:34:08 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [1dad1e7691a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1dad1e7691a0) 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=1dad1e7691a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1dad1e7691a0)
Changeset description:
Calculate maximum join result size and use that to cap growth of BATs.
This should fix bug #3791.
## Comment 21155
Date: 2015-08-18 13:22:53 +0200
From: @swingbit
The query that used to fail now works.
## Comment 21156
Date: 2015-08-18 13:27:35 +0200
From: @sjoerdmullender
Thanks for testing.
## Comment 21178
Date: 2015-08-28 13:41:28 +0200
From: @sjoerdmullender
Jul2015 has been released.
| HEAPextend: failed to extend to 2420077101056 | https://api.github.com/repos/MonetDB/MonetDB/issues/3791/comments | 0 | 2020-11-30T13:16:31Z | 2024-06-27T12:08:27Z | https://github.com/MonetDB/MonetDB/issues/3791 | 753,470,027 | 3,791 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-14 11:20:37 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.21.1 (Jul2015)
CC: @drstmane
Last updated: 2015-08-14 11:26:46 +0200
## Comment 21142
Date: 2015-08-14 11:20:37 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36
Build Identifier:
TRACE works fine the first time, but then it seems to append to the previous one.
See example below.
Notice that the second trace is not just appended to the first one. It is actually different (more bat.append calls)
sql>trace select name from sys.functions;
+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tick | statement |
: s : :
+======+=================================================================================================================================================================================================================================================================================+
| 2 | X_33=0@0:void := querylog.define("trace select name from sys.functions;":str,"default_pipe":str,23:int); |
| 28 | X_20=<tmp_1475>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 29 | X_22=<tmp_71>[0]:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| 48 | X_24=<tmp_33>[0]:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| 27 | X_17=<tmp_317>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 9 | X_30=<tmp_71>[1]:bat[:oid,:int] := bat.append(X_22=<tmp_71>[1]:bat[:oid,:int],256:int); |
| 35 | X_21=<tmp_74>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 9 | X_27=<tmp_1475>[1]:bat[:oid,:str] := bat.append(X_20=<tmp_1475>[1]:bat[:oid,:str],"name":str); |
| 6 | X_32=<tmp_33>[1]:bat[:oid,:int] := bat.append(X_24=<tmp_33>[1]:bat[:oid,:int],0:int); |
| 6 | X_25=<tmp_317>[1]:bat[:oid,:str] := bat.append(X_17=<tmp_317>[1]:bat[:oid,:str],"sys.functions":str); |
| 14 | X_2=0:int := sql.mvc(); |
| 6 | X_28=<tmp_74>[1]:bat[:oid,:str] := bat.append(X_21=<tmp_74>[1]:bat[:oid,:str],"varchar":str); |
| 12 | X_12=<tmp_3207>[0]:bat[:oid,:str]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", hlb>=1379@0:oid, hub<1049955@0:oid} := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,1:int); |
| 10 | X_6=<tmp_135>[1379]:bat[:oid,:str]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", rows=1379, hlb>=0@0:oid, hub<1379@0:oid} := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,0:int); |
| 13 | (X_9=<tmp_2717>[0]:bat[:oid,:oid]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", rows=1379, hlb>=0@0:oid, hub<1379@0:oid},r1_9=<tmp_3207>[0]:bat[:oid,:str]) := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,2:int); |
| 235 | X_3=<tmpr_520>[1359]:bat[:oid,:oid] := sql.tid(X_2=0:int,"sys":str,"functions":str); |
| 5 | X_14=<tmp_135>[1379]:bat[:oid,:str] := sql.delta(X_6=<tmp_135>[1379]:bat[:oid,:str],X_9=<tmp_2717>[0]:bat[:oid,:oid],r1_9=<tmp_3207>[0]:bat[:oid,:str],X_12=<tmp_3207>[0]:bat[:oid,:str]); |
| 39 | X_15=<tmp_1644>[1359]:bat[:oid,:str] := algebra.leftfetchjoin(X_3=<tmpr_520>[1359]:bat[:oid,:oid],X_14=<tmp_135>[1379]:bat[:oid,:str]); |
| 2387 | barrier X_47=false:bit{transparent} := language.dataflow(); |
| 2519 | sql.resultSet(X_25=<tmp_317>[1]:bat[:oid,:str],X_27=<tmp_1475>[1]:bat[:oid,:str],X_28=<tmp_74>[1]:bat[:oid,:str],X_30=<tmp_71>[1]:bat[:oid,:int],X_32=<tmp_33>[1]:bat[:oid,:int],X_15=<tmp_1644>[1359]:bat[:oid,:str]); |
| 0 | end user.s2_1; |
| 6727 | function user.s2_1{autoCommit=true}():void; |
| 6796 | X_3=0@0:void := user.s2_1(); |
+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
23 tuples (20.604ms)
sql>trace select name from sys.functions;
+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| tick | statement |
: s : :
+======+=================================================================================================================================================================================================================================================================================+
| 2 | X_33=0@0:void := querylog.define("trace select name from sys.functions;":str,"default_pipe":str,23:int); |
| 28 | X_20=<tmp_1475>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 29 | X_22=<tmp_71>[0]:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| 48 | X_24=<tmp_33>[0]:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| 27 | X_17=<tmp_317>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 9 | X_30=<tmp_71>[1]:bat[:oid,:int] := bat.append(X_22=<tmp_71>[1]:bat[:oid,:int],256:int); |
| 35 | X_21=<tmp_74>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 9 | X_27=<tmp_1475>[1]:bat[:oid,:str] := bat.append(X_20=<tmp_1475>[1]:bat[:oid,:str],"name":str); |
| 6 | X_32=<tmp_33>[1]:bat[:oid,:int] := bat.append(X_24=<tmp_33>[1]:bat[:oid,:int],0:int); |
| 6 | X_25=<tmp_317>[1]:bat[:oid,:str] := bat.append(X_17=<tmp_317>[1]:bat[:oid,:str],"sys.functions":str); |
| 14 | X_2=0:int := sql.mvc(); |
| 6 | X_28=<tmp_74>[1]:bat[:oid,:str] := bat.append(X_21=<tmp_74>[1]:bat[:oid,:str],"varchar":str); |
| 12 | X_12=<tmp_3207>[0]:bat[:oid,:str]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", hlb>=1379@0:oid, hub<1049955@0:oid} := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,1:int); |
| 10 | X_6=<tmp_135>[1379]:bat[:oid,:str]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", rows=1379, hlb>=0@0:oid, hub<1379@0:oid} := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,0:int); |
| 13 | (X_9=<tmp_2717>[0]:bat[:oid,:oid]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", rows=1379, hlb>=0@0:oid, hub<1379@0:oid},r1_9=<tmp_3207>[0]:bat[:oid,:str]) := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,2:int); |
| 235 | X_3=<tmpr_520>[1359]:bat[:oid,:oid] := sql.tid(X_2=0:int,"sys":str,"functions":str); |
| 5 | X_14=<tmp_135>[1379]:bat[:oid,:str] := sql.delta(X_6=<tmp_135>[1379]:bat[:oid,:str],X_9=<tmp_2717>[0]:bat[:oid,:oid],r1_9=<tmp_3207>[0]:bat[:oid,:str],X_12=<tmp_3207>[0]:bat[:oid,:str]); |
| 39 | X_15=<tmp_1644>[1359]:bat[:oid,:str] := algebra.leftfetchjoin(X_3=<tmpr_520>[1359]:bat[:oid,:oid],X_14=<tmp_135>[1379]:bat[:oid,:str]); |
| 2387 | barrier X_47=false:bit{transparent} := language.dataflow(); |
| 2519 | sql.resultSet(X_25=<tmp_317>[1]:bat[:oid,:str],X_27=<tmp_1475>[1]:bat[:oid,:str],X_28=<tmp_74>[1]:bat[:oid,:str],X_30=<tmp_71>[1]:bat[:oid,:int],X_32=<tmp_33>[1]:bat[:oid,:int],X_15=<tmp_1644>[1359]:bat[:oid,:str]); |
| 0 | end user.s2_1; |
| 6727 | function user.s2_1{autoCommit=true}():void; |
| 6796 | X_3=0@0:void := user.s2_1(); |
| 2 | X_33=0@0:void := querylog.define("trace select name from sys.functions;":str,"default_pipe":str,23:int); |
| 2 | X_2=0:int := sql.mvc(); |
| 17 | X_22=<tmp_355>[0]:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| 11 | X_24=<tmp_41>[0]:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| 18 | X_17=<tmp_602>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 24 | X_21=<tmp_101>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 3 | X_30=<tmp_355>[1]:bat[:oid,:int] := bat.append(X_22=<tmp_355>[1]:bat[:oid,:int],256:int); |
| 5 | X_32=<tmp_41>[1]:bat[:oid,:int] := bat.append(X_24=<tmp_41>[1]:bat[:oid,:int],0:int); |
| 4 | X_25=<tmp_602>[1]:bat[:oid,:str] := bat.append(X_17=<tmp_602>[1]:bat[:oid,:str],"sys.functions":str); |
| 2 | X_28=<tmp_101>[1]:bat[:oid,:str] := bat.append(X_21=<tmp_101>[1]:bat[:oid,:str],"varchar":str); |
| 14 | X_20=<tmp_314>[0]:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| 2 | X_27=<tmp_314>[1]:bat[:oid,:str] := bat.append(X_20=<tmp_314>[1]:bat[:oid,:str],"name":str); |
| 179 | X_3=<tmpr_737>[1359]:bat[:oid,:oid] := sql.tid(X_2=0:int,"sys":str,"functions":str); |
| 6 | X_6=<tmp_135>[1379]:bat[:oid,:str]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", rows=1379, hlb>=0@0:oid, hub<1379@0:oid} := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,0:int); |
| 9 | X_12=<tmp_3207>[0]:bat[:oid,:str]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", hlb>=1379@0:oid, hub<1049955@0:oid} := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,1:int); |
| 10 | (X_9=<tmp_2717>[0]:bat[:oid,:oid]{file="/export/data/roberto/dbfarms/dbfarm.Spinque_Jul2015.preview/saintgobain05/./bat/01/135", rows=1379, hlb>=0@0:oid, hub<1379@0:oid},r1_9=<tmp_3207>[0]:bat[:oid,:str]) := sql.bind(X_2=0:int,"sys":str,"functions":str,"name":str,2:int); |
| 2 | X_14=<tmp_135>[1379]:bat[:oid,:str] := sql.delta(X_6=<tmp_135>[1379]:bat[:oid,:str],X_9=<tmp_2717>[0]:bat[:oid,:oid],r1_9=<tmp_3207>[0]:bat[:oid,:str],X_12=<tmp_3207>[0]:bat[:oid,:str]); |
| 18 | X_15=<tmp_322>[1359]:bat[:oid,:str] := algebra.leftfetchjoin(X_3=<tmpr_737>[1359]:bat[:oid,:oid],X_14=<tmp_135>[1379]:bat[:oid,:str]); |
| 1852 | barrier X_47=false:bit{transparent} := language.dataflow(); |
| 2507 | sql.resultSet(X_25=<tmp_602>[1]:bat[:oid,:str],X_27=<tmp_314>[1]:bat[:oid,:str],X_28=<tmp_101>[1]:bat[:oid,:str],X_30=<tmp_355>[1]:bat[:oid,:int],X_32=<tmp_41>[1]:bat[:oid,:int],X_15=<tmp_322>[1359]:bat[:oid,:str]); |
| 1 | end user.s2_1; |
| 4895 | function user.s2_1{autoCommit=true}():void; |
| 4961 | X_3=0@0:void := user.s2_1(); |
+------+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
46 tuples (11.454ms)
Reproducible: Always
### Steps to Reproduce:
1. trace select name from sys.fuctions;
2. trace select name from sys.fuctions;
3.
### Actual Results:
The second trace appends to the first one
MonetDB 5 server v11.21.2 (64-bit, 64-bit oids, 128-bit integers)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 15.6GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.37 2015-04-28 (compiled with 8.37)
openssl: OpenSSL 1.0.1k 8 Jan 2015 (compiled with OpenSSL 1.0.1k-fips 8 Jan 2015)
libxml2: 2.9.2 (compiled with 2.9.2)
Compiled by: roberto@photon.spinque.com (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/bin/ld -m elf_x86_64
## Comment 21143
Date: 2015-08-14 11:24:09 +0200
From: @drstmane
fixed by http://dev.monetdb.org/hg/MonetDB/rev/f95b938410b9
## Comment 21144
Date: 2015-08-14 11:26:46 +0200
From: @swingbit
Ah, it was fixed already my bad.
My last pull was just before the fix.
Thanks for the quick reaction.
| TRACE is broken after the first time | https://api.github.com/repos/MonetDB/MonetDB/issues/3790/comments | 0 | 2020-11-30T13:16:28Z | 2024-06-27T12:08:26Z | https://github.com/MonetDB/MonetDB/issues/3790 | 753,469,986 | 3,790 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-13 14:54:30 +0200
From: @hannesmuehleisen
To: GDK devs <<bugs-common>>
Version: 11.21.1 (Jul2015)
Last updated: 2015-11-03 10:18:19 +0100
## Comment 21139
Date: 2015-08-13 14:54:30 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:
Reproducible: Always
### Steps to Reproduce:
1. Run mserver5 with gdk_nr_threads to largish number, e.g. 96 (like the default on diamonds1)
2. CREATE TABLE s(s STRING);
3. Insert significant amount of unique strings, e.g. 10M strings with 10 random characters, in our example this leads to a string heap of ~24 GB.
4. SELECT * FROM s;
### Actual Results:
Query fails,
HEAPextend: failed to extend to 2303616614400 for 03/324.theap: h->storage == STORE_MEM && can_map && fd >= 0 && HEAPload_intern() != GDK_SUCCEED
### Expected Results:
Query should run, even though its result is admittedly very large.
From debugging, we found that MATpackIncrement() calls HEAPextend()
## Comment 21141
Date: 2015-08-13 16:18:11 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [32935e5e09fb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=32935e5e09fb) 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=32935e5e09fb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=32935e5e09fb)
Changeset description:
Don't extend string heaps since they may get replaced due to sharing.
This fixes bug #3789.
## Comment 21303
Date: 2015-09-29 14:28:23 +0200
From: @sjoerdmullender
I'm assuming this was indeed fixed.
## Comment 21439
Date: 2015-11-03 10:18:19 +0100
From: @sjoerdmullender
Jul2015 SP1 has been released.
| Query on large string table fails on HEAPextend | https://api.github.com/repos/MonetDB/MonetDB/issues/3789/comments | 0 | 2020-11-30T13:16:25Z | 2024-06-27T12:08:25Z | https://github.com/MonetDB/MonetDB/issues/3789 | 753,469,946 | 3,789 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-13 12:24:16 +0200
From: @swingbit
To: clients devs <<bugs-clients>>
Version: 11.19.15 (Oct2014-SP4)
Last updated: 2017-02-21 14:36:50 +0100
## Comment 21134
Date: 2015-08-13 12:24:16 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.155 Safari/537.36
Build Identifier:
The pom file monetdb-jdbc-11.19.15.pom contains <version>2.15</version>
It looks like the versioning of jdbc changed at some point to match the one of MonetDB, but the version inside the pom file was left behind.
Not sure if the same happens in other pom files.
Reproducible: Always
## Comment 21135
Date: 2015-08-13 12:49:27 +0200
From: @sjoerdmullender
JDBC version numbering is independent from MonetDB version numbering. If the driver didn't change in a release cycle, its version number does not change.
Note that the JDBC driver in the current release candidate is 2.16 whereas the server is 11.21.1.
## Comment 21136
Date: 2015-08-13 12:53:13 +0200
From: @swingbit
Then why I see jdbc versions 11.9.x here?
https://clojars.org/repo/monetdb/monetdb-jdbc/
## Comment 21137
Date: 2015-08-13 14:28:49 +0200
From: @swingbit
I changed the title of the issue.
It is not the version *in* the pom file to be wrong.
The last three versions have been published to the maven repository with wrong versions:
https://clojars.org/repo/monetdb/monetdb-jdbc/maven-metadata.xml
So the latest version that still work with maven is 2.13
## Comment 21138
Date: 2015-08-13 14:37:34 +0200
From: @sjoerdmullender
It looks like a bug in the upload script.
## Comment 21304
Date: 2015-09-29 14:29:57 +0200
From: @sjoerdmullender
JDBC 2.17 has been released and uploaded to the Maven repository. Do you still experience the problem?
## Comment 21307
Date: 2015-09-29 15:00:02 +0200
From: @swingbit
2.17 looks fine
## Comment 25046
Date: 2017-02-21 14:36:50 +0100
From: @swingbit
I know this bug is fixed, but I wanted to point out that the packages and metadata for the wrong versions are still in the repository (see https://clojars.org/repo/monetdb/monetdb-jdbc/).
When asking via maven for the most recent jdbc driver, you'll get version 11.19.15 and the build will actually fail, because the pom for 11.19.15 actually describes itself as 2.15.
Can the 11.19.* versions be removed from the repository?
| JDBC published in maven repository with wrong versions | https://api.github.com/repos/MonetDB/MonetDB/issues/3788/comments | 0 | 2020-11-30T13:16:23Z | 2024-06-27T12:08:24Z | https://github.com/MonetDB/MonetDB/issues/3788 | 753,469,926 | 3,788 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-12 17:44:10 +0200
From: Richard Hughes <<richard.monetdb>>
To: SQL devs <<bugs-sql>>
Version: 11.21.1 (Jul2015)
CC: @njnes
Last updated: 2015-08-28 13:41:23 +0200
## Comment 21132
Date: 2015-08-12 17:44:10 +0200
From: Richard Hughes <<richard.monetdb>>
Build is Jul2015 [8b38c01061c5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8b38c01061c5)
sql>create table foo (a smallint);
operation successful (18.292ms)
sql>select count(y),sum(z) from (select '',false,a=200 from foo union all select '',null,a=200 from foo) as t(x,y,z) group by x;
b and g must be aligned
sql>plan select count(y),sum(z) from (select '',false,a=200 from foo union all select '',null,a=200 from foo) as t(x,y,z) group by x;
+-----------------------------------------------------------------------------+
| rel |
+=============================================================================+
| project ( |
| | group by ( |
| | | union ( |
| | | | group by ( |
| | | | | project ( |
| | | | | | project ( |
| | | | | | | table(sys.foo) [ foo.a ] COUNT |
| | | | | | ) [ char "" as L1.L1, boolean "false" as L2.L2, sys.=(foo.a, smal |
: lint "200") as L5.L5 ] :
| | | | | ) [ L1.L1 as t.x, L2.L2 as t.y, L5.L5 as t.z ] |
| | | | ) [ t.x ] [ t.x, sys.count no nil (t.y) as L7.L7, sys.sum no nil (tin |
: yint[t.z] as t.z) as L10.L10 ], :
| | | | group by ( |
| | | | | project ( |
| | | | | | project ( |
| | | | | | | table(sys.foo) [ foo.a ] COUNT |
| | | | | | ) [ char "" as L3.L3, any "NULL" as L4.L4, sys.=(foo.a, smallint |
: "200") as L6.L6 ] :
| | | | | ) [ L3.L3 as t.x, boolean[L4.L4] as t.y, L6.L6 as t.z ] |
| | | | ) [ t.x ] [ t.x, sys.count no nil (t.y) as L7.L7, sys.sum no nil (tin |
: yint[t.z] as t.z) as L10.L10 ] :
| | | ) [ t.x, L7.L7, L10.L10 ] |
| | ) [ t.x ] [ t.x, sys.sum no nil (L7.L7) as L7.L7, sys.sum no nil (L10.L10 |
: ) as L10.L10 ] :
| ) [ L7 as L7.L7, L10 as L10.L10 ] |
+-----------------------------------------------------------------------------+
20 tuples (1.286ms)
sql>explain select count(y),sum(z) from (select '',false,a=200 from foo union all select '',null,a=200 from foo) as t(x,y,z) group by x;
+-----------------------------------------------------------------------------+
| mal |
+=============================================================================+
| function user.s15_1{autoCommit=true}(A0:str,A1:bit,A2:sht,A3:str,A4:void,A5 |
: :sht):void; :
| X_90:void := querylog.define("explain select count(y),sum(z) from (sele |
: ct \\'\\',false,a=200 from foo union all select \\'\\',null,a=200 from foo) :
: as t(x,y,z) group by x;","default_pipe",66); :
| barrier X_110 := language.dataflow(); |
| X_65 := bat.new(nil:oid,nil:str); |
| X_71 := bat.append(X_65,".L7"); |
| X_81 := bat.append(X_71,".L10"); |
| X_66 := bat.new(nil:oid,nil:str); |
| X_73 := bat.append(X_66,"L7"); |
| X_83 := bat.append(X_73,"L10"); |
| X_67 := bat.new(nil:oid,nil:str); |
| X_75 := bat.append(X_67,"wrd"); |
| X_85 := bat.append(X_75,"hugeint"); |
| X_68 := bat.new(nil:oid,nil:int); |
| X_77 := bat.append(X_68,64); |
| X_87 := bat.append(X_77,128); |
| X_70 := bat.new(nil:oid,nil:int); |
| X_79 := bat.append(X_70,0); |
| X_89 := bat.append(X_79,0); |
| X_9:bat[:oid,:wrd] := bat.new(nil:oid,nil:wrd); |
| X_8 := sql.mvc(); |
| X_12:bat[:oid,:oid] := sql.tid(X_8,"sys","foo"); |
| X_15:bat[:oid,:sht] := sql.bind(X_8,"sys","foo","a",0); |
| (X_18,r1_18) := sql.bind(X_8,"sys","foo","a",2); |
| X_21:bat[:oid,:sht] := sql.bind(X_8,"sys","foo","a",1); |
| X_23 := sql.delta(X_15,X_18,r1_18,X_21); |
| X_24 := algebra.leftfetchjoin(X_12,X_23); |
| X_25 := algebra.project(X_24,A1); |
| X_26 := algebra.project(X_24,A0); |
| (X_27,r1_29,r2_29) := group.subgroupdone(X_26); |
| X_30:bat[:oid,:wrd] := aggr.subcount(X_25,X_27,r1_29,true); |
| X_45 := algebra.leftfetchjoin(r1_29,X_26); |
| X_55:bat[:oid,:bit] := batcalc.==(X_24,A2); |
| X_56 := batcalc.bte(X_55); |
| X_57:bat[:oid,:hge] := aggr.subsum(X_56,X_27,r1_29,true,true); |
| X_31 := bat.append(X_9,X_30,true); |
| X_33 := sql.single(nil:bit); |
| X_34 := batcalc.bit(X_33); |
| X_35 := algebra.project(X_24,A3); |
| (X_36,r1_47,r2_47) := group.subgroupdone(X_35); |
| X_39:bat[:oid,:wrd] := aggr.subcount(X_34,X_36,r1_47,true); |
| X_47 := algebra.leftfetchjoin(r1_47,X_35); |
| X_59:bat[:oid,:bit] := batcalc.==(X_24,A5); |
| X_60 := batcalc.bte(X_59); |
| X_61:bat[:oid,:hge] := aggr.subsum(X_60,X_36,r1_47,true,true); |
| X_41 := bat.append(X_31,X_39,true); |
| X_42:bat[:oid,:str] := bat.new(nil:oid,nil:str); |
| X_46 := bat.append(X_42,X_45,true); |
| X_48 := bat.append(X_46,X_47,true); |
| (X_49,r1_60,r2_60) := group.subgroupdone(X_48); |
| X_52:bat[:oid,:wrd] := aggr.subsum(X_41,X_49,r1_60,true,true); |
| X_53:bat[:oid,:hge] := bat.new(nil:oid,nil:hge); |
| X_58 := bat.append(X_53,X_57,true); |
| X_62 := bat.append(X_58,X_61,true); |
| X_63:bat[:oid,:hge] := aggr.subsum(X_62,X_49,r1_60,true,true); |
| language.pass(X_26); |
| language.pass(X_27); |
| language.pass(r1_29); |
| language.pass(X_35); |
| language.pass(X_24); |
| language.pass(X_36); |
| language.pass(r1_47); |
| language.pass(X_49); |
| language.pass(r1_60); |
| exit X_110; |
| sql.resultSet(X_81,X_83,X_85,X_87,X_89,X_52,X_63); |
| end user.s15_1; |
+-----------------------------------------------------------------------------+
66 tuples (6.596ms)
Bizarrely, that's the simplest I can get the query; all further reductions I've tried from there make the problem go away.
I think that formally I should have used "cast(null as boolean)" instead of just plain "null", but this query works on Oct2014-SP4.
## Comment 21145
Date: 2015-08-14 12:39:13 +0200
From: @njnes
fixed handling of the auto-coersion of the NULL value into a boolean.
## Comment 21146
Date: 2015-08-14 12:42:22 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [bc6870273af0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bc6870273af0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bc6870273af0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bc6870273af0)
Changeset description:
added test for Bug #3787
## Comment 21147
Date: 2015-08-14 12:42:36 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [67ad185c24a5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=67ad185c24a5) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=67ad185c24a5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=67ad185c24a5)
Changeset description:
fixed bug #3787, ie handle NULL cast properly
## Comment 21176
Date: 2015-08-28 13:41:23 +0200
From: @sjoerdmullender
Jul2015 has been released.
| "b and g must be aligned" from complex group/union query | https://api.github.com/repos/MonetDB/MonetDB/issues/3787/comments | 0 | 2020-11-30T13:16:20Z | 2024-06-27T12:08:23Z | https://github.com/MonetDB/MonetDB/issues/3787 | 753,469,889 | 3,787 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-12 13:28:45 +0200
From: @hannesmuehleisen
To: clients devs <<bugs-clients>>
Version: 11.19.9 (Oct2014-SP2)
Last updated: 2015-08-28 13:42:37 +0200
## Comment 21124
Date: 2015-08-12 13:28:45 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:
The JDBC driver never tells the server to free result sets. This leads to result sets piling up for long-running connections and a steady growth of the dbfarm.
Reproducible: Always
### Steps to Reproduce:
1. Open a JDBC connection
2. Run many SELECT queries with large result sets on this connection
3. Actually call close() on result sets
### Actual Results:
dbfarm grows until the disk is full
### Expected Results:
No permanent increase in size
## Comment 21125
Date: 2015-08-12 13:32:21 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [bbd59fc85a93](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bbd59fc85a93) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bbd59fc85a93](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bbd59fc85a93)
Changeset description:
JDBC Driver: Send Xclose <queryid> on ResultSet.close() if required
This fixes Bug #3786
## Comment 21214
Date: 2015-08-28 13:42:37 +0200
From: @sjoerdmullender
Jul2015 has been released.
| ResultSet.close() never sends Xclose to free resources | https://api.github.com/repos/MonetDB/MonetDB/issues/3786/comments | 0 | 2020-11-30T13:16:17Z | 2024-06-27T12:08:22Z | https://github.com/MonetDB/MonetDB/issues/3786 | 753,469,861 | 3,786 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-12 13:09:18 +0200
From: Richard Hughes <<richard.monetdb>>
To: SQL devs <<bugs-sql>>
Version: 11.21.1 (Jul2015)
CC: @njnes
Last updated: 2015-08-28 13:42:53 +0200
## Comment 21122
Date: 2015-08-12 13:09:18 +0200
From: Richard Hughes <<richard.monetdb>>
Build is Jul2015 [92af99c05811](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=92af99c05811)
sql>create table foo (a timestamp,b timestamp);
operation successful (24.743ms)
sql>insert into foo values ('2000-1-1','2001-1-1');
1 affected row (22.329ms)
sql>select sum(b-a) from foo;
overflow in conversion of 31622400000 to bte.
sql>explain select sum(b-a) from foo;
+-----------------------------------------------------------------------------+
| mal |
+=============================================================================+
| function user.s17_1{autoCommit=true}():void; |
| X_32:void := querylog.define("explain select sum(b-a) from foo;","no_mi |
: tosis_pipe",22); :
| barrier X_45 := language.dataflow(); |
| X_2 := sql.mvc(); |
| X_3:bat[:oid,:oid] := sql.tid(X_2,"sys","foo"); |
| X_6:bat[:oid,:timestamp] := sql.bind(X_2,"sys","foo","b",0); |
| (X_9,r1_9) := sql.bind(X_2,"sys","foo","b",2); |
| X_12:bat[:oid,:timestamp] := sql.bind(X_2,"sys","foo","b",1); |
| X_14 := sql.delta(X_6,X_9,r1_9,X_12); |
| X_15 := algebra.leftfetchjoin(X_3,X_14); |
| X_16:bat[:oid,:timestamp] := sql.bind(X_2,"sys","foo","a",0); |
| (X_18,r1_18) := sql.bind(X_2,"sys","foo","a",2); |
| X_20:bat[:oid,:timestamp] := sql.bind(X_2,"sys","foo","a",1); |
| X_21 := sql.delta(X_16,X_18,r1_18,X_20); |
| X_22 := algebra.leftfetchjoin(X_3,X_21); |
| X_23:bat[:oid,:lng] := batmtime.diff(X_15,X_22); |
| X_24 := batcalc.bte(X_23); |
| X_25:hge := aggr.sum(X_24); |
| language.pass(X_3); |
| exit X_45; |
| sql.resultSet("sys.L1","L1","hugeint",128,0,7,X_25); |
| end user.s17_1; |
+-----------------------------------------------------------------------------+
22 tuples (2.742ms)
This worked in Oct2014-SP4.
## Comment 21123
Date: 2015-08-12 13:22:55 +0200
From: Richard Hughes <<richard.monetdb>>
Even simpler repro:
sql>select sum(i) from (select interval '1' day) x(i);
overflow in conversion of 86400000 to bte.
sql>explain select sum(i) from (select interval '1' day) x(i);
+-----------------------------------------------------------------------------+
| mal |
+=============================================================================+
| function user.s3_2{autoCommit=true}(A0:lng):void; |
| X_13:void := querylog.define("explain select sum(i) from (select interv |
: al \\'1\\' day) x(i);","default_pipe",7); :
| X_3 := sql.single(A0); |
| X_4 := batcalc.bte(X_3); |
| X_5:lng := aggr.sum(X_4); |
| sql.resultSet(".L1","L1","bigint",64,0,7,X_5); |
| end user.s3_2; |
| optimizer.mitosis() |
| optimizer.dataflow() |
+-----------------------------------------------------------------------------+
9 tuples (54.898ms)
## Comment 21129
Date: 2015-08-12 14:24:38 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [4bcdb422d056](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4bcdb422d056) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4bcdb422d056](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4bcdb422d056)
Changeset description:
added fix and test for bug #3785
## Comment 21131
Date: 2015-08-12 14:29:30 +0200
From: @njnes
added missing sum operators in the catalog
## Comment 21221
Date: 2015-08-28 13:42:53 +0200
From: @sjoerdmullender
Jul2015 has been released.
| sum(interval) causes overflow in conversion to bte | https://api.github.com/repos/MonetDB/MonetDB/issues/3785/comments | 0 | 2020-11-30T13:16:14Z | 2024-06-27T12:08:21Z | https://github.com/MonetDB/MonetDB/issues/3785 | 753,469,824 | 3,785 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-11 12:14:22 +0200
From: @hannesmuehleisen
To: SQL devs <<bugs-sql>>
Version: 11.19.3 (Oct2014)
Last updated: 2015-08-28 13:43:11 +0200
## Comment 21115
Date: 2015-08-11 12:14:22 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:
When running the following query, an assertion fails and kills mserver
SELECT t.rcl,SUM(ct) as t,SUM(cr) as r,SUM(ce) as tel, COUNT(*) as r1 FROM (select ct,cr,ce, case when ct = 0 then 0 when ct BETWEEN 1 AND 10000 then 1 when ct BETWEEN 10000 AND 50000 then 2 when ct BETWEEN 50000 AND 100000 then 3 when ct BETWEEN 100000 AND 200000 then 4 when ct BETWEEN 200000 AND 300000 then 5 when ct BETWEEN 300000 AND 500000 then 6 when ct BETWEEN 500000 AND 1000000 then 7 when ct BETWEEN 1000000 AND 2000000 then 8 when ct BETWEEN 2000000 AND 5000000 then 9 when ct BETWEEN 5000000 AND 10000000 then 10 when ct > 10000000 then 11 else 12 end as rcl from (SELECT reservedCid,ct,cr,ce FROM (SELECT jt.column1 as reservedCid,SUM(ri.column1) as ct,COUNT(ri.id) as cr,SUM(ri.el) as ce FROM Table3 as jt, (SELECT column3 as el, * FROM Table1) as ri WHERE (ri .column2 = 'R') AND jt.column2 = ri.id group by jt.column1) AS agg, Table2 AS contract WHERE agg.reservedCid = contract.id) as ft) as t GROUP BY t.rcl ORDER BY t.rcl;
Reproducible: Always
### Steps to Reproduce:
1. import from http://wikistats.ins.cwi.nl/lsde-data/schema-and-data-scanselect-assertion.sql.xz
2. run query above
3. crash
### Actual Results:
Crash
### Expected Results:
Some result or an error message
Here is a stack trace
frame 4: 0x000000010040259a libbat.12.dylib`BAT_scanselect(b=0x00000001051531d0, s=0x00000001051582e0, bn=0x0000000105172f20, tl=0x000000010419b570, th=0x000000010419b570, li=1, hi=1, equi=1, anti=0, lval=1, hval=1, maximum=358031, use_imprints=0) + 9002 at gdk_select.c:1008
frame 5: 0x00000001003fd54b libbat.12.dylib`BATsubselect(b=0x00000001051531d0, s=0x00000001051582e0, tl=0x000000010419b570, th=0x000000010419b570, li=1, hi=1, anti=0) + 36267 at gdk_select.c:1704
frame 6: 0x00000001000ec549 libmonetdb5.19.dylib`ALGsubselect2(result=0x0000000101092970, bid=0x0000000101092250, sid=0x00000001010921d0, low=0x000000010419b570, high=0x000000010419b570, li=0x0000000101090350, hi=0x0000000101090650, anti=0x0000000101090650) + 841 at algebra.c:341
## Comment 21117
Date: 2015-08-11 15:11:41 +0200
From: @sjoerdmullender
I couldn't initially reproduce this problem, but if I set the number of threads to 4, I could.
## Comment 21119
Date: 2015-08-11 15:41:36 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [fff94a9041d2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fff94a9041d2) 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=fff94a9041d2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fff94a9041d2)
Changeset description:
Off-by-one error.
p is incremented before the number of remaining items is calculated, a
calculation that involves p. Compensate for the early increment.
This fixes bug #3784.
## Comment 21234
Date: 2015-08-28 13:43:11 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Assertion failed: (bn->batCapacity >= cnt), function BAT_scanselect, file gdk_select.c, line 1008. | https://api.github.com/repos/MonetDB/MonetDB/issues/3784/comments | 0 | 2020-11-30T13:16:12Z | 2024-06-27T12:08:20Z | https://github.com/MonetDB/MonetDB/issues/3784 | 753,469,784 | 3,784 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-10 15:49:18 +0200
From: Richard Hughes <<richard.monetdb>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:41:56 +0200
## Comment 21113
Date: 2015-08-10 15:49:18 +0200
From: Richard Hughes <<richard.monetdb>>
The following query is a standard 'convert timestamp to UNIX time':
select now()-timestamp '1970-1-1';
On Oct2014-SP4 this gives:
sql>select now()-timestamp '1970-1-1';
+-------------------+
| current_timestamp |
+===================+
| 1439212945000 |
+-------------------+
1 tuple (1.520ms)
On Jul2015 [e25934221162](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e25934221162) this gives:
sql>select now()-timestamp '1970-1-1';
+-----------------------------------------------------------------------------+
| current_timestamp |
+=============================================================================+
| 1439212929.000 |
+-----------------------------------------------------------------------------+
1 tuple (1.414ms)
Was this silent behavioural change intentional?
The new result could be argued to be more correct (it's certainly better at hiding implementation details), but if you are going to stick with the change then please put a really big disclaimer in the release notes because I doubt I'm the only one who is going to get caught out.
A workaround appears to be "select cast(now()-timestamp '1970-1-1' as bigint);", which behaves the same on both versions.
(BTW, the epoch() function doesn't return milliseconds, so even in Jul2015 I won't be using it)
## Comment 21127
Date: 2015-08-12 14:20:03 +0200
From: @njnes
Yes its intentional and yes we should include a warning for this change.
## Comment 21130
Date: 2015-08-12 14:27:39 +0200
From: @sjoerdmullender
(In reply to Niels Nes from comment 1)
> Yes its intentional and yes we should include a warning for this change.
Then please add a changelog message to sql/ChangeLog.Jul2015 (use Maddlog -f ...).
## Comment 21157
Date: 2015-08-18 13:42:06 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8e113ab16cba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8e113ab16cba) 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=8e113ab16cba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8e113ab16cba)
Changeset description:
Add a changelog message.
Also see bug #3783.
## Comment 21195
Date: 2015-08-28 13:41:56 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Behavioural change in Jul2015 for 'timestamp minus timestamp' | https://api.github.com/repos/MonetDB/MonetDB/issues/3783/comments | 0 | 2020-11-30T13:16:09Z | 2024-06-27T12:08:19Z | https://github.com/MonetDB/MonetDB/issues/3783 | 753,469,760 | 3,783 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-08 09:45:32 +0200
From: Clint Cummins <<ccummins>>
To: SQL devs <<bugs-sql>>
Version: 11.17.17 (Jan2014-SP2)
CC: @njnes
Last updated: 2015-08-08 17:14:26 +0200
## Comment 21106
Date: 2015-08-08 09:45:32 +0200
From: Clint Cummins <<ccummins>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.130 Safari/537.36
Build Identifier:
Second ODBC batch query fails, with "HY000 General error", if it contains 2 or more SQL commands.
Reproducible: Always
### Steps to Reproduce:
1. Start first process, which uses ODBC interface to send a batch query via SQLExecDirect, and the batch query contains 2 or more SQL commands, such as "Create Table A1 as (query 1) with data; Create Table A2 as (query 2) with data;".
2. Start second process before batch query from first process finishes (easy to do if first query takes a few seconds to complete). Second process sends a similar query via SQLExecDirect with different tablenames: "Create Table B1 as (query 1) with data; Create Table B2 as (query 2) with data;".
### Actual Results:
First query succeeds.
Second query fails, with error "HY000 General error".
### Expected Results:
Both queries succeed.
If the queries contain only one SQL command each (for example if tables A2 and B2 are not created), they both succeed.
Are simultaneous batch queries supposed to work?
Or is it considered too complex to handle?
We might be able to work around it, but would like to know if this is intended to work.
## Comment 21110
Date: 2015-08-08 17:14:26 +0200
From: @njnes
this has to do with multi version concurrency control and MonetDB's coarse grain conflict detection (ie on a table/column level). Since all 4 statements update the catalog (which is stored in tables) it gives transaction conflicts. If the table creation is kept out side the concurrent statement ie just data copying, it
should work as you expect.
| concurrent ODBC batch (2+ commands) queries fail (SQLExecDirect) | https://api.github.com/repos/MonetDB/MonetDB/issues/3782/comments | 0 | 2020-11-30T13:16:06Z | 2024-06-28T13:14:44Z | https://github.com/MonetDB/MonetDB/issues/3782 | 753,469,723 | 3,782 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-08 04:27:58 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: ajdamico
Duplicates: #3378
Last updated: 2016-04-29 07:57:38 +0200
## Comment 21105
Date: 2015-08-08 04:27:58 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
hi, i think it'd be good to add a function to deal with boolean x non-integer numeric types
right now things crash unless you multiply by 1
SELECT: no such binary operator 'sql_mul(boolean,double)'
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE test (i INTEGER , d DOUBLE , b BOOLEAN);
INSERT INTO test VALUES ( 1 , 1.0 , TRUE ) ;
SELECT ( i * d ) FROM test ;
SELECT ( i * b ) FROM test ;
SELECT ( b * d ) FROM test ;
### Actual Results:
sql>CREATE TABLE test (i INTEGER , d DOUBLE , b BOOLEAN);
operation successful (8.904ms)
sql>INSERT INTO test VALUES ( 1 , 1.0 , TRUE ) ;
1 affected row (3.957ms)
sql>SELECT ( i * d ) FROM test ;
+--------------------------+
| sql_mul_i |
+==========================+
| 1 |
+--------------------------+
1 tuple (2.359ms)
sql>SELECT ( i * b ) FROM test ;
+-----------+
| sql_mul_i |
+===========+
| 1 |
+-----------+
1 tuple (1.351ms)
sql>SELECT ( b * d ) FROM test ;
SELECT: no such binary operator 'sql_mul(boolean,double)'
sql>
## Comment 22113
Date: 2016-04-29 07:57:38 +0200
From: Anthony Damico <<ajdamico>>
*** This bug has been marked as a duplicate of bug #3378 ***
| feature request: please allow boolean x double | https://api.github.com/repos/MonetDB/MonetDB/issues/3781/comments | 0 | 2020-11-30T13:16:04Z | 2024-06-28T07:19:46Z | https://github.com/MonetDB/MonetDB/issues/3781 | 753,469,695 | 3,781 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-08 04:22:55 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: ajdamico, martin.van.dinther, @njnes, till.wollenberg
Last updated: 2019-01-14 13:35:16 +0100
## Comment 21104
Date: 2015-08-08 04:22:55 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
sorry if i'm mistaking the usage of HAVING, but this works in SQLite so i'm confused why it's breaking in monetdb?
Reproducible: Always
### Steps to Reproduce:
CREATE TABLE bugexample (id INTEGER , value INTEGER);
INSERT INTO bugexample VALUES ( 1 , 1 ) , ( 2 , 2 ) , ( 2 , 2 ) ;
SELECT id FROM bugexample GROUP BY id HAVING id > 1;
SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id HAVING z > 1;
SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id HAVING z > 1;
### Actual Results:
sql>CREATE TABLE bugexample (id INTEGER , value INTEGER);
operation successful (12.075ms)
sql>INSERT INTO bugexample VALUES ( 1 , 1 ) , ( 2 , 2 ) , ( 2 , 2 ) ;
3 affected rows (5.528ms)
sql>
sql>SELECT id FROM bugexample GROUP BY id HAVING id > 1;
+------+
| id |
+======+
| 2 |
+------+
1 tuple (0.941ms)
sql>SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id HAVING z > 1;
SELECT: identifier 'z' unknown
sql>SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id HAVING z > 1;
SELECT: identifier 'z' unknown
sql>
### Expected Results:
read the dynamically-created column
## Comment 21108
Date: 2015-08-08 17:08:20 +0200
From: @njnes
the having is handled before the selection, ie the z alias isn't known jet.
## Comment 21109
Date: 2015-08-08 17:10:33 +0200
From: Anthony Damico <<ajdamico>>
sorry, i'm confused, how should this query be written?
## Comment 21112
Date: 2015-08-08 17:26:37 +0200
From: Anthony Damico <<ajdamico>>
hi, these queries work as a workaround, but i thought the whole point of HAVING was to filter a query *after* it had been generated?
SELECT z , id FROM ( SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id ) AS w GROUP BY id , z HAVING z > 1;
SELECT z , id FROM ( SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id ) AS w GROUP BY id , z HAVING z > 1;
the GROUP BY is necessary for the HAVING statement (so these commands do not work).. i don't understand the utility of HAVING if it cannot read an alias?
SELECT * FROM ( SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id ) AS w HAVING z > 1;
SELECT * FROM ( SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id ) AS w HAVING z > 1;
## Comment 21140
Date: 2015-08-13 15:39:57 +0200
From: Martin van Dinther <<martin.van.dinther>>
I think you are right in that the alias name should be usable in the HAVING clause, so I reopened this issue.
For the time being some possible workarounds are:
1) duplicate the aggregate-expression in the HAVING clause like:
SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id HAVING SUM(value) > 1;
SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id HAVING COUNT(*) > 1;
2) use aggregate query in the FROM-clause like:
SELECT z , id FROM ( SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id ) AS w WHERE z > 1;
SELECT z , id FROM ( SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id ) AS w WHERE z > 1;
These are a little different from your workarounds, as you do not need to GROUP twice.
3) use WITH-clause like:
WITH w as (SELECT id , SUM( value ) AS z FROM bugexample GROUP BY id) SELECT z , id FROM w WHERE z > 1;
WITH w as (SELECT id , COUNT(*) AS z FROM bugexample GROUP BY id) SELECT z , id FROM w WHERE z > 1;
4) create an aggregation VIEW once like:
CREATE VIEW w AS SELECT id, COUNT(*) AS count, SUM(value) AS sum_value FROM bugexample GROUP BY id;
and next use that view for all queries on the aggregate:
SELECT sum_value, id FROM w WHERE sum_value > 1;
SELECT count, id FROM w WHERE count > 1;
Thanks for reporting this issue/request.
| HAVING clause does not read AS columns? | https://api.github.com/repos/MonetDB/MonetDB/issues/3780/comments | 4 | 2020-11-30T13:16:02Z | 2024-06-28T07:19:46Z | https://github.com/MonetDB/MonetDB/issues/3780 | 753,469,664 | 3,780 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-08-03 23:31:24 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: ajdamico, @hannesmuehleisen
Last updated: 2015-08-28 13:41:32 +0200
## Comment 21095
Date: 2015-08-03 23:31:24 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
i am having a hard time figuring out how to make this example more minimal.
this problem first occurred on proprietary data, but i was able to reproduce the problem on the american community survey.
i tried to reproduce it on two smaller data sets, but the problem did not recur.
so i am not sure what is going on, but mserver5.exe just dies on me.
happens every time. it'll just take a bit of time to load the ACS. sorry
Reproducible: Always
### Steps to Reproduce:
LOAD the 2013 AMERICAN COMMUNITY SURVEY
options( "monetdb.sequential" = TRUE ) only windows users need this line
path.to.7z <- "7za" only macintosh and *nix users need this line
library(downloader)
setwd( "C:/My Directory/ACS/" )
single.year.datasets.to.download <- 2013
three.year.datasets.to.download <- NULL
five.year.datasets.to.download <- NULL
source_url( "https://raw.github.com/ajdamico/usgsd/master/American%20Community%20Survey/download%20all%20microdata.R" , prompt = FALSE , echo = TRUE )
once it's loaded on your computer, connect to it with these lines
library(MonetDB.R)
batfile <- "C:/My Directory/ACS/MonetDB/acs.bat" note for mac and *nix users: `acs.bat` might be `acs.sh` instead
second: run the MonetDB server
pid <- monetdb.server.start( batfile )
third: your five lines to make a monet database connection.
just like above, mine look like this:
dbname <- "acs"
dbport <- 50001
monet.url <- paste0( "monetdb://localhost:" , dbport , "/" , dbname )
db <- dbConnect( MonetDB.R() , monet.url , wait = TRUE )
once you are connected, this will cause the server to crash!
distinct_state <- sort( dbGetQuery( db , 'select distinct st from acs2013_1yr_m' )[ , 1 ] )
sql <-
paste0(
"CREATE TABLE test AS
( SELECT puma , serialno , " ,
paste0( "MAX( 1*( st = '" , distinct_state , "' ) ) AS thergrp_" , distinct_state , collapse = " , " ) ,
" FROM ( SELECT DISTINCT puma , serialno , st FROM acs2013_1yr_m ) AS z GROUP BY puma , serialno ) WITH DATA"
)
dbSendQuery( db , sql )
SERVER CRASHES
### Actual Results:
mserver5.exe dies
when i run with monetdb.debug.mapi = TRUE here's the output -- it crashes at the end of this. nothing informative.
> dbSendQuery( db , sql )
TX: 'sCREATE TABLE test AS
( SELECT puma , serialno , MAX( 1*( st = '1' ) ) AS thergrp_1 , MAX( 1*( st = '2' ) ) AS thergrp_2 , MAX( 1*( st = '4' ) ) AS thergrp_4 , MAX( 1*( st = '5' ) ) AS thergrp_5 , MAX( 1*( st = '6' ) ) AS thergrp_6 , MAX( 1*( st = '8' ) ) AS thergrp_8 , MAX( 1*( st = '9' ) ) AS thergrp_9 , MAX( 1*( st = '10' ) ) AS thergrp_10 , MAX( 1*( st = '11' ) ) AS thergrp_11 , MAX( 1*( st = '12' ) ) AS thergrp_12 , MAX( 1*( st = '13' ) ) AS thergrp_13 , MAX( 1*( st = '15' ) ) AS thergrp_15 , MAX( 1*( st = '16' ) ) AS thergrp_16 , MAX( 1*( st = '17' ) ) AS thergrp_17 , MAX( 1*( st = '18' ) ) AS thergrp_18 , MAX( 1*( st = '19' ) ) AS thergrp_19 , MAX( 1*( st = '20' ) ) AS thergrp_20 , MAX( 1*( st = '21' ) ) AS thergrp_21 , MAX( 1*( st = '22' ) ) AS thergrp_22 , MAX( 1*( st = '23' ) ) AS thergrp_23 , MAX( 1*( st = '24' ) ) AS thergrp_24 , MAX( 1*( st = '25' ) ) AS thergrp_25 , MAX( 1*( st = '26' ) ) AS thergrp_26 , MAX( 1*( st = '27' ) ) AS thergrp_27 , MAX( 1*( st = '28' ) ) AS thergrp_28 , MAX( 1*( st = '29' ) ) AS thergrp_29 , MAX( 1*( st = '30' ) ) AS thergrp_30 , MAX( 1*( st = '31' ) ) AS thergrp_31 , MAX( 1*( st = '32' ) ) AS thergrp_32 , MAX( 1*( st = '33' ) ) AS thergrp_33 , MAX( 1*( st = '34' ) ) AS thergrp_34 , MAX( 1*( st = '35' ) ) AS thergrp_35 , MAX( 1*( st = '36' ) ) AS thergrp_36 , MAX( 1*( st = '37' ) ) AS thergrp_37 , MAX( 1*( st = '38' ) ) AS thergrp_38 , MAX( 1*( st = '39' ) ) AS thergrp_39 , MAX( 1*( st = '40' ) ) AS thergrp_40 , MAX( 1*( st = '41' ) ) AS thergrp_41 , MAX( 1*( st = '42' ) ) AS thergrp_42 , MAX( 1*( st = '44' ) ) AS thergrp_44 , MAX( 1*( st = '45' ) ) AS thergrp_45 , MAX( 1*( st = '46' ) ) AS thergrp_46 , MAX( 1*( st = '47' ) ) AS thergrp_47 , MAX( 1*( st = '48' ) ) AS thergrp_48 , MAX( 1*( st = '49' ) ) AS thergrp_49 , MAX( 1*( st = '50' ) ) AS thergrp_50 , MAX( 1*( st = '51' ) ) AS thergrp_51 , MAX( 1*( st = '53' ) ) AS thergrp_53 , MAX( 1*( st = '54' ) ) AS thergrp_54 , MAX( 1*( st = '55' ) ) AS thergrp_55 , MAX( 1*( st = '56' ) ) AS thergrp_56 FROM ( SELECT DISTINCT puma , serialno , st FROM acs2013_1yr_m ) AS z GROUP BY puma , serialno ) WITH DATA
;'
RX: ''
An object of class "MonetDBResult"
Slot "env":
<environment: 0x0585f1ac>
### Expected Results:
a table not a crash :(
MonetDB 5 server v11.19.13 "Oct2014-SP4"
Serving database 'acs', using 4 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 64.000 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50001/
MonetDB/SQL module loaded
>
> sessionInfo()
R version 3.2.1 (2015-06-18)
Platform: i386-w64-mingw32/i386 (32-bit)
Running under: Windows Server 2008 R2 x64 (build 7601) Service Pack 1
locale:
[1] LC_COLLATE=English_United States.1252
[2] LC_CTYPE=English_United States.1252
[3] LC_MONETARY=English_United States.1252
[4] LC_NUMERIC=C
[5] LC_TIME=English_United States.1252
attached base packages:
[1] stats graphics grDevices utils datasets methods base
other attached packages:
[1] MonetDB.R_1.0.0 DBI_0.3.1
loaded via a namespace (and not attached):
[1] codetools_0.2-11 digest_0.6.8
## Comment 21100
Date: 2015-08-05 15:05:36 +0200
From: @hannesmuehleisen
Can't reproduce crash on Oct2014 with OSX. Will try on Windows next.
Offending Query:
CREATE TABLE test AS
( SELECT puma , serialno , MAX( 1*( st = '1' ) ) AS thergrp_1 , MAX( 1*( st = '2' ) ) AS thergrp_2 , MAX( 1*( st = '4' ) ) AS thergrp_4 , MAX( 1*( st = '5' ) ) AS thergrp_5 , MAX( 1*( st = '6' ) ) AS thergrp_6 , MAX( 1*( st = '8' ) ) AS thergrp_8 , MAX( 1*( st = '9' ) ) AS thergrp_9 , MAX( 1*( st = '10' ) ) AS thergrp_10 , MAX( 1*( st = '11' ) ) AS thergrp_11 , MAX( 1*( st = '12' ) ) AS thergrp_12 , MAX( 1*( st = '13' ) ) AS thergrp_13 , MAX( 1*( st = '15' ) ) AS thergrp_15 , MAX( 1*( st = '16' ) ) AS thergrp_16 , MAX( 1*( st = '17' ) ) AS thergrp_17 , MAX( 1*( st = '18' ) ) AS thergrp_18 , MAX( 1*( st = '19' ) ) AS thergrp_19 , MAX( 1*( st = '20' ) ) AS thergrp_20 , MAX( 1*( st = '21' ) ) AS thergrp_21 , MAX( 1*( st = '22' ) ) AS thergrp_22 , MAX( 1*( st = '23' ) ) AS thergrp_23 , MAX( 1*( st = '24' ) ) AS thergrp_24 , MAX( 1*( st = '25' ) ) AS thergrp_25 , MAX( 1*( st = '26' ) ) AS thergrp_26 , MAX( 1*( st = '27' ) ) AS thergrp_27 , MAX( 1*( st = '28' ) ) AS thergrp_28 , MAX( 1*( st = '29' ) ) AS thergrp_29 , MAX( 1*( st = '30' ) ) AS thergrp_30 , MAX( 1*( st = '31' ) ) AS thergrp_31 , MAX( 1*( st = '32' ) ) AS thergrp_32 , MAX( 1*( st = '33' ) ) AS thergrp_33 , MAX( 1*( st = '34' ) ) AS thergrp_34 , MAX( 1*( st = '35' ) ) AS thergrp_35 , MAX( 1*( st = '36' ) ) AS thergrp_36 , MAX( 1*( st = '37' ) ) AS thergrp_37 , MAX( 1*( st = '38' ) ) AS thergrp_38 , MAX( 1*( st = '39' ) ) AS thergrp_39 , MAX( 1*( st = '40' ) ) AS thergrp_40 , MAX( 1*( st = '41' ) ) AS thergrp_41 , MAX( 1*( st = '42' ) ) AS thergrp_42 , MAX( 1*( st = '44' ) ) AS thergrp_44 , MAX( 1*( st = '45' ) ) AS thergrp_45 , MAX( 1*( st = '46' ) ) AS thergrp_46 , MAX( 1*( st = '47' ) ) AS thergrp_47 , MAX( 1*( st = '48' ) ) AS thergrp_48 , MAX( 1*( st = '49' ) ) AS thergrp_49 , MAX( 1*( st = '50' ) ) AS thergrp_50 , MAX( 1*( st = '51' ) ) AS thergrp_51 , MAX( 1*( st = '53' ) ) AS thergrp_53 , MAX( 1*( st = '54' ) ) AS thergrp_54 , MAX( 1*( st = '55' ) ) AS thergrp_55 , MAX( 1*( st = '56' ) ) AS thergrp_56 FROM ( SELECT DISTINCT puma , serialno , st FROM acs2013_1yr_m ) AS z GROUP BY puma , serialno ) WITH DATA
Schema:
CREATE TABLE "sys"."acs2013_1yr_m" (
"rt" CHAR(1),
"serialno" INTEGER,
"division" INTEGER,
"puma" INTEGER,
"region" INTEGER,
"st" INTEGER,
"adjhsg" INTEGER,
"adjinc" INTEGER,
"wgtp" INTEGER,
"np" INTEGER,
"type_" INTEGER,
"access" INTEGER,
"acr" INTEGER,
"ags" INTEGER,
"bath" INTEGER,
"bdsp" INTEGER,
"bld" INTEGER,
"broadbnd" INTEGER,
"bus" INTEGER,
"compothx" INTEGER,
"conp" INTEGER,
"dialup" INTEGER,
"dsl" INTEGER,
"elep" INTEGER,
"fiberop" INTEGER,
"fs" INTEGER,
"fulp" INTEGER,
"gasp" INTEGER,
"handheld" INTEGER,
"hfl" INTEGER,
"insp" INTEGER,
"laptop" INTEGER,
"mhp" INTEGER,
"modem" INTEGER,
"mrgi" INTEGER,
"mrgp" INTEGER,
"mrgt" INTEGER,
"mrgx" INTEGER,
"othsvcex" INTEGER,
"refr" INTEGER,
"rmsp" INTEGER,
"rntm" INTEGER,
"rntp" INTEGER,
"rwat" INTEGER,
"rwatpr" INTEGER,
"satellite" INTEGER,
"sink" INTEGER,
"smp" INTEGER,
"stov" INTEGER,
"tel" INTEGER,
"ten" INTEGER,
"toil" INTEGER,
"vacs" INTEGER,
"valp" INTEGER,
"veh" INTEGER,
"watp" INTEGER,
"ybl" INTEGER,
"fes" INTEGER,
"ffincp" INTEGER,
"fgrntp" INTEGER,
"fhincp" INTEGER,
"fincp" INTEGER,
"fparc" INTEGER,
"fsmocp" INTEGER,
"grntp" INTEGER,
"grpip" INTEGER,
"hhl" INTEGER,
"hht" INTEGER,
"hincp" INTEGER,
"hugcl" INTEGER,
"hupac" INTEGER,
"hupaoc" INTEGER,
"huparc" INTEGER,
"kit" INTEGER,
"lngi" INTEGER,
"multg" INTEGER,
"mv" INTEGER,
"noc" INTEGER,
"npf" INTEGER,
"npp" INTEGER,
"nr" INTEGER,
"nrc" INTEGER,
"ocpip" INTEGER,
"partner" INTEGER,
"plm" INTEGER,
"psf" INTEGER,
"r18" INTEGER,
"r60" INTEGER,
"r65" INTEGER,
"resmode" INTEGER,
"smocp" INTEGER,
"smx" INTEGER,
"srnt" INTEGER,
"ssmc" INTEGER,
"sval" INTEGER,
"taxp" INTEGER,
"wif" INTEGER,
"wkexrel" INTEGER,
"workstat" INTEGER,
"faccessp" INTEGER,
"facrp" INTEGER,
"fagsp" INTEGER,
"fbathp" INTEGER,
"fbdsp" INTEGER,
"fbldp" INTEGER,
"fbroadbndp" INTEGER,
"fbusp" INTEGER,
"fcompothxp" INTEGER,
"fconp" INTEGER,
"fdialupp" INTEGER,
"fdslp" INTEGER,
"felep" INTEGER,
"ffiberopp" INTEGER,
"ffsp" INTEGER,
"ffulp" INTEGER,
"fgasp" INTEGER,
"fhandheldp" INTEGER,
"fhflp" INTEGER,
"finsp" INTEGER,
"fkitp" INTEGER,
"flaptopp" INTEGER,
"fmhp" INTEGER,
"fmodemp" INTEGER,
"fmrgip" INTEGER,
"fmrgp" INTEGER,
"fmrgtp" INTEGER,
"fmrgxp" INTEGER,
"fmvp" INTEGER,
"fothsvcexp" INTEGER,
"fplmp" INTEGER,
"frefrp" INTEGER,
"frmsp" INTEGER,
"frntmp" INTEGER,
"frntp" INTEGER,
"frwatp" INTEGER,
"frwatprp" INTEGER,
"fsatellitep" INTEGER,
"fsinkp" INTEGER,
"fsmp" INTEGER,
"fsmxhp" INTEGER,
"fsmxsp" INTEGER,
"fstovp" INTEGER,
"ftaxp" INTEGER,
"ftelp" INTEGER,
"ftenp" INTEGER,
"ftoilp" INTEGER,
"fvacsp" INTEGER,
"fvalp" INTEGER,
"fvehp" INTEGER,
"fwatp" INTEGER,
"fyblp" INTEGER,
"wgtp1" INTEGER,
"wgtp2" INTEGER,
"wgtp3" INTEGER,
"wgtp4" INTEGER,
"wgtp5" INTEGER,
"wgtp6" INTEGER,
"wgtp7" INTEGER,
"wgtp8" INTEGER,
"wgtp9" INTEGER,
"wgtp10" INTEGER,
"wgtp11" INTEGER,
"wgtp12" INTEGER,
"wgtp13" INTEGER,
"wgtp14" INTEGER,
"wgtp15" INTEGER,
"wgtp16" INTEGER,
"wgtp17" INTEGER,
"wgtp18" INTEGER,
"wgtp19" INTEGER,
"wgtp20" INTEGER,
"wgtp21" INTEGER,
"wgtp22" INTEGER,
"wgtp23" INTEGER,
"wgtp24" INTEGER,
"wgtp25" INTEGER,
"wgtp26" INTEGER,
"wgtp27" INTEGER,
"wgtp28" INTEGER,
"wgtp29" INTEGER,
"wgtp30" INTEGER,
"wgtp31" INTEGER,
"wgtp32" INTEGER,
"wgtp33" INTEGER,
"wgtp34" INTEGER,
"wgtp35" INTEGER,
"wgtp36" INTEGER,
"wgtp37" INTEGER,
"wgtp38" INTEGER,
"wgtp39" INTEGER,
"wgtp40" INTEGER,
"wgtp41" INTEGER,
"wgtp42" INTEGER,
"wgtp43" INTEGER,
"wgtp44" INTEGER,
"wgtp45" INTEGER,
"wgtp46" INTEGER,
"wgtp47" INTEGER,
"wgtp48" INTEGER,
"wgtp49" INTEGER,
"wgtp50" INTEGER,
"wgtp51" INTEGER,
"wgtp52" INTEGER,
"wgtp53" INTEGER,
"wgtp54" INTEGER,
"wgtp55" INTEGER,
"wgtp56" INTEGER,
"wgtp57" INTEGER,
"wgtp58" INTEGER,
"wgtp59" INTEGER,
"wgtp60" INTEGER,
"wgtp61" INTEGER,
"wgtp62" INTEGER,
"wgtp63" INTEGER,
"wgtp64" INTEGER,
"wgtp65" INTEGER,
"wgtp66" INTEGER,
"wgtp67" INTEGER,
"wgtp68" INTEGER,
"wgtp69" INTEGER,
"wgtp70" INTEGER,
"wgtp71" INTEGER,
"wgtp72" INTEGER,
"wgtp73" INTEGER,
"wgtp74" INTEGER,
"wgtp75" INTEGER,
"wgtp76" INTEGER,
"wgtp77" INTEGER,
"wgtp78" INTEGER,
"wgtp79" INTEGER,
"wgtp80" INTEGER,
"sporder" INTEGER,
"pwgtp" INTEGER,
"agep" INTEGER,
"cit" INTEGER,
"citwp" INTEGER,
"cow" INTEGER,
"ddrs" INTEGER,
"dear" INTEGER,
"deye" INTEGER,
"dout" INTEGER,
"dphy" INTEGER,
"drat" INTEGER,
"dratx" INTEGER,
"drem" INTEGER,
"eng" INTEGER,
"fer" INTEGER,
"gcl" INTEGER,
"gcm" INTEGER,
"gcr" INTEGER,
"hins1" INTEGER,
"hins2" INTEGER,
"hins3" INTEGER,
"hins4" INTEGER,
"hins5" INTEGER,
"hins6" INTEGER,
"hins7" INTEGER,
"intp" INTEGER,
"jwmnp" INTEGER,
"jwrip" INTEGER,
"jwtr" INTEGER,
"lanx" INTEGER,
"mar" INTEGER,
"marhd" INTEGER,
"marhm" INTEGER,
"marht" INTEGER,
"marhw" INTEGER,
"marhyp" INTEGER,
"mig" INTEGER,
"mil" INTEGER,
"mlpa" INTEGER,
"mlpb" INTEGER,
"mlpcd" INTEGER,
"mlpe" INTEGER,
"mlpfg" INTEGER,
"mlph" INTEGER,
"mlpi" INTEGER,
"mlpj" INTEGER,
"mlpk" INTEGER,
"nwab" INTEGER,
"nwav" INTEGER,
"nwla" INTEGER,
"nwlk" INTEGER,
"nwre" INTEGER,
"oip" INTEGER,
"pap" INTEGER,
"relp" INTEGER,
"retp" INTEGER,
"sch" INTEGER,
"schg" INTEGER,
"schl" INTEGER,
"semp" INTEGER,
"sex" INTEGER,
"ssip" INTEGER,
"ssp" INTEGER,
"wagp" INTEGER,
"wkhp" INTEGER,
"wkl" INTEGER,
"wkw" INTEGER,
"wrk" INTEGER,
"yoep" INTEGER,
"anc" INTEGER,
"anc1p" INTEGER,
"anc2p" INTEGER,
"decade" INTEGER,
"dis" INTEGER,
"drivesp" INTEGER,
"esp" INTEGER,
"esr" INTEGER,
"fod1p" INTEGER,
"fod2p" INTEGER,
"hicov" INTEGER,
"hisp" INTEGER,
"indp" INTEGER,
"jwap" INTEGER,
"jwdp" INTEGER,
"lanp" INTEGER,
"migpuma" INTEGER,
"migsp" INTEGER,
"msp" INTEGER,
"naicsp" VARCHAR(255),
"nativity" INTEGER,
"nop" INTEGER,
"oc" INTEGER,
"occp" INTEGER,
"paoc" INTEGER,
"pernp" INTEGER,
"pincp" INTEGER,
"pobp" INTEGER,
"povpip" INTEGER,
"powpuma" INTEGER,
"powsp" INTEGER,
"privcov" INTEGER,
"pubcov" INTEGER,
"qtrbir" INTEGER,
"rac1p" INTEGER,
"rac2p" INTEGER,
"rac3p" INTEGER,
"racaian" INTEGER,
"racasn" INTEGER,
"racblk" INTEGER,
"racnh" INTEGER,
"racnum" INTEGER,
"racpi" INTEGER,
"racsor" INTEGER,
"racwht" INTEGER,
"rc" INTEGER,
"sciengp" INTEGER,
"sciengrlp" INTEGER,
"sfn" INTEGER,
"sfr" INTEGER,
"socp" VARCHAR(255),
"vps" INTEGER,
"waob" INTEGER,
"fagep" INTEGER,
"fancp" INTEGER,
"fcitp" INTEGER,
"fcitwp" INTEGER,
"fcowp" INTEGER,
"fddrsp" INTEGER,
"fdearp" INTEGER,
"fdeyep" INTEGER,
"fdisp" INTEGER,
"fdoutp" INTEGER,
"fdphyp" INTEGER,
"fdratp" INTEGER,
"fdratxp" INTEGER,
"fdremp" INTEGER,
"fengp" INTEGER,
"fesrp" INTEGER,
"fferp" INTEGER,
"ffodp" INTEGER,
"fgclp" INTEGER,
"fgcmp" INTEGER,
"fgcrp" INTEGER,
"fhins1p" INTEGER,
"fhins2p" INTEGER,
"fhins3c" INTEGER,
"fhins3p" INTEGER,
"fhins4c" INTEGER,
"fhins4p" INTEGER,
"fhins5c" INTEGER,
"fhins5p" INTEGER,
"fhins6p" INTEGER,
"fhins7p" INTEGER,
"fhisp" INTEGER,
"findp" INTEGER,
"fintp" INTEGER,
"fjwdp" INTEGER,
"fjwmnp" INTEGER,
"fjwrip" INTEGER,
"fjwtrp" INTEGER,
"flanp" INTEGER,
"flanxp" INTEGER,
"fmarhdp" INTEGER,
"fmarhmp" INTEGER,
"fmarhtp" INTEGER,
"fmarhwp" INTEGER,
"fmarhyp" INTEGER,
"fmarp" INTEGER,
"fmigp" INTEGER,
"fmigsp" INTEGER,
"fmilpp" INTEGER,
"fmilsp" INTEGER,
"foccp" INTEGER,
"foip" INTEGER,
"fpap" INTEGER,
"fpernp" INTEGER,
"fpincp" INTEGER,
"fpobp" INTEGER,
"fpowsp" INTEGER,
"fprivcovp" INTEGER,
"fpubcovp" INTEGER,
"fracp" INTEGER,
"frelp" INTEGER,
"fretp" INTEGER,
"fschgp" INTEGER,
"fschlp" INTEGER,
"fschp" INTEGER,
"fsemp" INTEGER,
"fsexp" INTEGER,
"fssip" INTEGER,
"fssp" INTEGER,
"fwagp" INTEGER,
"fwkhp" INTEGER,
"fwklp" INTEGER,
"fwkwp" INTEGER,
"fwrkp" INTEGER,
"fyoep" INTEGER,
"pwgtp1" INTEGER,
"pwgtp2" INTEGER,
"pwgtp3" INTEGER,
"pwgtp4" INTEGER,
"pwgtp5" INTEGER,
"pwgtp6" INTEGER,
"pwgtp7" INTEGER,
"pwgtp8" INTEGER,
"pwgtp9" INTEGER,
"pwgtp10" INTEGER,
"pwgtp11" INTEGER,
"pwgtp12" INTEGER,
"pwgtp13" INTEGER,
"pwgtp14" INTEGER,
"pwgtp15" INTEGER,
"pwgtp16" INTEGER,
"pwgtp17" INTEGER,
"pwgtp18" INTEGER,
"pwgtp19" INTEGER,
"pwgtp20" INTEGER,
"pwgtp21" INTEGER,
"pwgtp22" INTEGER,
"pwgtp23" INTEGER,
"pwgtp24" INTEGER,
"pwgtp25" INTEGER,
"pwgtp26" INTEGER,
"pwgtp27" INTEGER,
"pwgtp28" INTEGER,
"pwgtp29" INTEGER,
"pwgtp30" INTEGER,
"pwgtp31" INTEGER,
"pwgtp32" INTEGER,
"pwgtp33" INTEGER,
"pwgtp34" INTEGER,
"pwgtp35" INTEGER,
"pwgtp36" INTEGER,
"pwgtp37" INTEGER,
"pwgtp38" INTEGER,
"pwgtp39" INTEGER,
"pwgtp40" INTEGER,
"pwgtp41" INTEGER,
"pwgtp42" INTEGER,
"pwgtp43" INTEGER,
"pwgtp44" INTEGER,
"pwgtp45" INTEGER,
"pwgtp46" INTEGER,
"pwgtp47" INTEGER,
"pwgtp48" INTEGER,
"pwgtp49" INTEGER,
"pwgtp50" INTEGER,
"pwgtp51" INTEGER,
"pwgtp52" INTEGER,
"pwgtp53" INTEGER,
"pwgtp54" INTEGER,
"pwgtp55" INTEGER,
"pwgtp56" INTEGER,
"pwgtp57" INTEGER,
"pwgtp58" INTEGER,
"pwgtp59" INTEGER,
"pwgtp60" INTEGER,
"pwgtp61" INTEGER,
"pwgtp62" INTEGER,
"pwgtp63" INTEGER,
"pwgtp64" INTEGER,
"pwgtp65" INTEGER,
"pwgtp66" INTEGER,
"pwgtp67" INTEGER,
"pwgtp68" INTEGER,
"pwgtp69" INTEGER,
"pwgtp70" INTEGER,
"pwgtp71" INTEGER,
"pwgtp72" INTEGER,
"pwgtp73" INTEGER,
"pwgtp74" INTEGER,
"pwgtp75" INTEGER,
"pwgtp76" INTEGER,
"pwgtp77" INTEGER,
"pwgtp78" INTEGER,
"pwgtp79" INTEGER,
"pwgtp80" INTEGER,
"one" INTEGER,
"idkey" INTEGER auto_increment
);
Data:
http://wikistats.ins.cwi.nl/lsde-data/acstbl.csv.bz2 (600MB, default delimiters)
## Comment 21101
Date: 2015-08-05 16:33:34 +0200
From: Anthony Damico <<ajdamico>>
https://youtu.be/tfQs7WbVse8?t=85
## Comment 21102
Date: 2015-08-05 16:35:50 +0200
From: @hannesmuehleisen
Confirmed this on Windows 7 with the Oct 2014 branch.
## Comment 21103
Date: 2015-08-05 16:51:30 +0200
From: @hannesmuehleisen
Works fine in Jul branch, used build from http://monetdb.cwi.nl/testweb/web/56485:aebfa751b214/MonetDB5-SQL-Installer-x86_64-aebfa751b214.msi
## Comment 21179
Date: 2015-08-28 13:41:32 +0200
From: @sjoerdmullender
Jul2015 has been released.
| server crashes on MAX() on SELECT DISTINCT something combo | https://api.github.com/repos/MonetDB/MonetDB/issues/3779/comments | 0 | 2020-11-30T13:15:58Z | 2024-06-27T12:08:15Z | https://github.com/MonetDB/MonetDB/issues/3779 | 753,469,621 | 3,779 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-28 16:01:22 +0200
From: @hannesmuehleisen
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2015-09-28 15:37:30 +0200
## Comment 21063
Date: 2015-07-28 16:01:22 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.107 Safari/537.36
Build Identifier:
Create a table on remote node, say
CREATE TABLE sometable_0(A BIGINT);
Insert some data
INSERT INTO SOMETABLE VALUES (42);
Add this table as a remote table on another node with a slightly wrong schema
CREATE REMOTE TABLE sometable_0 (A INTEGER) ON 'mapi:monetdb://.../...';
SELECT * FROM sometable_0;
Result: crash of remote node. Also, unhelpful error message on master node: "illegal input, not a JSON header (got '')"
Reproducible: Always
### Actual Results:
Crash
### Expected Results:
No crash, error should be thrown at remote table creation. Also, better error message on crash of remote node.
## Comment 21064
Date: 2015-07-28 16:04:04 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [317820b49de5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=317820b49de5) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=317820b49de5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=317820b49de5)
Changeset description:
Test case for Bug #3778
## Comment 21096
Date: 2015-08-05 12:32:20 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [87df8ec9d2ce](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=87df8ec9d2ce) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=87df8ec9d2ce](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=87df8ec9d2ce)
Changeset description:
added more defensive code to handle typos for the remote cases.
see bugs 3778 and 3754
## Comment 21098
Date: 2015-08-05 12:33:00 +0200
From: @njnes
added a check for proper types in the mvc_bind* code.
## Comment 21233
Date: 2015-08-28 13:43:10 +0200
From: @sjoerdmullender
Jul2015 has been released.
## Comment 21290
Date: 2015-09-28 15:37:17 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [56adbdf57769](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=56adbdf57769) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=56adbdf57769](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=56adbdf57769)
Changeset description:
renamed schemadiff.SQL.py to schemadiff.Bug-3778.SQL.py
## Comment 21291
Date: 2015-09-28 15:37:23 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [f15a56550f53](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f15a56550f53) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f15a56550f53](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f15a56550f53)
Changeset description:
added "canonical" stable output for tests schemadiff.Bug-3778 & copy_into.Bug-3813;
correct / expected output still needs to be approved / provided !
## Comment 21293
Date: 2015-09-28 15:37:30 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0b830207930c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0b830207930c) made by Stefan Manegold <Stefan.Manegold@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0b830207930c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0b830207930c)
Changeset description:
BugTracker-2015: activate "dormand(?)" / new tests schemadiff.Bug-3778 & copy_into.Bug-3813
| Crash on remote table schema mismatch | https://api.github.com/repos/MonetDB/MonetDB/issues/3778/comments | 0 | 2020-11-30T13:15:56Z | 2024-06-27T12:08:14Z | https://github.com/MonetDB/MonetDB/issues/3778 | 753,469,580 | 3,778 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-22 18:33:24 +0200
From: Marcin K <<marcin>>
To: clients devs <<bugs-clients>>
Version: 11.21.19 (Jul2015-SP4)
CC: martin.van.dinther
Last updated: 2018-10-11 18:01:25 +0200
## Comment 21045
Date: 2015-07-22 18:33:24 +0200
From: Marcin K <<marcin>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.132 Safari/537.36
Build Identifier:
When logged in to mclient and issuing select statement e.g. "select * from some_table;" mclient quits without any errors and no result printed to the screen.
When query does not select "directly" from that table e.g. in case where offending table is joined onto another table, mclinet works as expected and results are printed to the screen.
Reproducible: Always
### Steps to Reproduce:
1. log into mclient
2. issue select statement
### Actual Results:
Mclient quits.
### Expected Results:
Expected printed result from issued query.
## Comment 21060
Date: 2015-07-23 12:57:36 +0200
From: Martin van Dinther <<martin.van.dinther>>
Could you please provide a reproduction script with SQL create table statement, possibly some data (INSERT statements) which allow us to reproduce this problem.
Also does only mclient stop or also the mserver5 process?
## Comment 21305
Date: 2015-09-29 14:32:12 +0200
From: @sjoerdmullender
I would like to add that the scenario as described is tested thousands of times every single day, so is unlikely to fail. I'm not saying there is no bug (bugs are always possible), I'm saying the bug report is lacking sufficient detail.
## Comment 26637
Date: 2018-10-11 18:01:25 +0200
From: Martin van Dinther <<martin.van.dinther>>
Closing this old issue as we have no way to reproduce the issue.
| mclient quits when executing simple select statement for particular table. | https://api.github.com/repos/MonetDB/MonetDB/issues/3777/comments | 0 | 2020-11-30T13:15:53Z | 2024-06-28T13:14:43Z | https://github.com/MonetDB/MonetDB/issues/3777 | 753,469,546 | 3,777 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-22 14:38:54 +0200
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.17.21 (Jan2014-SP3)
Last updated: 2015-11-08 10:14:36 +0100
## Comment 21041
Date: 2015-07-22 14:38:54 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
Check and make sure that cute/paste/execute of MAL programs work again after the recent rendering changes.
Reproducible: Always
## Comment 21476
Date: 2015-11-08 10:14:36 +0100
From: @mlkersten
this should become a feature with low priority.
| MAL execution of rendered snippets | https://api.github.com/repos/MonetDB/MonetDB/issues/3776/comments | 0 | 2020-11-30T13:15:51Z | 2024-06-28T13:14:43Z | https://github.com/MonetDB/MonetDB/issues/3776 | 753,469,519 | 3,776 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-21 13:18:18 +0200
From: @hannesmuehleisen
To: SQL devs <<bugs-sql>>
Version: 11.19.3 (Oct2014)
CC: @njnes, @drstmane
Last updated: 2015-08-28 13:41:49 +0200
## Comment 21032
Date: 2015-07-21 13:18:18 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.132 Safari/537.36
Build Identifier:
Backslashes preceding the field separator lead to import failure in COPY INTO.
Reproducible: Always
### Steps to Reproduce:
start transaction;
create table whatgoodisadatabaseifyoucannotimport(a string, b integer);
copy 1 records into whatgoodisadatabaseifyoucannotimport from stdin using delimiters ' ','\n','';
asdf\ 42
rollback;
### Actual Results:
Failed to import table (and that's it)
### Expected Results:
Backslash should be read as literal backslash.
## Comment 21033
Date: 2015-07-21 13:33:04 +0200
From: @drstmane
Oct2014 was still a bit more elaborate on error messages:
sql>start transaction;
auto commit mode: off
sql>create table whatgoodisadatabaseifyoucannotimport(a string, b integer);
operation successful (0.515ms)
sql>copy 1 records into whatgoodisadatabaseifyoucannotimport from stdin using
more>delimiters ' ','\n','';
more>asdf\ 42
missing separator ' ' line 0 expecting 1 got 0 fields
failed to import table
sql>
These apparently got lost on the default branch before the Jul2015 branch was created ...
## Comment 21034
Date: 2015-07-21 13:58:22 +0200
From: @hannesmuehleisen
Same error when using the BEST EFFORT flag.
## Comment 21035
Date: 2015-07-21 17:19:54 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [5923731a420d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5923731a420d) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5923731a420d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5923731a420d)
Changeset description:
Test for Bug #3775
## Comment 21036
Date: 2015-07-22 09:07:22 +0200
From: @njnes
in copy into the '\' is treated as escape symbol. Looking into the missing error.
## Comment 21039
Date: 2015-07-22 10:20:38 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [b26c48634f0d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b26c48634f0d) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26c48634f0d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26c48634f0d)
Changeset description:
added tests for bugs 3775 and 3773
## Comment 21188
Date: 2015-08-28 13:41:49 +0200
From: @sjoerdmullender
Jul2015 has been released.
| COPY INTO: Backslash preceding field separator kills import | https://api.github.com/repos/MonetDB/MonetDB/issues/3775/comments | 0 | 2020-11-30T13:15:48Z | 2024-06-27T12:08:11Z | https://github.com/MonetDB/MonetDB/issues/3775 | 753,469,486 | 3,775 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-21 11:15:31 +0200
From: @yzchang
To: clients devs <<bugs-clients>>
Version: -- development
CC: @yzchang
Last updated: 2020-11-12 14:47:42 +0100
## Comment 21031
Date: 2015-07-21 11:15:31 +0200
From: @yzchang
mclient is unaware of merge/remote tables yet. Issues found so far:
1. '\d' command does not show merge/remote tables. Merge/remote tables should be added as new types of tables.
2. '\d <a merge table>' shows "CREATE TABLE" instead of "CREATE MERGE TABLE"
3. '\d <a remote table>' shows only the remote URL part of a remote table, e.g.:
sql>\d t5
mapi:monetdb://localhost:50000/test
4. results of 'mclient -D' do not include merge/remote tables
Documentation for how to create merge/remote tables are here:
https://www.monetdb.org/Documentation/Cookbooks/SQLrecipes/DataPartitioning
https://www.monetdb.org/Documentation/Cookbooks/SQLrecipes/DistributedQueryProcessing
## Comment 21044
Date: 2015-07-22 16:23:59 +0200
From: @sjoerdmullender
Changesets [91643b6a257e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=91643b6a257e) [f0ba0766ac53](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f0ba0766ac53) and [01cd8cd56d15](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=01cd8cd56d15) implement this feature.
Do they work satisfactorily?
## Comment 21054
Date: 2015-07-23 11:30:52 +0200
From: @yzchang
Thanks! Basic tests now produce expected results. How can I create a test for this? The queries + mclient commands used and the output are the following:
sql>CREATE TABLE t1 (i int);
operation successful (2.068ms)
sql>CREATE MERGE TABLE mt1 (t int);
operation successful (1.737ms)
sql>ALTER TABLE mt1 ADD TABLE t1;
operation successful (1.220ms)
sql>CREATE REMOTE TABLE rt1 (t int) on 'mapi:monetdb://localhost:50000/test';
operation successful (2.064ms)
sql>\d
MERGE TABLE sys.mt1
REMOTE TABLE sys.rt1
TABLE sys.t1
sql>\d mt1
CREATE MERGE TABLE "sys"."mt1" (
"t" INTEGER
);
sql>\d rt1
CREATE REMOTE TABLE "sys"."rt1" (
"t" INTEGER
) ON 'mapi:monetdb://localhost:50000/test';
sql>\D
START TRANSACTION;
SET SCHEMA "sys";
CREATE TABLE "sys"."t1" (
"i" INTEGER
);
CREATE MERGE TABLE "sys"."mt1" (
"t" INTEGER
);
CREATE REMOTE TABLE "sys"."rt1" (
"t" INTEGER
) ON 'mapi:monetdb://localhost:50000/test';
ALTER TABLE "sys"."mt1" ADD TABLE "t1";
COMMIT;
## Comment 21213
Date: 2015-08-28 13:42:32 +0200
From: @sjoerdmullender
Jul2015 has been released.
## Comment 21527
Date: 2015-11-16 16:06:21 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [95d728adb4b9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=95d728adb4b9) made by Jennie Zhang <y.zhang@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=95d728adb4b9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=95d728adb4b9)
Changeset description:
Added test for fixed bug #3774
## Comment 28259
Date: 2020-11-12 14:47:42 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [9711b482487e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9711b482487e) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=9711b482487e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=9711b482487e)
Changeset description:
Converted msqldump-merge-and-remote-tables.Bug-3774 test
| mclient is unaware of merge tables and remote tables | https://api.github.com/repos/MonetDB/MonetDB/issues/3774/comments | 0 | 2020-11-30T13:15:46Z | 2024-06-27T12:08:10Z | https://github.com/MonetDB/MonetDB/issues/3774 | 753,469,454 | 3,774 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-21 10:12:41 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:13 +0200
## Comment 21030
Date: 2015-07-21 10:12:41 +0200
From: @sjoerdmullender
compare the two plan:
create table x (y decimal(10,4));
plan quantile(y, 0.0) from x;
plan quantile(y, 0) from x;
The first works, the second doesn't. However both are questionable.
The first casts column y to double (why?), the second casts it to tinyint(!).
I think there should be no cast at all of column y, since quantiles are defined on all integer types (there may have to be some higher level magic to deal with decimals).
## Comment 21037
Date: 2015-07-22 10:08:30 +0200
From: @njnes
improved aggregation function resolution.
## Comment 21038
Date: 2015-07-22 10:20:37 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [b26c48634f0d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b26c48634f0d) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26c48634f0d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b26c48634f0d)
Changeset description:
added tests for bugs 3775 and 3773
## Comment 21040
Date: 2015-07-22 10:23:29 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [7bd0dd798226](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7bd0dd798226) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7bd0dd798226](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7bd0dd798226)
Changeset description:
when we cannot resolve a aggregation function on all types, fallback to
searching based on name, number of arguments and first argument type.
Solve bug #3773
## Comment 21206
Date: 2015-08-28 13:42:13 +0200
From: @sjoerdmullender
Jul2015 has been released.
| quantile(col, 0) and quantile(col, 1) fail | https://api.github.com/repos/MonetDB/MonetDB/issues/3773/comments | 0 | 2020-11-30T13:15:44Z | 2024-06-27T12:08:09Z | https://github.com/MonetDB/MonetDB/issues/3773 | 753,469,427 | 3,773 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-20 00:18:55 +0200
From: vera <<vera.matei>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:07 +0200
## Comment 21027
Date: 2015-07-20 00:18:55 +0200
From: vera <<vera.matei>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
A user can grant any role, even if that role was not assigned to him. The user can even grant the role to itself, which gives the user permissions that was not having previously.
Reproducible: Always
## Comment 21029
Date: 2015-07-20 21:41:57 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [2b167d2b527d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2b167d2b527d) made by Vera Matei <vera.matei@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2b167d2b527d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2b167d2b527d)
Changeset description:
Test for bug #3772.
## Comment 21046
Date: 2015-07-22 22:24:01 +0200
From: @njnes
fixed, ie now only monetdb user or role owner, or granted with admin can grant roles
## Comment 21202
Date: 2015-08-28 13:42:07 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Any user can grant a role. | https://api.github.com/repos/MonetDB/MonetDB/issues/3772/comments | 2 | 2020-11-30T13:15:41Z | 2024-06-27T12:08:08Z | https://github.com/MonetDB/MonetDB/issues/3772 | 753,469,406 | 3,772 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-19 23:29:12 +0200
From: vera <<vera.matei>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes, @yzchang
Last updated: 2015-10-17 12:40:53 +0200
## Comment 21026
Date: 2015-07-19 23:29:12 +0200
From: vera <<vera.matei>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
When a schema owner (which always has the right to SELECT, INSERT, CREATE, etc.) also assumes the monetdb role, it loses the right to SELECT, INSERT, UPDATE and DELETE, but it can still CREATE, ALTER or DROP tables. This only happens for schema owners and not for regular users. If a regular user assumes the monetdb role, he does get all the privileges on tables.
Reproducible: Always
## Comment 21028
Date: 2015-07-20 21:41:46 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [af031cf381f1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=af031cf381f1) made by Vera Matei <vera.matei@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=af031cf381f1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=af031cf381f1)
Changeset description:
Test for bug #3771. One test case does not fail, but it is included to support the bug description.
## Comment 21047
Date: 2015-07-22 22:31:19 +0200
From: @njnes
fixed, ie both role and user id's are used to check for schema ownership
## Comment 21165
Date: 2015-08-25 14:06:09 +0200
From: @yzchang
Although the bug is fixed for user created schemas, it doesn't work with the default "sys" schema. Re-open it. The existing corresponding test will be extended to cover the new case as well.
## Comment 21306
Date: 2015-09-29 14:35:35 +0200
From: @sjoerdmullender
Jennie, did you extend the test as promised?
## Comment 21312
Date: 2015-09-30 22:00:05 +0200
From: @yzchang
Sorry, it was actually Vera who said she will extend the test. Guess it was lost among the many things she was trying to do during the wrap up. I need to dig in the old communications how to extend the test. I put this on the top of my list.
## Comment 21351
Date: 2015-10-17 12:40:53 +0200
From: @yzchang
Checked with Niels, that similar queries don't work with the "sys" schema is a correct behaviour, not a bug. Therefore, change the status to resolved & fixed. Niels' earlier fix for the not-pre-created-schemas is already released in Jul2015.
The owner of the "sys" schema is the _user_ "monetdb", hence, granting the _role_ "monetDB" to another user doesn't give that user any rights about the "sys" schema. To pass admin rights to a user, the role "sysadmin" should be granted. Then the user will be able to create/drop/update/alter/etc tables in the "sys" schema.
To avoid future confusion, we should disallow granting a role which was automatically created for each user (with the same name as the user name).
| Owner of the schema loses rights if assumes the monetdb role. | https://api.github.com/repos/MonetDB/MonetDB/issues/3771/comments | 0 | 2020-11-30T13:15:39Z | 2024-06-27T12:08:07Z | https://github.com/MonetDB/MonetDB/issues/3771 | 753,469,367 | 3,771 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-19 22:29:32 +0200
From: 357416268
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: 357416268, @njnes
Last updated: 2015-08-28 13:42:49 +0200
## Comment 21025
Date: 2015-07-19 22:29:32 +0200
From: 357416268
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.134 Safari/537.36
Build Identifier:
1.
2.
Reproducible: Always
### Steps to Reproduce:
1.
create table uniquecatalog11(id bigint PRIMARY KEY
, targetid bigint
, ra_avg double
, decl_avg double
, flux_ref double
, datapoints int
, zone smallint
, x double
, y double
, z double
, INACTIVE BOOLEAN
);
2. create function neighbor30()
returns table (ra_avg double)
begin
declare table uzone (id bigint, ra_avg double);
insert into uzone select id, ra_avg from uniquecatalog11;
return table( select ra_avg
from uzone as u0
where id between 10 and 20
and ra_avg between 10 and 20
);
end;
### Actual Results:
monetdb crashed.
### Expected Results:
a udf defined successfully.
default and July branches are tested on.
## Comment 21050
Date: 2015-07-22 22:52:46 +0200
From: @njnes
added more protection against declared tables (as they do not have a schema)
## Comment 21051
Date: 2015-07-22 22:54:05 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [a0e705004156](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a0e705004156) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a0e705004156](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a0e705004156)
Changeset description:
fix for bug #3770, ie protect agains missing schema names
## Comment 21217
Date: 2015-08-28 13:42:49 +0200
From: @sjoerdmullender
Jul2015 has been released.
| combined conditions on declared table in User Defined Function definition crashes monetdb | https://api.github.com/repos/MonetDB/MonetDB/issues/3770/comments | 0 | 2020-11-30T13:15:37Z | 2024-06-27T12:08:06Z | https://github.com/MonetDB/MonetDB/issues/3770 | 753,469,337 | 3,770 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-17 13:03:36 +0200
From: tim.brown
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: martin.van.dinther, @njnes, tim.brown
Last updated: 2015-08-28 13:42:01 +0200
## Comment 21020
Date: 2015-07-17 13:03:36 +0200
From: tim.brown
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.134 Safari/537.36
Build Identifier:
When querying a view based on UNION ALL query, then grouping by a CASTed value in that query, the databases crashes with a SIGSEGV fault.
Reproducible: Always
### Steps to Reproduce:
1.Create tables union_a and union_b including a timestamp column mytimestamp
2.CREATE VIEW union_view AS SELECT * FROM union_a UNION ALL union_b
3.SELECT COUNT(*), CAST(mytimestamp AS date) AS mydate GROUP BY mydate
### Actual Results:
mclient and other tools report connection loss.
merovingian.log reports:
2015-07-17 11:47:06 MSG merovingian[44201]: database '<xxxxxxxxxx>' (44903) was killed by signal SIGSEGV
### Expected Results:
Produce record set. The expected set can be obtained by running the same query against a table instead of a view.
One of the test cases here shows the same behaviour, but I cannot find it in the bug tracker:
https://www.monetdb.org/pipermail/users-list/2013-May/006347.html
## Comment 21021
Date: 2015-07-17 13:11:59 +0200
From: tim.brown
Sorry, step 3 in steps to reproduce should read:
3.SELECT COUNT(*), CAST(mytimestamp AS date) AS mydate FROM union_view GROUP BY mydate
## Comment 21052
Date: 2015-07-22 23:04:44 +0200
From: @njnes
It seems we are unable to reproduce this. I get an error, ie in the last query, ie
SELECT: identifier 'mytimestamp' unknown
## Comment 21053
Date: 2015-07-23 10:05:09 +0200
From: tim.brown
Yes, I made a mistake in the steps to reproduce - see my first comment.
Full steps:
create table union_a (id bigint, mytimestamp timestamp);
create table union_b (id bigint, mytimestamp timestamp);
create view union_view as select * from union_a union all select * from union_b;
select count(*), cast(mytimestamp as date) as mydate from union_view group by mydate;
## Comment 21059
Date: 2015-07-23 12:37:27 +0200
From: Martin van Dinther <<martin.van.dinther>>
Is reproducable in default branch. With assertions enabled it fails with assertion failure:
>mserver5: ../../../dev/sql/server/rel_optimizer.c:3114: rel_push_aggr_down: Assertion `ne' failed.
## Comment 21079
Date: 2015-08-01 15:18:17 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=30d12a4105a0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0)
Changeset description:
Bug fixes
Bug #3759 fixed types of returned bats (ie use timestamps instead of lng) in modules/mal/clients.c
Bug #3769 fixed crash (triggered assert) by properly looking for referenced groupby columns in push aggr down
optimizer in rel_optimizer.c
Bug #3760 fixed correlated subquery handling in rel_select.c, ie merge only distinct expressions.
Bug #3761 fixed by properly adding the zero_or_one aggregation only when needed (ie when the cardinality of
the outer query is a column/table, ie when we expect one value per row for the subquery).
Bug #3364 fixed in sql_privileges.c, ie allow set role when role_id == auth_id (ie default role).
Bug #3365 fixed in sql_privileges.c, the sql_grant_table_privs always added 'all' privileges in one go
in rel_schema.c properly pass the login_id or role_id based on the 'from current_{role/user}'
part of the grant statement
Bug #3476 was already fixed by previous revoke / schema fixes.
in gdk/gdk_select.c fixed problem with anti select and nils (stop before first nil instead of last)
## Comment 21082
Date: 2015-08-01 16:17:09 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [4fc2c4e0adbe](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4fc2c4e0adbe) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4fc2c4e0adbe](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4fc2c4e0adbe)
Changeset description:
added test for bug #3769
## Comment 21083
Date: 2015-08-01 16:17:39 +0200
From: @njnes
properly look for referenced groupby columns in push aggr down
## Comment 21199
Date: 2015-08-28 13:42:01 +0200
From: @sjoerdmullender
Jul2015 has been released.
| SIGSEGV when combining a cast/column alias with a UNION ALL view | https://api.github.com/repos/MonetDB/MonetDB/issues/3769/comments | 0 | 2020-11-30T13:15:34Z | 2024-06-27T12:08:05Z | https://github.com/MonetDB/MonetDB/issues/3769 | 753,469,298 | 3,769 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-16 17:17:09 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes, @drstmane
Last updated: 2015-08-02 12:16:43 +0200
## Comment 21012
Date: 2015-07-16 17:17:09 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.125 Safari/537.36
Build Identifier:
MonetDB reports GDK reported error.
HEAPalloc: Insufficient space for HEAP of 1023836056551424 bytes.
HEAPalloc: Insufficient space for HEAP of 1023836056551424 bytes.
After running the following query;
CREATE TABLE "sys"."bloks" (
"network" INET,
"geoname_id" INTEGER,
"registered_country_geoname_id" INTEGER,
"represented_country_geoname_id" INTEGER,
"is_anonymous_proxy" BOOLEAN,
"is_satellite_provider" BOOLEAN,
"postal_code" CHAR(8),
"latitude" DOUBLE,
"longitude" DOUBLE
);
CREATE TABLE "sys"."portscan" (
"timestamp" BIGINT,
"ip" INET,
"port" INTEGER,
"closed" BOOLEAN
);
select * from bloks, portscan where network >>= ip limit 10;
GDK reported error.
HEAPalloc: Insufficient space for HEAP of 1023836056551424 bytes.
HEAPalloc: Insufficient space for HEAP of 1023836056551424 bytes.
My bloks table contains about 500MB worth of data, the portscan about 4GB. The system running the database has 8GB of memory. I'll try if I can get this query to work with a ordinary 'between'.
Reproducible: Always
MonetDB 5 server v11.22.0 (64-bit, 64-bit oids, 128-bit integers)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 7.8GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.30 2012-02-04 (compiled with 8.30)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e 11 Feb 2013)
libxml2: 2.8.0 (compiled with 2.8.0)
Compiled by: root@ditscan (x86_64-unknown-linux-gnu)
Compilation: gcc -O3 -pipe -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code -D_FORTIFY_SOURCE=2
Linking : /usr/bin/ld -m elf_x86_64
## Comment 21013
Date: 2015-07-16 18:31:43 +0200
From: @sjoerdmullender
You're asking for a cross product of 500MB * 4GB and then look at 10 entries. That's not going to fly since MonetDB first calculates this huge cross product.
## Comment 21014
Date: 2015-07-16 21:20:24 +0200
From: @skinkie
(In reply to Sjoerd Mullender from comment 1)
> You're asking for a cross product of 500MB * 4GB and then look at 10
> entries. That's not going to fly since MonetDB first calculates this huge
> cross product.
I have also attempted the following for a more moderately sized query based on decimal IP addresses, sadly bigint is required instead of an unsigned int32.
select * from portscand left join blocks on (ip between network and broadcast) limit 10;
This pattern isn't also not flying. If I would want to annotate the entire table with latitude and longitudes from blocks. What SQL pattern might fly for this operation?
## Comment 21015
Date: 2015-07-17 07:55:33 +0200
From: @drstmane
Stefan,
please be aware that the data type is completely irrelevant to the behaviour you report. Neither does the (CSV-?) storage size of your tables (at least by itself).
Your queries ask for a theta-join (non-equality join predicate) between two tables. With such predicates, tuples from each table are very likely to match with multiple tuples from the other table; hence, the join results is likely to be (much) larger than the larger of the two tables, possibly even close the size of the cross (Cartesian) product of both tables. If this does not fit in your systems address space of free disk space (which ever comes first), you cannot execute such queries (at least not with MonetDB).
Having said that, what matter are the number of tuples in both tables, and thus the number of tuples in their cross product, as well as the number of tuples (expected) in your inequality-join result.
If MonetDB is (was) able to estimate the inequality-join result size ( tuples), it would need to allocate result buffers "only" for this size; otherwise, it allocates result buffers for the potential cross product as result to avoid (multiple) expensive re-allocations while producing the actual result. As said above, if this doesn't fit, it fails as reported.
In your case, even if the plain join succeeds, the projection (large due to "select *") might still fail to fit entirely.
To be of any help, we'd at the very least need to know the *relevant* information about your query and your data:
- number of tuples in both tables
(my guess: their product is in the order of 1023836056551424/8 ?)
- number of (expected) tuples in the inequality-join result(s)
If you don't know the latter, you might want to try to calculate it via
select count(*) from bloks, portscan where network >>= ip;
or
select count(*) from portscand left join blocks on (ip between network and broadcast);
If these succeed, we also know that the plain join fits, but the projection doesn't.
If it fail, we know that the (MonetDB-estimated) plain join result does not fit.
## Comment 21016
Date: 2015-07-17 08:04:27 +0200
From: @drstmane
NB:
Why would you want to statically annotate the entire portscan table with lat & lon from bloks? This de-normalization just blows-up your storage footprint ...
What about simple creating a view like this:
create view portscan_lat_lon as (
select p.*, b.latitude, b.longitude
from portscan p join bloks b on b.network >>= p.ip
);
## Comment 21017
Date: 2015-07-17 10:32:17 +0200
From: @skinkie
Hi Stefan, thanks for your in depth reply. I would like to annotate the table because I must render the table as as CSV output for foreign processing, and use this output as input for geotile rendering in mapnik.
The number of rows in both tables:
sql>select count(*) from bloks;
+---------+
| L1 |
+=========+
| 9794888 |
+---------+
sql>select count(*) from portscan;
+-----------+
| L1 |
+===========+
| 104527599 |
+-----------+
Trying your suggested view, where timestamp 1435050437 should result in 113 entries.
select * from portscan p join bloks b on b.network >>= p.ip where timestamp = 1435050437; -- takes longer than writing this reply
create table portscans as select * from portscan where timestamp = 1435050437 with data;
select * from portscans p left join bloks b on b.network >>= p.ip; -- also doesn't complete
The requested counts do not complete.
What properties do I know from the bloks table? I am assuming that the input data in the network field should be non-overlapping. Therefore the result of the (left) join should only result into a maximum rows of table portscan.
When writing a very specific IPv4 only solution I would end up with a index of: 9794888 (rows) * 4byte (struct addr_in / uint32_t) * 3 (network, broadcast, index). ~120MB, this index should be sorted. For each entry in my portscan table I can do a linear scan where network <= needle <= broadcast , or more optimised: a modified binary search resulting in at least the left nearest neighbor, where the result is validated with network <= needle <= broadcast.
Removing the inet performance out of the equation:
select * from blocks where 2563895902 between network and broadcast;
1 tuple (46.315ms) ~ 1 tuple (141.797ms)
sql>select * from blocks, portscand where ip between network and broadcast and timestamp = 1435050437;
97 tuples (24.8s)
Why would individual point queries be about 5x faster? I have attached some SQL traces in order to answer the question.
## Comment 21018
Date: 2015-07-17 10:32:50 +0200
From: @skinkie
Created attachment 343
Point query
> Attached file: [trace-single.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3768_trace-single.txt_343) (text/plain, 342914 bytes)
> Description: Point query
## Comment 21019
Date: 2015-07-17 10:33:11 +0200
From: @skinkie
Created attachment 344
Join query
> Attached file: [trace-join.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3768_trace-join.txt_344) (text/plain, 396506 bytes)
> Description: Join query
## Comment 21022
Date: 2015-07-17 13:36:40 +0200
From: @drstmane
This reveals (quite) a bit:
sql>explain select count(*) from bloks, portscan where network >>= ip;
+-------------------------------------------------------------------------------------------------+
| mal |
+=================================================================================================+
| function user.s6_1{autoCommit=true}():void; |
| barrier X_69 := language.dataflow(); |
| X_2 := sql.mvc(); |
| X_3:bat[:oid,:oid] := sql.tid(X_2,"sys","bloks"); |
| X_6:bat[:oid,:inet] := sql.bind(X_2,"sys","bloks","network",0); |
| (X_9,r1_9) := sql.bind(X_2,"sys","bloks","network",2); |
| X_12:bat[:oid,:inet] := sql.bind(X_2,"sys","bloks","network",1); |
| X_14 := sql.delta(X_6,X_9,r1_9,X_12); |
| X_15 := algebra.leftfetchjoin(X_3,X_14); |
| X_16:bat[:oid,:oid] := sql.tid(X_2,"sys","portscan"); |
| X_18:bat[:oid,:lng] := sql.bind(X_2,"sys","portscan","timestamp",0); |
| (X_20,r1_20) := sql.bind(X_2,"sys","portscan","timestamp",2); |
| X_22:bat[:oid,:lng] := sql.bind(X_2,"sys","portscan","timestamp",1); |
| X_23 := sql.delta(X_18,X_20,r1_20,X_22); |
| X_24 := algebra.leftfetchjoin(X_16,X_23); |
| (X_25,r1_25) := algebra.crossproduct(X_15,X_24); |
| X_27 := algebra.leftfetchjoin(X_25,X_15); |
| X_28:bat[:oid,:inet] := sql.bind(X_2,"sys","portscan","ip",0); |
| (X_30,r1_30) := sql.bind(X_2,"sys","portscan","ip",2); |
| X_32:bat[:oid,:inet] := sql.bind(X_2,"sys","portscan","ip",1); |
| X_33 := sql.delta(X_28,X_30,r1_30,X_32); |
| X_34:bat[:oid,:inet] := algebra.leftfetchjoinPath(r1_25,X_16,X_33); |
| X_35:bat[:oid,:bit] := mal.manifold("inet",">>=",X_27,X_34); |
| X_39 := algebra.subselect(X_35,true,true,true,true,false); |
| X_41 := algebra.leftfetchjoin(X_39,X_27); |
| X_42 := aggr.count(X_41); |
| language.pass(X_15); |
| language.pass(X_16); |
| language.pass(X_27); |
| exit X_69; |
| sql.exportValue(1,"sys.L1","L1","wrd",64,0,7,X_42,""); |
| end s6_1; |
| querylog.define("select count(*) from bloks, portscan where network >>= ip;","default_pipe") |
+-------------------------------------------------------------------------------------------------+
33 tuples (1.977ms)
a) MonetDB indeed chooses to first build a cross product and then filter that with the join predicate.
b) There is no "bulk" implementation for the ">>=" operation on type inet; hence, "manifold" kicks in iterating over the values, making is slow.
For the latter (b), please file a feature request.
For the former (a) similarly *might* be due to the fact that there is no ">>=" specific theta-join implementation; using a generic theta-join evaluating ">>=" as function call for each element in the cross product would save the matrialization of the entire cross product, but would be just as slow as filtering the cross product without bulk ">>=" implementation.
## Comment 21023
Date: 2015-07-17 13:51:33 +0200
From: @drstmane
NB:
What is the primary key (if any) of your portscan table?
May I assume that portscan.ip is not unique, i.e., the same ip occurs more than once?
May I assume that you want exactly one (lat,lon) per ip?
May I assume that bloks.network is unique?
May I also assume that with network >>= ip, each (distinct) portscan.ip matches exactly one bloks.network?
(if not, you'd get multiple matches per ip, i.e., your "annotation" would enlarge the portscan table .. !???)
What about (something like) this
select p.*, pb.lat, pb.lon
from
(
select pi.ip, b.lat, b.lon -- add more columns of bloks as you need
from
-- reduced theta-join or cross product only for unique/distinct ip values
( select distinct ip from portscan ) as pi
join
bloks as b
on b.network >>= p.ip
) as pb
join
portscan p
on p.ip = pb.ip -- (hopefully) efficient (n:1) equi-join;
;
## Comment 21024
Date: 2015-07-17 14:00:00 +0200
From: @skinkie
(In reply to Stefan Manegold from comment 9)
> What is the primary key (if any) of your portscan table?
>
> May I assume that portscan.ip is not unique, i.e., the same ip occurs more
> than once?
The scan is done in random order for ip-port pairs. The same ip occurs multiple times for multiple timestamps finding open or closed ports at these times.
> May I assume that you want exactly one (lat,lon) per ip?
Yes, the reason for denormalisation of 'IP' was merely because a pointer to an upstream table might have been more expensive (if I could have shrunken it down to INTEGER datatypes).
> May I assume that bloks.network is unique?
I assume the same, if this is not the case the source data is just not idiot proof.
> May I also assume that with network >>= ip, each (distinct) portscan.ip
> matches exactly one bloks.network?
> (if not, you'd get multiple matches per ip, i.e., your "annotation" would
> enlarge the portscan table .. !???)
I found that not all IPs have an annotated locations, the data is sparse. Thus I think correctly speaking: matches at most one network.
I think MonetDB has eaten my SSH daemon, I'll come back shortly with the suggested query.
## Comment 21093
Date: 2015-08-02 12:16:43 +0200
From: @njnes
A single join condition of b.network >>= p.ip will always result in a cross product. This because we do not have advanced join operators on the >>= operator.
You could add this in the form of a join filter operation. So this is at most a
feature request..
| inet types join result in Insufficient space for HEAP | https://api.github.com/repos/MonetDB/MonetDB/issues/3768/comments | 0 | 2020-11-30T13:15:31Z | 2024-06-28T13:14:42Z | https://github.com/MonetDB/MonetDB/issues/3768 | 753,469,262 | 3,768 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-15 23:58:42 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:41:39 +0200
## Comment 21010
Date: 2015-07-15 23:58:42 +0200
From: @yzchang
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
When create a TEMP TABLE using "LIKE" to define its columns gives _no_ result, neither an error nor "operation successful"
Reproducible: Always
### Steps to Reproduce:
1. Run the following queries:
sql>create table t1 (i int);
operation successful (25.500ms)
sql>create temp table tmp (like t1);
sql>select * from tmp;
SELECT: no such table 'tmp'
### Actual Results:
nothing at all
### Expected Results:
Either an error, or "operation successful"
## Comment 21011
Date: 2015-07-16 00:04:59 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [db6edcd1218a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=db6edcd1218a) made by Jennie Zhang <y.zhang@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=db6edcd1218a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=db6edcd1218a)
Changeset description:
Added (and enabled :)) test for bug #3767
## Comment 21043
Date: 2015-07-22 16:20:47 +0200
From: @njnes
with in the tmp schema, the table t1 isn't know, ie the create statement should have failed. Which it now does..
## Comment 21181
Date: 2015-08-28 13:41:39 +0200
From: @sjoerdmullender
Jul2015 has been released.
| CREATE TEMP TABLE using "LIKE" incorrectly handled | https://api.github.com/repos/MonetDB/MonetDB/issues/3767/comments | 0 | 2020-11-30T13:15:28Z | 2024-06-27T12:08:03Z | https://github.com/MonetDB/MonetDB/issues/3767 | 753,469,234 | 3,767 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-15 16:07:32 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes, @yzchang
Last updated: 2015-08-28 13:42:58 +0200
## Comment 21002
Date: 2015-07-15 16:07:32 +0200
From: @yzchang
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:39.0) Gecko/20100101 Firefox/39.0
Build Identifier:
[This also happens in Jul2015]
In the following mclient session, although it reports "CREATE VIEW tst.v1..." succeeded (note the schema 'tst' which is different than the current schema 'sys'), SELECT from tst.v1 says "no such table". Also, the view is not found in the SQL catalogue.
sql>create table t1 (i int);
operation successful (1.891ms)
sql>create schema tst;
operation successful (1.226ms)
sql>create view tst.v1 (i) as select * from t1;
operation successful (1.142ms)
sql>select * from tst.v1;
SELECT: no such table 'v1'
sql>select * from _tables where name like '%v1%';
+----+------+-----------+-------+------+--------+---------------+--------+
| id | name | schema_id | query | type | system | commit_action | access |
+====+======+===========+=======+======+========+===============+========+
+----+------+-----------+-------+------+--------+---------------+--------+
0 tuples (3.210ms)
It doesn't helpt to switch to the other schema 'tst':
sql>set schema tst;
auto commit mode: on
sql>select * from v1;
SELECT: no such table 'v1'
sql>select * from tst.v1;
SELECT: no such table 'v1'
However, if one first switches to the other schema 'tst', and create the view. Then the view is visible in both 'tst' and 'sys'. Also, tst.v1 is added to the SQL catalogue:
sql>set schema tst;
auto commit mode: on
sql>create view v1 (i) as select * from sys.t1;
operation successful (2.324ms)
sql>select * from v1;
+---+
| i |
+===+
+---+
0 tuples (3.655ms)
sql>set schema sys;
auto commit mode: on
sql>select * from tst.v1;
+---+
| i |
+===+
+---+
0 tuples (2.598ms)
sql>select * from _tables where name like '%v1%';
+------+------+-----------+---------------------------------------------+------+--------+---------------+--------+
| id | name | schema_id | query | type | system | commit_action | access |
+======+======+===========+=============================================+======+========+===============+========+
| 7377 | v1 | 7371 | create view v1 (i) as select * from sys.t1; | 1 | false | 0 | 0 |
+------+------+-----------+---------------------------------------------+------+--------+---------------+--------+
1 tuple (5.581ms)
Reproducible: Always
### Steps to Reproduce:
1. Run the following queries to reproduce the problem:
create table t1 (i int);
create schema tst;
create view tst.v1 (i) as select * from t1;
select * from tst.v1;
select * from _tables where name like '%v1%';
### Actual Results:
1st select query: error
2nd select query: empty results
### Expected Results:
sql>select * from tst.v1;
+---+
| i |
+===+
+---+
0 tuples (2.598ms)
sql>select * from _tables where name like '%v1%';
+------+------+-----------+---------------------------------------------+------+--------+---------------+--------+
| id | name | schema_id | query | type | system | commit_action | access |
+======+======+===========+=============================================+======+========+===============+========+
| 7377 | v1 | 7371 | create view v1 (i) as select * from sys.t1; | 1 | false | 0 | 0 |
+------+------+-----------+---------------------------------------------+------+--------+---------------+--------+
1 tuple (5.581ms)
## Comment 21004
Date: 2015-07-15 16:26:33 +0200
From: @yzchang
This bug is related to Bug #3708, but is slightly different.
Bug #3708 is about creating a view V for schema2 under schema2, and then try to access schema2.V in schema1. This works now, as is also shown in my mclient session.
This bug is about creating a viw V for schema2 under schema1 (!), and then try to access schema2.V in schema1 will result in an error.
If it's not allowed to create views for a different schema than the current schema, then the CREATE VIEW statement should return an error.
## Comment 21005
Date: 2015-07-15 16:38:12 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0e35d49441c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0e35d49441c9) made by Jennie Zhang <y.zhang@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0e35d49441c9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0e35d49441c9)
Changeset description:
Added test for Bug #3766
## Comment 21009
Date: 2015-07-15 17:20:43 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0d892d399f1e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0d892d399f1e) 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=0d892d399f1e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0d892d399f1e)
Changeset description:
Enable test for bug #3766.
## Comment 21042
Date: 2015-07-22 15:23:45 +0200
From: @njnes
the create view should have failed, as the t1 table is never reachable from the tst schema. We now properly detect that, ie use the proper schema to execute the sub-(view)-query
## Comment 21061
Date: 2015-07-24 14:41:38 +0200
From: @yzchang
Hai Niels,
When processing "create view tst.v1" do you switch current_schema to "tst" underwater? Because, now
create view tst.v1 (i) as select * from t1;
will return "SELECT: no such table 't1'", while
create view tst.v1 (i) as select * from sys.t1;
will succeed (as it should).
Is this expected behaviour? So even if I'm still in schema "sys", I have to explicitly identify t1 with sys.t1?
Jennie
## Comment 21225
Date: 2015-08-28 13:42:58 +0200
From: @sjoerdmullender
Jul2015 has been released.
| VIEW not visible if created under a different schema | https://api.github.com/repos/MonetDB/MonetDB/issues/3766/comments | 0 | 2020-11-30T13:15:25Z | 2024-06-27T12:08:02Z | https://github.com/MonetDB/MonetDB/issues/3766 | 753,469,207 | 3,766 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-14 14:36:42 +0200
From: vera <<vera.matei>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:16 +0200
## Comment 20999
Date: 2015-07-14 14:36:42 +0200
From: vera <<vera.matei>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
If for a user a privilege was granted (e.g. SELECT) and then revoked, if the privilege is then again regranted (on the same table), it seems to not have any effect. That is, the user gets an error (ungranted privilege) if it tries to use it.
Reproducible: Always
## Comment 21000
Date: 2015-07-14 14:44:35 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0a177ab017e9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0a177ab017e9) made by Vera Matei <vera.matei@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0a177ab017e9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0a177ab017e9)
Changeset description:
A test for bug #3765.
## Comment 21048
Date: 2015-07-22 22:32:32 +0200
From: @njnes
rights were not properly revoked
## Comment 21208
Date: 2015-08-28 13:42:16 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Re-granting a revoked privilege does not work | https://api.github.com/repos/MonetDB/MonetDB/issues/3765/comments | 0 | 2020-11-30T13:15:23Z | 2024-06-27T12:08:01Z | https://github.com/MonetDB/MonetDB/issues/3765 | 753,469,184 | 3,765 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-14 09:44:14 +0200
From: vera <<vera.matei>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:47 +0200
## Comment 20997
Date: 2015-07-14 09:44:14 +0200
From: vera <<vera.matei>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
Usually dropping more than two users makes the whole system crash.
The message in the merovingian.log file is: "database 'newdb' (25230) was killed by signal SIGABRT".
Reproducible: Always
## Comment 21049
Date: 2015-07-22 22:33:14 +0200
From: @njnes
mal_authorize wasn't move to the headless setup.
## Comment 21216
Date: 2015-08-28 13:42:47 +0200
From: @sjoerdmullender
Jul2015 has been released.
| DROPping multiple users causes a crash | https://api.github.com/repos/MonetDB/MonetDB/issues/3764/comments | 0 | 2020-11-30T13:15:20Z | 2024-06-27T12:08:00Z | https://github.com/MonetDB/MonetDB/issues/3764 | 753,469,158 | 3,764 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-10 09:47:50 +0200
From: Vijay Krishna <<vijayakrishna55>>
To: clients devs <<bugs-clients>>
Version: 11.19.15 (Oct2014-SP4)
CC: vijayakrishna55, @yzchang
Last updated: 2015-08-28 13:42:41 +0200
## Comment 20989
Date: 2015-07-10 09:47:50 +0200
From: Vijay Krishna <<vijayakrishna55>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
Build Identifier:
While inserting a row into a table with (at least) 14 Foreign keys using JDBC Prepared Statement, the database is getting stopped.
Works fine for tables with less than 13 FKs..
The insert operation fails and the mserver has to be restarted to bring back the system to normalcy.
The same insert works fine for the table with 14 FKs when done through mclient manually.
Reproducible: Always
### Steps to Reproduce:
1.Create a table that has 14 foreign keys.
2.Insert a row through JDBC Prepared Statement for this table.
3.While executing the line connection.prepareStatement(sqlString) the database crashes.
If you are using a Java IDE (like Eclipse), try testing this with a debugger at the mentioned line.
The debugger goes off for a long time.. It get returned directly to the exception catch block from this line..
The exception would be "java.sql.SQLException: Unable to connect (localhost:50000): Connection to server lost!"
This exception is thrown after the database has been killed.. There is no trace for why its being killed..
## Comment 20990
Date: 2015-07-10 15:38:43 +0200
From: @yzchang
Hai Vijay,
Thanks for firing the bug report.
Can you please also provide us the schema and the java test program?
Also, can you please run the MonetDB server with GDB to catch where the server has crashed? You may need to recompile monetdb with the --enable-debug option.
Thanks!
Regards,
Jennie
## Comment 20995
Date: 2015-07-14 06:20:56 +0200
From: Vijay Krishna <<vijayakrishna55>>
Created attachment 342
Sample java code
> Attached file: [testMonetFK.java](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3763_testMonetFK.java_342) (application/octet-stream, 1322 bytes)
> Description: Sample java code
## Comment 20996
Date: 2015-07-14 06:24:27 +0200
From: Vijay Krishna <<vijayakrishna55>>
The schema is simple and straight forward as follows.. Had 20 tables and a relationship table..
$ ./bin/mclient -d fkTestDB
Welcome to mclient, the MonetDB/SQL interactive terminal (Jan2014)
Database: MonetDB v11.17.9 (Jan2014), 'mapi:monetdb://vijay-1833:50000/fkTestDB'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>\d
TABLE sys.reltable
TABLE sys.table1
TABLE sys.table10
TABLE sys.table11
TABLE sys.table12
TABLE sys.table13
TABLE sys.table14
TABLE sys.table15
TABLE sys.table16
TABLE sys.table17
TABLE sys.table18
TABLE sys.table19
TABLE sys.table2
TABLE sys.table20
TABLE sys.table3
TABLE sys.table4
TABLE sys.table5
TABLE sys.table6
TABLE sys.table7
TABLE sys.table8
TABLE sys.table9
The 20 tables have same create table as follows...
sql>\d table1
CREATE TABLE "sys"."table1" (
"id1" BIGINT NOT NULL,
"name1" VARCHAR(50),
"createdtime" TIMESTAMP,
CONSTRAINT "table1_id1_pkey" PRIMARY KEY ("id1")
);
sql>\d table2
CREATE TABLE "sys"."table2" (
"id2" BIGINT NOT NULL,
"name2" VARCHAR(50),
"createdtime" TIMESTAMP,
CONSTRAINT "table2_id2_pkey" PRIMARY KEY ("id2")
);
The create table of reltable with only 14 foreign key relations is as follows...
sql>\d reltable
CREATE TABLE "sys"."reltable" (
"id0" BIGINT NOT NULL,
"id1" BIGINT,
"id2" BIGINT,
"id3" BIGINT,
"id4" BIGINT,
"id5" BIGINT,
"id6" BIGINT,
"id7" BIGINT,
"id8" BIGINT,
"id9" BIGINT,
"id10" BIGINT,
"id11" BIGINT,
"id12" BIGINT,
"id13" BIGINT,
"id14" BIGINT,
"id15" BIGINT,
"id16" BIGINT,
"id17" BIGINT,
"id18" BIGINT,
"id19" BIGINT,
"id20" BIGINT,
CONSTRAINT "reltable_id0_pkey" PRIMARY KEY ("id0"),
CONSTRAINT "reltable_id10_fkey" FOREIGN KEY ("id10") REFERENCES "sys"."table10" ("id10") ON DELETE SET NULL,
CONSTRAINT "reltable_id11_fkey" FOREIGN KEY ("id11") REFERENCES "sys"."table11" ("id11") ON DELETE SET NULL,
CONSTRAINT "reltable_id12_fkey" FOREIGN KEY ("id12") REFERENCES "sys"."table12" ("id12") ON DELETE SET NULL,
CONSTRAINT "reltable_id13_fkey" FOREIGN KEY ("id13") REFERENCES "sys"."table13" ("id13") ON DELETE SET NULL,
CONSTRAINT "reltable_id14_fkey" FOREIGN KEY ("id14") REFERENCES "sys"."table14" ("id14"),
CONSTRAINT "reltable_id1_fkey" FOREIGN KEY ("id1") REFERENCES "sys"."table1" ("id1") ON DELETE SET NULL,
CONSTRAINT "reltable_id2_fkey" FOREIGN KEY ("id2") REFERENCES "sys"."table2" ("id2") ON DELETE SET NULL,
CONSTRAINT "reltable_id3_fkey" FOREIGN KEY ("id3") REFERENCES "sys"."table3" ("id3") ON DELETE SET NULL,
CONSTRAINT "reltable_id4_fkey" FOREIGN KEY ("id4") REFERENCES "sys"."table4" ("id4") ON DELETE SET NULL,
CONSTRAINT "reltable_id5_fkey" FOREIGN KEY ("id5") REFERENCES "sys"."table5" ("id5") ON DELETE SET NULL,
CONSTRAINT "reltable_id6_fkey" FOREIGN KEY ("id6") REFERENCES "sys"."table6" ("id6") ON DELETE SET NULL,
CONSTRAINT "reltable_id7_fkey" FOREIGN KEY ("id7") REFERENCES "sys"."table7" ("id7") ON DELETE SET NULL,
CONSTRAINT "reltable_id8_fkey" FOREIGN KEY ("id8") REFERENCES "sys"."table8" ("id8") ON DELETE SET NULL,
CONSTRAINT "reltable_id9_fkey" FOREIGN KEY ("id9") REFERENCES "sys"."table9" ("id9") ON DELETE SET NULL
);
I am using MonetDB tar downloaded from Downloads... I am not compiling from source code.. Isn't this reproducible in the tar even...???
## Comment 21133
Date: 2015-08-13 11:05:37 +0200
From: @sjoerdmullender
Fixed with changeset [08bc3bf282e3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=08bc3bf282e3)
## Comment 21215
Date: 2015-08-28 13:42:41 +0200
From: @sjoerdmullender
Jul2015 has been released.
| JDBC PreparedStatement for a table with 14 Foreign Keys crashing the Database | https://api.github.com/repos/MonetDB/MonetDB/issues/3763/comments | 0 | 2020-11-30T13:15:18Z | 2024-06-27T12:07:59Z | https://github.com/MonetDB/MonetDB/issues/3763 | 753,469,125 | 3,763 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-09 19:48:49 +0200
From: @eyalroz
To: M Travis <<travism1>>
Version: unspecified
CC: travism1
Last updated: 2017-04-09 01:46:42 +0200
## Comment 20985
Date: 2015-07-09 19:48:49 +0200
From: @eyalroz
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2244.0 Safari/537.36
Build Identifier:
It would be nice if the BugZilla pages had a different favicon than monetdb.org's general one. Perhaps a dinosaur head combined with the blue swoosh?
Not anything of high priority of course :-)
Reproducible: Always
## Comment 20986
Date: 2015-07-09 19:50:26 +0200
From: @eyalroz
And a bit of a different logo or header section for the Bugzilla section would help set them apart. I'd also consider making the MonetDB link at the top left of the pages here be a link to the MonetDB Bugzilla root page.
## Comment 25210
Date: 2017-04-09 01:46:42 +0200
From: M Travis <<travism1>>
More info about favicons for reference: https://www.everipedia.com/Favicons/
| Different FavIcon, logo for the Bugzilla section of the website | https://api.github.com/repos/MonetDB/MonetDB/issues/3762/comments | 0 | 2020-11-30T13:15:15Z | 2024-06-28T07:19:45Z | https://github.com/MonetDB/MonetDB/issues/3762 | 753,469,092 | 3,762 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-09 18:33:29 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:56 +0200
## Comment 20984
Date: 2015-07-09 18:33:29 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
Query:
SELECT NULL AS table_catalog, (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema FROM sys.tables t;
fails with a error: zero_or_one: cardinality violation (46>1)
while the similar (only columns in select list are swapped) query:
SELECT (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema, NULL AS table_catalog FROM sys.tables t;
is accepted and processed normally.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB v11.19.15 (Oct2014-SP4))
2. start mclient
3. run SQL commands:
SELECT NULL AS table_catalog, (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema FROM sys.tables t;
SELECT (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema, NULL AS table_catalog FROM sys.tables t;
On
### Actual Results:
bash-4.2$ mclient -p 49000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.19.15 (Oct2014-SP4), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT NULL AS table_catalog, (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema FROM sys.tables t;
zero_or_one: cardinality violation (46>1)
sql>SELECT (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema, NULL AS table_catalog FROM sys.tables t;
+--------------+---------------+
| table_schema | table_catalog |
+==============+===============+
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| tmp | null |
| tmp | null |
| tmp | null |
| tmp | null |
| tmp | null |
| tmp | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| sys | null |
| bam | null |
| bam | null |
| bam | null |
| bam | null |
| bam | null |
| sys | null |
| sys | null |
+--------------+---------------+
46 tuples (4.029ms)
sql>
### Expected Results:
No execution error for the 1st SELECT query: SELECT NULL AS table_catalog, (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema FROM sys.tables t;
It also happens for MonetDB 5 server v11.22.0 (default branch) and Jul2015 branch.
Additional SQL tests (work only for Jul2015 and default branches):
SELECT NULL AS table_catalog, (SELECT table_type_name FROM sys.table_types WHERE table_type_id = type) AS table_type_name FROM sys.tables t;
-- this fails with Error: zero_or_one: cardinality violation (61>1)
SELECT (SELECT table_type_name FROM sys.table_types WHERE table_type_id = type) AS table_type_name, NULL AS table_catalog FROM sys.tables t;
-- this works fine
SELECT NULL AS table_catalog, (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema, t.name as table_name, (SELECT table_type_name FROM sys.table_types WHERE table_type_id = type) AS table_type_name FROM sys.tables t;
-- this fails with Error: zero_or_one: cardinality violation (61>1)
SELECT (SELECT s.name FROM sys.schemas s WHERE t.schema_id = s.id) AS table_schema, t.name as table_name, (SELECT table_type_name FROM sys.table_types WHERE table_type_id = type) AS table_type_name, NULL AS table_catalog FROM sys.tables t;
-- this works fine
I need this SQL syntax (with "NULL AS table_catalog," as the first column in the SELECT-list) to work properly in order to continue with the creation of the view: information_schema.tables.
## Comment 21077
Date: 2015-08-01 15:18:11 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=30d12a4105a0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0)
Changeset description:
Bug fixes
Bug #3759 fixed types of returned bats (ie use timestamps instead of lng) in modules/mal/clients.c
Bug #3769 fixed crash (triggered assert) by properly looking for referenced groupby columns in push aggr down
optimizer in rel_optimizer.c
Bug #3760 fixed correlated subquery handling in rel_select.c, ie merge only distinct expressions.
Bug #3761 fixed by properly adding the zero_or_one aggregation only when needed (ie when the cardinality of
the outer query is a column/table, ie when we expect one value per row for the subquery).
Bug #3364 fixed in sql_privileges.c, ie allow set role when role_id == auth_id (ie default role).
Bug #3365 fixed in sql_privileges.c, the sql_grant_table_privs always added 'all' privileges in one go
in rel_schema.c properly pass the login_id or role_id based on the 'from current_{role/user}'
part of the grant statement
Bug #3476 was already fixed by previous revoke / schema fixes.
in gdk/gdk_select.c fixed problem with anti select and nils (stop before first nil instead of last)
## Comment 21085
Date: 2015-08-01 16:22:42 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [fcb611669cd1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fcb611669cd1) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fcb611669cd1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fcb611669cd1)
Changeset description:
added tests for bugs 3760 and 3761
## Comment 21087
Date: 2015-08-01 16:23:40 +0200
From: @njnes
only call zero or one when needed
## Comment 21223
Date: 2015-08-28 13:42:56 +0200
From: @sjoerdmullender
Jul2015 has been released.
| SQL executor has problem with (position of) a subquery in a SELECT-list. Inconsistent behavior. | https://api.github.com/repos/MonetDB/MonetDB/issues/3761/comments | 0 | 2020-11-30T13:15:13Z | 2024-06-27T12:07:57Z | https://github.com/MonetDB/MonetDB/issues/3761 | 753,469,056 | 3,761 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-09 17:28:22 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:43:08 +0200
## Comment 20983
Date: 2015-07-09 17:28:22 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
Query:
SELECT b, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
fails with a parse error: SELECT: identifier 'b' ambiguous
while the similar queries:
SELECT b, CASE a WHEN b THEN 444 END, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a) FROM t2;
and
SELECT b as "b1", (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
are accepted and processed normally.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB v11.19.15 (Oct2014-SP4))
2. start mclient
3. run SQL commands:
CREATE TABLE t2 (a int, b int);
INSERT INTO t2 VALUES (1,2);
SELECT * FROM t2;
SELECT b, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
SELECT b, CASE a WHEN b THEN 444 END, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a) FROM t2;
SELECT b as "b1", (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
DROP TABLE t2;
### Actual Results:
bash-4.2$ ./start_mserver5.sh
builtin opt gdk_dbpath = /export/scratch1/dinther/Downloads/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt mapi_port = 49000
cmdline opt gdk_debug = 10
MonetDB 5 server v11.19.15 "Oct2014-SP4"
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:49000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
>
bash-4.2$ mclient -p 49000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.19.15 (Oct2014-SP4), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TABLE t2 (a int, b int);
operation successful (8.875ms)
sql>INSERT INTO t2 VALUES (1,2);
1 affected row (1.067ms)
sql>SELECT * FROM t2;
+------+------+
| a | b |
+======+======+
| 1 | 2 |
+------+------+
1 tuple (1.234ms)
sql>SELECT b, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
SELECT: identifier 'b' ambiguous
sql>SELECT b, CASE a WHEN b THEN 444 END, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a) FROM t2;
+------+------+------+
| b | L1 | L3 |
+======+======+======+
| 2 | null | 0 |
+------+------+------+
1 tuple (6.470ms)
sql>SELECT b as "b1", (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
+------+------+-----------------------+
| b1 | L2 | ifthenelse_isnull_=_a |
+======+======+=======================+
| 2 | 0 | null |
+------+------+-----------------------+
1 tuple (5.905ms)
sql>DROP TABLE t2;
operation successful (1.581ms)
sql>\q
bash-4.2$
### Expected Results:
No error for the 1st SELECT query: SELECT b, (SELECT count(*) FROM t2 AS x WHERE x.a < t2.a), CASE a WHEN b THEN 444 END FROM t2;
It should produce:
+------+------+-----------------------+
| b | L2 | ifthenelse_isnull_=_a |
+======+======+=======================+
| 2 | 0 | null |
+------+------+-----------------------+
1 tuple (5.905ms)
## Comment 21076
Date: 2015-08-01 15:18:09 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=30d12a4105a0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0)
Changeset description:
Bug fixes
Bug #3759 fixed types of returned bats (ie use timestamps instead of lng) in modules/mal/clients.c
Bug #3769 fixed crash (triggered assert) by properly looking for referenced groupby columns in push aggr down
optimizer in rel_optimizer.c
Bug #3760 fixed correlated subquery handling in rel_select.c, ie merge only distinct expressions.
Bug #3761 fixed by properly adding the zero_or_one aggregation only when needed (ie when the cardinality of
the outer query is a column/table, ie when we expect one value per row for the subquery).
Bug #3364 fixed in sql_privileges.c, ie allow set role when role_id == auth_id (ie default role).
Bug #3365 fixed in sql_privileges.c, the sql_grant_table_privs always added 'all' privileges in one go
in rel_schema.c properly pass the login_id or role_id based on the 'from current_{role/user}'
part of the grant statement
Bug #3476 was already fixed by previous revoke / schema fixes.
in gdk/gdk_select.c fixed problem with anti select and nils (stop before first nil instead of last)
## Comment 21084
Date: 2015-08-01 16:22:40 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [fcb611669cd1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fcb611669cd1) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fcb611669cd1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fcb611669cd1)
Changeset description:
added tests for bugs 3760 and 3761
## Comment 21086
Date: 2015-08-01 16:23:05 +0200
From: @njnes
Fixed, ie properly merge unique lists
## Comment 21232
Date: 2015-08-28 13:43:08 +0200
From: @sjoerdmullender
Jul2015 has been released.
| SQL parser has problem with (position of) a scalar subquery in a SELECT-list | https://api.github.com/repos/MonetDB/MonetDB/issues/3760/comments | 0 | 2020-11-30T13:15:10Z | 2024-06-27T12:07:56Z | https://github.com/MonetDB/MonetDB/issues/3760 | 753,469,024 | 3,760 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-09 15:37:05 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2015-08-28 13:41:25 +0200
## Comment 20981
Date: 2015-07-09 15:37:05 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
>mserver5: ../../../dev/monetdb5/mal/mal_interpreter.c:646: runMALsequence: Assertion `bid == 0 || bid == ((bat) int_nil) || t == 255 || ((BBP[abs(bid)>>14][abs(bid)&((1 << 14)-1)].cache[(bid)<0]->T->type == 0)?6:BBP[abs(bid)>>14][abs(bid)&((1 << 14)-1)].cache[(bid)<0]->T->type) == ((t == 0)?6:t)' failed.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB 5 server v11.22.0)
2. start mclient
3. issue SQL queries:
select COUNT(*) from "sys"."queue";
select COUNT(*) from "sys"."rejects";
select COUNT(*) from "sys"."sessions";
### Actual Results:
bash-4.2$ ./start_INSTALL_mserver5.sh
builtin opt gdk_dbpath = /export/scratch1/dinther/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt embedded_r = true
cmdline opt mapi_port = 41000
cmdline opt gdk_debug = 10
MonetDB 5 server v11.22.0
This is an unreleased version
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs and 128bit integers dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:41000/
MonetDB/GIS module loaded
Start processing logs sql/sql_logs version 52200
Finished processing logs sql/sql_logs
MonetDB/SQL module loaded
MonetDB/R module loaded
> SQL catalog created, loading sql scripts once
loading sql script: 09_like.sql
loading sql script: 10_math.sql
loading sql script: 11_times.sql
loading sql script: 12_url.sql
loading sql script: 13_date.sql
loading sql script: 14_inet.sql
loading sql script: 15_querylog.sql
loading sql script: 16_tracelog.sql
loading sql script: 17_temporal.sql
loading sql script: 20_vacuum.sql
loading sql script: 21_dependency_functions.sql
loading sql script: 22_clients.sql
loading sql script: 23_skyserver.sql
loading sql script: 24_zorder.sql
loading sql script: 25_debug.sql
loading sql script: 26_sysmon.sql
loading sql script: 27_rejects.sql
loading sql script: 39_analytics.sql
loading sql script: 39_analytics_hge.sql
loading sql script: 40_geom.sql
loading sql script: 40_json.sql
loading sql script: 40_json_hge.sql
loading sql script: 41_md5sum.sql
loading sql script: 45_uuid.sql
loading sql script: 46_gsl.sql
loading sql script: 51_sys_schema_extension.sql
loading sql script: 72_fits.sql
loading sql script: 74_netcdf.sql
loading sql script: 75_storagemodel.sql
loading sql script: 80_statistics.sql
loading sql script: 80_udf.sql
loading sql script: 80_udf_hge.sql
loading sql script: 85_bam.sql
loading sql script: 90_generator.sql
loading sql script: 90_generator_hge.sql
loading sql script: 99_system.sql
>mserver5: ../../../dev/monetdb5/mal/mal_interpreter.c:646: runMALsequence: Assertion `bid == 0 || bid == ((bat) int_nil) || t == 255 || ((BBP[abs(bid)>>14][abs(bid)&((1 << 14)-1)].cache[(bid)<0]->T->type == 0)?6:BBP[abs(bid)>>14][abs(bid)&((1 << 14)-1)].cache[(bid)<0]->T->type) == ((t == 0)?6:t)' failed.
./start_INSTALL_mserver5.sh: line 5: 5740 Aborted /export/scratch1/dinther/INSTALL/bin/mserver5 -d10 --set embedded_r=true --set mapi_port=41000
bash-4.2$
bash-4.2$ mclient -p 41000
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.22.0 (unreleased), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select COUNT(*) from "sys"."queue";
+------+
| L1 |
+======+
| 1 |
+------+
1 tuple (1.241ms)
sql>select COUNT(*) from "sys"."rejects";
No reject table available
sql>select COUNT(*) from "sys"."sessions";
sql>
bash-4.2$
### Expected Results:
No error for query: select COUNT(*) from "sys"."rejects";
Also the error msg "No reject table available" is strange as we are querying the rejects table, and not the reject (without an s) table
No assertion failure after query: select COUNT(*) from "sys"."sessions";
Potentially the assertion failure is due to some internal data corruption after executing: select COUNT(*) from "sys"."rejects";
The problem does NOT exist in Oct2014 SP4, but probably does exist in Jul2015 branch also. Please fix it in Jul2015 branch also.
## Comment 20982
Date: 2015-07-09 16:10:51 +0200
From: Martin van Dinther <<martin.van.dinther>>
additional info: I compiled sources with configure flags: --enable-assert --disable-debug
## Comment 21075
Date: 2015-08-01 15:18:07 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=30d12a4105a0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30d12a4105a0)
Changeset description:
Bug fixes
Bug #3759 fixed types of returned bats (ie use timestamps instead of lng) in modules/mal/clients.c
Bug #3769 fixed crash (triggered assert) by properly looking for referenced groupby columns in push aggr down
optimizer in rel_optimizer.c
Bug #3760 fixed correlated subquery handling in rel_select.c, ie merge only distinct expressions.
Bug #3761 fixed by properly adding the zero_or_one aggregation only when needed (ie when the cardinality of
the outer query is a column/table, ie when we expect one value per row for the subquery).
Bug #3364 fixed in sql_privileges.c, ie allow set role when role_id == auth_id (ie default role).
Bug #3365 fixed in sql_privileges.c, the sql_grant_table_privs always added 'all' privileges in one go
in rel_schema.c properly pass the login_id or role_id based on the 'from current_{role/user}'
part of the grant statement
Bug #3476 was already fixed by previous revoke / schema fixes.
in gdk/gdk_select.c fixed problem with anti select and nils (stop before first nil instead of last)
## Comment 21080
Date: 2015-08-01 16:13:22 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e431bcfc8a34](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e431bcfc8a34) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e431bcfc8a34](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e431bcfc8a34)
Changeset description:
added test for bug #3759
## Comment 21081
Date: 2015-08-01 16:14:07 +0200
From: @njnes
Fixed aligned sql with mal/c level types
## Comment 21177
Date: 2015-08-28 13:41:25 +0200
From: @sjoerdmullender
Jul2015 has been released.
| select data from "sys"."rejects" returns unexpected error and when next select data from "sys"."sessions" causes an assertion failure in mal_interpreter.c:646. | https://api.github.com/repos/MonetDB/MonetDB/issues/3759/comments | 0 | 2020-11-30T13:15:08Z | 2024-06-27T12:07:55Z | https://github.com/MonetDB/MonetDB/issues/3759 | 753,468,999 | 3,759 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-09 13:50:00 +0200
From: Dieter <<mayerd>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes, @drstmane, @yzchang
Last updated: 2016-03-23 15:38:28 +0100
## Comment 20976
Date: 2015-07-09 13:50:00 +0200
From: Dieter <<mayerd>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
Build Identifier:
"COPY INTO ..." doesn't work, if executing from 2 processes in parallel.
ODBC Driver reports
"General Error"
or
"CREATE TABLE: name 'table01' already in use"
The concurrent (parallel) import of data should work correctly.
Also a parallel create table/drop table or other commands changing the database catalog information.
Reproducible: Always
### Steps to Reproduce:
1.Put Data.csv to your home directory on Fedora operating system.
2.Check monetbulk.cmd source code if 32bit / 64bit is used
3.Check monetBulk.vbs source code and check user/pw/odbc-dsn for
accessing database voc
4.Execute "monetbulk.cmd" to reproduce the error situation
It may take some seconds until the error occurs
### Actual Results:
ODBC Driver reports
"General Error"
or
"CREATE TABLE: name 'table01' already in use"
### Expected Results:
All data of data.csv should be imported into the 2 tables without error.
In our test script monetBulk.vbs we do a loop to import data.csv 10 times.
We are doing this in the test script, because so we can merely ensure that the error situation occurs.
## Comment 20977
Date: 2015-07-09 13:51:30 +0200
From: Dieter <<mayerd>>
Created attachment 338
Description and comments for the scenario
> Attached file: [description.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3758_description.txt_338) (text/plain, 484 bytes)
> Description: Description and comments for the scenario
## Comment 20978
Date: 2015-07-09 13:56:19 +0200
From: Dieter <<mayerd>>
Created attachment 339
Data.csv for import
> Attached file: [data.csv](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3758_data.csv_339) (application/vnd.ms-excel, 1000894 bytes)
> Description: Data.csv for import
## Comment 20979
Date: 2015-07-09 13:57:21 +0200
From: Dieter <<mayerd>>
Created attachment 340
Windows .cmd-File for executing 2 VBScripts in parallel
> Attached file: [monetbulk.cmd](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3758_monetbulk.cmd_340) (application/octet-stream, 539 bytes)
> Description: Windows .cmd-File for executing 2 VBScripts in parallel
## Comment 20980
Date: 2015-07-09 13:58:37 +0200
From: Dieter <<mayerd>>
Created attachment 341
VBScript for import of data.csv
> Attached file: [monetBulk.vbs](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3758_monetBulk.vbs_341) (application/octet-stream, 2131 bytes)
> Description: VBScript for import of data.csv
## Comment 21055
Date: 2015-07-23 11:56:25 +0200
From: Dieter <<mayerd>>
Created attachment 345
.cmd File for testing drop/create in parallel
This cmd file reproduces the error situation without importing via COPY INTO, but only execute drop table and create table in concurrent processes.
> Attached file: [monetDropCreate.cmd](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3758_monetDropCreate.cmd_345) (text/plain, 444 bytes)
> Description: .cmd File for testing drop/create in parallel
## Comment 21056
Date: 2015-07-23 11:58:41 +0200
From: Dieter <<mayerd>>
Created attachment 346
.vbs file reproducing error only with drop/create table
This .vbs file only executes drop table and create table
without COPY INTO.
> Attached file: [monetDropCreate.vbs](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3758_monetDropCreate.vbs_346) (text/plain, 1864 bytes)
> Description: .vbs file reproducing error only with drop/create table
## Comment 21057
Date: 2015-07-23 12:01:51 +0200
From: Dieter <<mayerd>>
I have made further analysis on the error situation.
The problem occurs not only when importing data with COPY INTO-Statement.
It also happens if I only execute
- DROP TABLE
- CREATE TABLE
in parallel for 2 different tables.
## Comment 21058
Date: 2015-07-23 12:34:14 +0200
From: @drstmane
Most probably it not the concurrent copy into into different tables,
but rather the concurrent creation of (different) tables.
Schema statements are (conflicting) transactions on the SQL catalogue.
With MonetDB's optimistic concurrency control approach,
all but one conflicting transaction(s) will be aborted
and it's up to the user / application to handle the abort as desired
(e.g., retry until successful).
I'm admittedly not a VBS expert,
but I cannot find where/how in your script you check whether the create table
statement succeeded or failed, and what you do in case it fails ...
## Comment 21062
Date: 2015-07-27 21:15:40 +0200
From: Dieter <<mayerd>>
Yes you are right in saying that the problem occurs in conflicting schema changing operations.
For there are some open questions:
1. Why dont you lock these transaction on the monet server? Every database I know (Oracle, MySQL, Msql Server, DB2,..) handels concurrent transactions itself (queuing the requests in arrival sequence) without leaving the problem to the application.
Stating this behavior as "optimistic concurrency control approach" is a friendly way to say: "it's your problem", isn't it?
2. If it is the only way to handle this behaviour. What unique ODBC error code Inhave to check to handle exactly the lock situation?
In my test scenario I got the message "common error" which not seems to be an error code for only this specific situation.
3. You say: every but one SQL catalogue changing transaction will be aborted.
But why do I get more than one record for a certain table in a specific schema
executing
SELECT name, schema_id FROM sys.tables where name='table01' and schema_id=3146 ?
(3146 is an example, I'v got about 1800 same records!)
As I understand it, this is a corrupt database catalogue information, what I think should never occur.
BTW: DROP TABLE voc.table01 reduces the number of records in the resultset by one.
Your help would be appreciated.
Dieter
## Comment 21092
Date: 2015-08-02 12:12:00 +0200
From: @njnes
1) locking isn't always friendly as well, you could start a transaction do one DDL statement and never comeback.
2) get the DDL statement out of the concurrent code, is the obvious solution. If this isn't possible an transaction failure should occure. Not sure what ODBC will give in that case.
3) This indicates a bug, which I'm convinced is fixed in the jul2015 and default branch.
## Comment 21227
Date: 2015-08-28 13:43:00 +0200
From: @sjoerdmullender
Jul2015 has been released.
## Comment 21348
Date: 2015-10-17 10:47:18 +0200
From: Dieter <<mayerd>>
Corrupted schema data are still present also with July 2015 release of MonetDB.
The problem is not fixed jet.
When doing concurrent schema operations on the same table, after a while I find no records sys.columns for my table, but in sys.tables there are several records with the same table name! --> corrupted schema
The Problem occurs on simple concurrent create table/drop table operations without importing data.
Mostly server threads of MonetDB abort with segmentation faults. In some cases I observed that the whole dbfarm was out of work after an error.
Even doing concurrent schema operations on different tables also results in error situation and server crashes.
## Comment 21947
Date: 2016-03-23 15:38:28 +0100
From: @njnes
many fixes were done around concurrent schema changes, ie we expect this problem to be fixed (in the to be release sp3)
| "COPY INTO ..." doesn't work, if executing from 2 processes concurrently. | https://api.github.com/repos/MonetDB/MonetDB/issues/3758/comments | 0 | 2020-11-30T13:15:05Z | 2024-06-27T12:07:54Z | https://github.com/MonetDB/MonetDB/issues/3758 | 753,468,966 | 3,758 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-08 16:27:41 +0200
From: @skinkie
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.19.15 (Oct2014-SP4)
CC: @mlkersten
Last updated: 2015-12-30 13:22:31 +0100
## Comment 20973
Date: 2015-07-08 16:27:41 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
Build Identifier:
I am trying to import a .gz file of 2229566049 bytes (2GB). When importing the file MonetDB cancels on:
could not allocate space for
HEAPextend: failed to extend to 2778726400 for 13/1313.theap: h->storage == STORE_MEM && can_map && fd >= 0 && HEAPload_intern() != GDK_SUCCEED
The uncompressed size is expanded 19384794504 bytes (19GB). The database then cancels on a Out-of-Memomry when trying to import the plain csv.
The system has 32GB of memory, ulimit -Sv reports unlimited.
What kind of operation may I expect from COPY INTO? What are the memory characteristics? What does the above error means, is it diskspace or memory? Could the error be more clear to the enduser?
Reproducible: Always
MonetDB 5 server v11.22.0 (64-bit, 64-bit oids, 128-bit integers)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 20974
Date: 2015-07-08 23:01:27 +0200
From: @mlkersten
One possible cause could be a series of underlying BATextends.
Did you provide an estimate on the number of tuples to prepare for?
e.g.
COPY n RECORDS INTO....
if 'n' is reasonable accurate then it avoids possible expensive
sequences of table storage extensions.
It might be that the system did not properly in time switched
from storage in the swap space to a memory mapped file.
## Comment 20975
Date: 2015-07-09 00:15:27 +0200
From: @skinkie
No I did not specify the numbers of columns, and only provided the file. After shutting down all the other databases (and clean up some extra space) the import succeeded. I'll add RECORDS to my future attempts.
Is MonetDB mmaping the input file, or are those buffered reads?
## Comment 21308
Date: 2015-09-29 21:55:27 +0200
From: @sjoerdmullender
Stefan, there are two questions for you in the below.
From the error message I can see that the HEAPextend was trying to switch from an allocated to a memory mapped heap. This should happen when the size grows bigger than 256 kB (GDK_mmap_minsize), i.e. not terribly large. Furthermore, I can see that memory mapping a file of the required size failed for some reason while the heap was still allocated, and failed again after the heap had been written to disk, freed, and then mapped.
What I find strange is the requested heap size (2.5 GB) when this switch from allocated to memory mapped is happening. The old size must have been less than 256 kB, so that is a huge jump. That usually doesn't happen during a COPY INTO. Did you set the gdk_mmap_minsize parameter?
The error message suggests that there is either severe address space fragmentation (so that no big enough chunk of address space can be allocated), or that the system is running out of resources and the kernel doesn't allow any large allocations.
I find it very strange that on a 64-bit architecture, the address space is so fragmented that such a relatively small area (the 2.5 GB) cannot be allocated in the address space.
The OS this happened on is MacOS X?
## Comment 21309
Date: 2015-09-29 21:57:48 +0200
From: @skinkie
No, this is Linux using kernel 3.10.
## Comment 21310
Date: 2015-09-29 22:06:32 +0200
From: @sjoerdmullender
Two questions. ;-)
## Comment 21311
Date: 2015-09-29 22:08:05 +0200
From: @skinkie
"Did you set the gdk_mmap_minsize parameter?" I am not aware that I have explicitly set this value or configured it. I always run a build/run MonetDB with the stock configuration.
## Comment 21595
Date: 2015-11-25 22:22:02 +0100
From: @mlkersten
Any progress on this? Still problems importing the 2GB file?
## Comment 21701
Date: 2015-12-30 13:22:31 +0100
From: @mlkersten
Closed until further notices.
| Importing a 2GB .gz file results in could not allocate space for HEAPextend | https://api.github.com/repos/MonetDB/MonetDB/issues/3757/comments | 0 | 2020-11-30T13:15:02Z | 2024-06-28T13:14:41Z | https://github.com/MonetDB/MonetDB/issues/3757 | 753,468,930 | 3,757 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-08 15:59:59 +0200
From: Dennis Lorson <<dennis>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:43:07 +0200
## Comment 20970
Date: 2015-07-08 15:59:59 +0200
From: Dennis Lorson <<dennis>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/600.7.12 (KHTML, like Gecko) Version/8.0.7 Safari/600.7.12
Build Identifier:
The query planner will keep including a type conversion (e.g. batcalc.lng) on a column, even if not required, after a previous query has been performed where the type conversion was appropriate.
Reproducible: Always
### Steps to Reproduce:
1. create table test(value int);
2. insert into test values (1), (2), (3);
3. select * from test where value = 12345678900; value > INT_MAX
4. trace select * from test where value = 1; value < INT_MAX
### Actual Results:
The trace includes an (expensive) <batcalc.lng> instruction
### Expected Results:
The trace does not include a <batcalc.lng> instruction, since the last query did not provide a LONG-range literal in its condition.
Niels Nes indicated this has to do with the query cache.
While this issue does not affect the correctness of the result set, it has a serious impact on performance, since all later queries will be orders of magnitude slower than needed on large tables.
## Comment 21090
Date: 2015-08-01 21:56:06 +0200
From: @njnes
added an optimization which removes the case (changes the compare expression also if needed). The optimizer also handles cases for <, <=, >=, > and <>.
## Comment 21091
Date: 2015-08-01 21:59:07 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [aebfa751b214](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=aebfa751b214) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=aebfa751b214](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=aebfa751b214)
Changeset description:
fixed bug #3756, ie incase of up casts and comparisons with a simple atom (literal or stacked)
we convert to < max (of smaller type) of > max (of smaller type)
## Comment 21231
Date: 2015-08-28 13:43:07 +0200
From: @sjoerdmullender
Jul2015 has been released.
| column type conversion sticks to subsequent queries | https://api.github.com/repos/MonetDB/MonetDB/issues/3756/comments | 0 | 2020-11-30T13:14:59Z | 2024-06-27T12:07:52Z | https://github.com/MonetDB/MonetDB/issues/3756 | 753,468,900 | 3,756 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-08 13:47:04 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-07-08 16:23:32 +0200
## Comment 20969
Date: 2015-07-08 13:47:04 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
Build Identifier:
It seems that an existing lib/monetdb5/createdb/41_jsonstore.sql is being installed from a previous make install. When removing this file the problem is resolved.
It would be nice if problem such as these wouldn't prevent mclient to connect to a database.
Reproducible: Always
MonetDB 5 server v11.22.0 (64-bit, 64-bit oids, 128-bit integers)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 20972
Date: 2015-07-08 16:23:32 +0200
From: @njnes
this only happens when you compile your self. A make uninstall, before make install should (have) fixed the problem.
| New databases cannot be created: CREATE FUNCTION: name 'md5' (clob) already in use | https://api.github.com/repos/MonetDB/MonetDB/issues/3755/comments | 0 | 2020-11-30T13:14:57Z | 2024-06-28T13:14:41Z | https://github.com/MonetDB/MonetDB/issues/3755 | 753,468,870 | 3,755 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-07 18:12:35 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2018-04-23 16:31:18 +0200
## Comment 20968
Date: 2015-07-07 18:12:35 +0200
From: @yzchang
[Version should be changed to Jul2015 when it's added to the list]
commands to run server and client:
$ mserver5 --dbpath=/tmp/test
$ mclient -d test
Run the following queries:
CREATE TABLE t1 (i int);
CREATE REMOTE TABLE rt (LIKE t1) ON 'mapi:monetdb://localhost:50000/test';
SELECT * FROM rt;
to observe mserver5 crash at the following line:
0x00007fffef39d646 in timestamp_delta (d=0x0, ts=0) at /ufs/zhang/monet/Jul2015/sql/storage/bat/bat_storage.c:21
21 while (d->next && d->wtime > ts)
## Comment 21097
Date: 2015-08-05 12:32:50 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [87df8ec9d2ce](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=87df8ec9d2ce) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=87df8ec9d2ce](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=87df8ec9d2ce)
Changeset description:
added more defensive code to handle typos for the remote cases.
see bugs 3778 and 3754
## Comment 21099
Date: 2015-08-05 12:33:44 +0200
From: @njnes
fixed by adding for a valid table in the bat_storage.c bind and property functions
## Comment 21186
Date: 2015-08-28 13:41:47 +0200
From: @sjoerdmullender
Jul2015 has been released.
## Comment 26403
Date: 2018-04-23 16:31:18 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [a7b565049fd9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a7b565049fd9) made by Panagiotis Koutsourakis <kutsurak@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7b565049fd9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7b565049fd9)
Changeset description:
Signal to MAPI that the password is hashed
This should fix the test
sql/test/BugTracker-2015/local-remotetable-crash.Bug-3754 that was
broken.
| select from a REMOTE TABLE referring local table crashes mserver5 | https://api.github.com/repos/MonetDB/MonetDB/issues/3754/comments | 0 | 2020-11-30T13:14:55Z | 2024-06-27T12:07:49Z | https://github.com/MonetDB/MonetDB/issues/3754 | 753,468,842 | 3,754 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-06 15:04:44 +0200
From: Vladimir Radushevskiy <<vradrus>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @mlkersten, @njnes
Last updated: 2015-08-28 13:41:55 +0200
## Comment 20964
Date: 2015-07-06 15:04:44 +0200
From: Vladimir Radushevskiy <<vradrus>>
sql>SELECT json.isvalid('[0,1]');
+----------------------+
| isvalid_single_value |
+======================+
| true |
+----------------------+
1 tuple (0.224ms)
sql>SELECT json.isvalid('[0,,1]');
Not response in current session and 100% CPU usage on one core аnd eats memory.
## Comment 20965
Date: 2015-07-06 15:30:44 +0200
From: Vladimir Radushevskiy <<vradrus>>
Error in json parser:
SELECT json.isValid(null); => false
All this variants must be FALSE (json valid structures only {} and [])
SELECT json.isValid(''); => false
SELECT json.isValid('null'); => TRUE, must be false
SELECT json.isValid('"'); => false
SELECT json.isValid('""'); => false
SELECT json.isValid('"""'); => TRUE, must be false
SELECT json.isValid('"\""'); => TRUE, must be false
SELECT json.isValid('""""'); => false
SELECT json.isValid('"\"\""'); => false
Array:
SELECT json.isValid('[]'); => true
SELECT json.isValid('[null]'); => true
SELECT json.isValid('[""]'); => FALSE, must be true
SELECT json.isValid('["""]'); => TRUE, must be false
SELECT json.isValid('["\""]'); => true
SELECT json.isValid('[""""]'); => false
SELECT json.isValid('["\"\""]'); => FALSE, must be true
Object:
SELECT json.isValid('{}'); => true
SELECT json.isValid('{"test":null}'); => true
SELECT json.isValid('{"test":""}'); => FALSE, must be true
SELECT json.isValid('{"test":"""}'); => TRUE, must be false
SELECT json.isValid('{"test":"\""}'); => true
SELECT json.isValid('{"test":""""}'); => false
SELECT json.isValid('{"test":"\"\""}'); => FALSE, must be true
## Comment 20966
Date: 2015-07-06 17:17:36 +0200
From: Vladimir Radushevskiy <<vradrus>>
SELECT json.isValid('{"test":\""\"}'); => TRUE, must be false
## Comment 20967
Date: 2015-07-06 23:06:06 +0200
From: @mlkersten
Correct observation. Test has been added to the test suite the Jul2015 branch.
The errors will be fixed soon. Thx for this minitest.
## Comment 20971
Date: 2015-07-08 16:21:44 +0200
From: @njnes
fixed in jul2015 branch, added more restrictive parsing
## Comment 21194
Date: 2015-08-28 13:41:55 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Hang on json field parsing | https://api.github.com/repos/MonetDB/MonetDB/issues/3753/comments | 0 | 2020-11-30T13:14:52Z | 2024-06-27T12:07:48Z | https://github.com/MonetDB/MonetDB/issues/3753 | 753,468,807 | 3,753 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-02 13:30:04 +0200
From: @hannesmuehleisen
To: SQL devs <<bugs-sql>>
Version: 11.19.3 (Oct2014)
CC: martin.van.dinther
Duplicates: #3600
Last updated: 2015-07-03 10:37:47 +0200
## Comment 20958
Date: 2015-07-02 13:30:04 +0200
From: @hannesmuehleisen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.130 Safari/537.36
Build Identifier:
sql>create temporary table a (i integer);
operation successful (1.569ms)
sql>insert into a values(42);
1 affected row (1.341ms)
sql>select * from a;
+---+
| i |
+===+
+---+
0 tuples (0.842ms)
-- wtf?!
Reproducible: Always
### Expected Results:
Value should be in temp. table
## Comment 20960
Date: 2015-07-02 18:31:17 +0200
From: Martin van Dinther <<martin.van.dinther>>
Hi Hannes,
You will need to use:
create temporary table a (i integer) ON COMMIT PRESERVE ROWS;
instead.
The default behavior when creating temporary tables (so without the ON COMMIT clause) is ON COMMIT DELETE ROWS.
*** This bug has been marked as a duplicate of bug #3600 ***
## Comment 20962
Date: 2015-07-03 10:37:47 +0200
From: @hannesmuehleisen
Thanks Martin
| INSERT INTO temporary table has no effect | https://api.github.com/repos/MonetDB/MonetDB/issues/3752/comments | 0 | 2020-11-30T13:14:50Z | 2024-06-28T13:14:40Z | https://github.com/MonetDB/MonetDB/issues/3752 | 753,468,780 | 3,752 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-02 13:17:03 +0200
From: @mlkersten
To: Merovingian devs <<bugs-merovingian>>
Version: 11.21.19 (Jul2015-SP4)
Last updated: 2016-04-11 11:24:33 +0200
## Comment 20957
Date: 2015-07-02 13:17:03 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
If the environment gets corrupted, the only resort is to manually fix it.
However, a 'monetdbd recover' should be provided to get a clean state again.
- kill any remaining mserver processes the hard way (and in debuggers)
- remove any cruft to get a clean state
- move aside or ditch the merovingian log file
The case is illustrated as follows:
[mk@rocks101 ~]$ monetdbd get all /scratch/mk/dbfarm|grep status
status a monetdbd is serving this dbfarm, but a pidfile was not found/is corrupt
Indeed, there is no pid file in the dbfarm directory.
[mk@rocks101 dbfarm]$ ls -la
total 16
drwxr-xr-x 3 mk mk 4096 Jul 2 10:07 .
drwxrwxr-x 6 mk mk 4096 Jul 1 15:50 ..
-rw-rw-r-- 1 mk mk 0 Mar 15 11:08 .merovingian_lock
-rw-rw-r-- 1 mk mk 122 Mar 3 11:06 .merovingian_properties
We have, however, a daemon and server running
[mk@rocks101 ~]$ ps axl |grep monetdbd
1 2001 10006 1 20 0 417968 4420 poll_s Ssl ? 0:01 monetdbd start /scratch/mk/dbfarm
The server seems to hang in a debugger
[mk@rocks101 ~]$ ps axl |grep mserver5
0 2002 16044 26389 20 0 261944 12 poll_s S+ pts/5 0:00 gdb mserver5
0 2001 19130 10006 20 0 2669444 1195600 poll_s Ssl ? 0:28 /scratch/mk/default/Linux/bin/mserver5 --dbpath=/scratch/mk/dbfarm/sf1 --set merovingian_uri mapi:monetdb://rocks101.scilens.private:50000/sf1 --set mapi_open false --set mapi_port 0 --set mapi_usock /scratch/mk/dbfarm/sf1/.mapi.sock --set monet_vault_key /scratch/mk/dbfarm/sf1/.vaultkey --set gdk_nr_threads 8 --set max_clients 64 --set sql_optimizer default_pipe --set monet_daemon yes
[mk@rocks101 ~]$ monetdbd stop /scratch/mk/dbfarm
unable to open merovingian.pid: No such file or directory
Killing the gdb process release the monetdbd process as well, but keeping the mserver
Reproducible: Always
| MonetDBD can not recover | https://api.github.com/repos/MonetDB/MonetDB/issues/3751/comments | 0 | 2020-11-30T13:14:48Z | 2024-06-28T13:14:39Z | https://github.com/MonetDB/MonetDB/issues/3751 | 753,468,747 | 3,751 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-07-01 23:17:59 +0200
From: @mlkersten
To: Merovingian devs <<bugs-merovingian>>
Version: 11.21.19 (Jul2015-SP4)
CC: @hannesmuehleisen
Last updated: 2016-04-11 11:24:39 +0200
## Comment 20952
Date: 2015-07-01 23:17:59 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
It may happen that somethings goes wrong during mserver startup. For example, a user thread aborts. Then merovingian may belief that the server remains in "start up" phase, never to escape from this situation until the DBA explicitly stops it.
There should at least be a time out for systems in those states.
Reproducible: Always
## Comment 20953
Date: 2015-07-01 23:21:48 +0200
From: @mlkersten
It could als happen that the status of monetdb shows a healthy mserver, while in practice it might have gone unnoticed.
[mk@rocks104 ~]$ monetdb status
name state health remarks
sf1 S 11m 100% 2h mapi:monetdb://rocks104.scilens.private:50000/sf1
[mk@rocks104 ~]$ ps axl |grep monet
0 2001 6381 6339 20 0 112664 912 pipe_w S+ pts/0 0:00 grep --color=auto monet
1 2001 22478 1 20 0 417968 2340 poll_s Ssl ? 0:00 monetdbd start /scratch/mk/dbfarm
[mk@rocks104 ~]$ ps axl |grep mserver
0 2001 6386 6339 20 0 112664 916 pipe_w S+ pts/0 0:00 grep --color=auto mserver
Looks like we need a sanity checking thread to handle these cases.
## Comment 20954
Date: 2015-07-01 23:22:28 +0200
From: @mlkersten
On the initial case: there was no SQL reader running
## Comment 20955
Date: 2015-07-01 23:24:27 +0200
From: @mlkersten
second case denoted Suspended, so is in principle correct.
## Comment 20956
Date: 2015-07-02 10:25:49 +0200
From: @hannesmuehleisen
Have this problem all the time. Seriously annoying, also comes up on user list frequently. Perhaps we should ditch it, also because it never made it to Windows.
## Comment 21067
Date: 2015-07-29 17:26:36 +0200
From: @sjoerdmullender
(In reply to Martin Kersten from comment 1)
> It could als happen that the status of monetdb shows a healthy mserver,
> while in practice it might have gone unnoticed.
>
> [mk@rocks104 ~]$ monetdb status
> name state health remarks
> sf1 S 11m 100% 2h mapi:monetdb://rocks104.scilens.private:50000/sf1
> [mk@rocks104 ~]$ ps axl |grep monet
> 0 2001 6381 6339 20 0 112664 912 pipe_w S+ pts/0 0:00 grep
> --color=auto monet
> 1 2001 22478 1 20 0 417968 2340 poll_s Ssl ? 0:00
> monetdbd start /scratch/mk/dbfarm
> [mk@rocks104 ~]$ ps axl |grep mserver
> 0 2001 6386 6339 20 0 112664 916 pipe_w S+ pts/0 0:00 grep
> --color=auto mserver
>
> Looks like we need a sanity checking thread to handle these cases.
I don't understand the problem here. Merovingian reports that it knows abouty the database sf1 and that it is "S"topped. And ps corroborates that: there is no mserver process running. Where is the problem?
| Hanging mserver during startup | https://api.github.com/repos/MonetDB/MonetDB/issues/3750/comments | 0 | 2020-11-30T13:03:02Z | 2024-06-28T13:14:39Z | https://github.com/MonetDB/MonetDB/issues/3750 | 753,460,925 | 3,750 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-29 16:36:09 +0200
From: kuhviertel14
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-07-01 10:03:38 +0200
## Comment 20949
Date: 2015-06-29 16:36:09 +0200
From: kuhviertel14
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
I want to use MonetDB in connection with Tableau (visualization software). Tableau provides a nice drilldown functionality for attributes of type Date. I tested this functionality successfully with postgreSQL. Unfortunately, the following error message occurs, when trying with MonetDB:
SELECT: no such binary operator 'ms_trunc(int,tinyint)'
It would be very helpful, if the binary operator could be implemented in the next version, as it would dramatically improve the convenience of using MonetDB as a data source in Tableau.
Reproducible: Always
## Comment 20950
Date: 2015-07-01 10:03:38 +0200
From: @njnes
could you somehow find out which query tableau sends to the server when this
problem happens?
| SELECT: no such binary operator 'ms_trunc(int,tinyint)' | https://api.github.com/repos/MonetDB/MonetDB/issues/3749/comments | 0 | 2020-11-30T13:02:57Z | 2024-06-27T12:07:44Z | https://github.com/MonetDB/MonetDB/issues/3749 | 753,460,870 | 3,749 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-27 18:20:24 +0200
From: Alexander Alexandrov <<alexander.alexandrov>>
To: clients devs <<bugs-clients>>
Version: 11.19.15 (Oct2014-SP4)
CC: @hannesmuehleisen
Last updated: 2015-08-28 13:41:45 +0200
## Comment 20945
Date: 2015-06-27 18:20:24 +0200
From: Alexander Alexandrov <<alexander.alexandrov>>
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
The MonetDB JDBC driver currently has to be manually loaded by the client via Class.forName(...) prior to usage.
According to the DriverManager documentation [1], the driver can be added automatically by the JVM if one adds a META-INF/services/java.sql.Driver file to the jar containing the fully qualified class name of the SQLDriver implementation.
[1] https://docs.oracle.com/javase/7/docs/api/java/sql/DriverManager.html
Reproducible: Always
### Steps to Reproduce:
1. Run DriverManager.getConnection("jdbc:monetdb:...") without calling Class.forName(...) first.
### Actual Results:
Throws a "No suitable driver found for jdbc:monetdb:..." error.
### Expected Results:
The driver should be discovered automatically if the jar is in the runtime classpath.
## Comment 20963
Date: 2015-07-03 12:56:22 +0200
From: @hannesmuehleisen
Fixed in rev. [51565d00c2c5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=51565d00c2c5)
## Comment 21001
Date: 2015-07-15 14:10:11 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [9dc80e4dacbd](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9dc80e4dacbd) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9dc80e4dacbd](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9dc80e4dacbd)
Changeset description:
Java Client: Fix for Bug #3748
(grafted from 51565d00c2c54d68447c8d97017b64777329a441)
## Comment 21185
Date: 2015-08-28 13:41:45 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Missing META-INF/services/java.sql.Driver in JDBC package | https://api.github.com/repos/MonetDB/MonetDB/issues/3748/comments | 0 | 2020-11-30T13:02:55Z | 2024-06-27T12:07:43Z | https://github.com/MonetDB/MonetDB/issues/3748 | 753,460,849 | 3,748 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-26 09:18:20 +0200
From: John Thomas <<john>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:43:02 +0200
## Comment 20943
Date: 2015-06-26 09:18:20 +0200
From: John Thomas <<john>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36
Build Identifier:
When joining on a column that contains nulls, the resulting output is incorrect.
Reproducible: Always
### Steps to Reproduce:
1. Very basic test case setup:
create table foo (a string, b int);
create table bar (a string, b int);
insert into foo values ('hi',0),('there',null),('monet',1);
insert into bar values ('sup',0),('dude',1);
2. Perform join on column with null present.
3. Observe failure.
### Actual Results:
select foo.a,foo.b,bar.b,bar.a from foo join bar on foo.b=bar.b;
+-------+------+------+------+
| a | b | b | a |
+=======+======+======+======+
| hi | 0 | 0 | sup |
| there | null | 1 | dude |
+-------+------+------+------+
### Expected Results:
+-------+------+------+------+
| a | b | b | a |
+=======+======+======+======+
| hi | 0 | 0 | sup |
| monet | 1 | 1 | dude |
+-------+------+------+------+
From what I've observed of larger test cases, the result seems to have the correct number of rows, with the correct values on the right and incorrect values on the left.
This bug is present in all releases from Jan2014 (11.17.9) through Oct2014-SP4 (11.19.15). The Feb2013 release behaves correctly.
Interestingly, if you add "where foo.b is not null" to the test query above, the optimizer performs that filter prior to the join and produces the expected result. This suggests that null values aren't being handled correctly in the join function itself.
## Comment 20944
Date: 2015-06-26 20:23:32 +0200
From: @njnes
The mergejoin code didn't handle the nil properly (fixed in Jul2015).
## Comment 21228
Date: 2015-08-28 13:43:02 +0200
From: @sjoerdmullender
Jul2015 has been released.
| joins fail in the presence of nulls | https://api.github.com/repos/MonetDB/MonetDB/issues/3747/comments | 0 | 2020-11-30T13:02:52Z | 2024-06-27T12:07:42Z | https://github.com/MonetDB/MonetDB/issues/3747 | 753,460,822 | 3,747 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-25 15:22:21 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-06-28 13:26:16 +0200
## Comment 20942
Date: 2015-06-25 15:22:21 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
After a DECLARE TABLE statement has been executed, the table is permanently present in the schema.
Reproducible: Always
### Steps to Reproduce:
1. monetdb stop declarebug; monetdb destroy -f declarebug; monetdb create declarebug; monetdb start declarebug; monetdb release declarebug;
2. mclient -ddeclarebug -s"declare table declbug (id int, d double);"
3. mclient -ddeclarebug -s"select * from declbug;"
### Actual Results:
operation successful
+----+---+
| id | d |
+====+===+
+----+---+
0 tuples
### Expected Results:
Table should not exist anymore.
Did not test this behaviour in functions.
## Comment 20947
Date: 2015-06-28 13:26:16 +0200
From: @njnes
declare table at this (global) level isn't allowed in the sql standaard. Normaly its allowed in a MODULE (or with in any function/procedure).
As we do not support Modules the global level isn't handled.
Currently the declare at this level is transformed in a normal create (persistent) table.
| DECLARE TABLE should be temporary in session scope | https://api.github.com/repos/MonetDB/MonetDB/issues/3746/comments | 0 | 2020-11-30T13:02:50Z | 2024-06-28T13:14:38Z | https://github.com/MonetDB/MonetDB/issues/3746 | 753,460,791 | 3,746 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-22 18:35:47 +0200
From: 357416268
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2016-04-11 11:45:51 +0200
## Comment 20939
Date: 2015-06-22 18:35:47 +0200
From: 357416268
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36
Build Identifier:
If I COPY BINARY INTO a table which has a serial type primary key,
I can not use COPY BINARY INTO command directly to this table,
I must create a helper table without auto increment primary key, COPY BINARY INTO the helper table and then insert into the large table from the helper table.
but usually the last step is very time consuming.
Reproducible: Always
### Steps to Reproduce:
1.create table uniquecatalogg(targetid int, ra_avg double, decl_avg double, flux_ref double, zone smallint, x double, y double, z double);
2.create sequence "unique_seq" as int;
3.create table uniquecatalog(id int PRIMARY KEY DEFAULT NEXT VALUE FOR "unique_seq"
, targetid int, ra_avg double, decl_avg double, flux_ref double, datapoints int, one smallint, x double, y double, z double, INACTIVE BOOLEAN);
### Actual Results:
when I COPY BINARY 78GB binary data into monetdb, loading only takes 523.231 second,
while the last INSERT INTO takes 576.388 second.
### Expected Results:
COPY BINARY INTO table (col1, col2, col3) FROM file1, file2, file3;
if the table has a auto increment column, the column grows in the background like what it does in
INSERT INTO command.
| COPY BINARY doesn't support copy without auto-increment column | https://api.github.com/repos/MonetDB/MonetDB/issues/3745/comments | 0 | 2020-11-30T13:02:48Z | 2024-06-28T07:19:45Z | https://github.com/MonetDB/MonetDB/issues/3745 | 753,460,761 | 3,745 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-22 16:13:53 +0200
From: @bartscheers
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:59 +0200
## Comment 20938
Date: 2015-06-22 16:13:53 +0200
From: @bartscheers
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
A cast to int for a decimal value rounds the value off to closest int, while double is cast to truncated value.
Reproducible: Always
### Steps to Reproduce:
1. select cast(cast(13.8 as decimal(10,7)) as int);
2. select cast(cast(13.8 as double) as int);
### Actual Results:
+------+
| L2 |
+======+
| 14 |
+------+
1 tuple
+------+
| L2 |
+======+
| 13 |
+------+
1 tuple
### Expected Results:
At least identical behaviour.
+------+
| L2 |
+======+
| 13 |
+------+
1 tuple
+------+
| L2 |
+======+
| 13 |
+------+
1 tuple
## Comment 20940
Date: 2015-06-22 21:43:25 +0200
From: @njnes
fixed in jul2015 branch
## Comment 21226
Date: 2015-08-28 13:42:59 +0200
From: @sjoerdmullender
Jul2015 has been released.
| cast to int gives different results for decimal than double | https://api.github.com/repos/MonetDB/MonetDB/issues/3744/comments | 0 | 2020-11-30T13:02:46Z | 2024-06-27T12:07:39Z | https://github.com/MonetDB/MonetDB/issues/3744 | 753,460,729 | 3,744 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-22 15:03:50 +0200
From: 357416268
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @PedroTadim
Last updated: 2019-04-30 12:36:01 +0200
## Comment 20937
Date: 2015-06-22 15:03:50 +0200
From: 357416268
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36
Build Identifier:
DELETE FROM: cannot delete from merge table
Reproducible: Always
### Steps to Reproduce:
1.create table t1(t int); insert into t1 values(1);
2.create table t2(t int);insert into t2 values(1);
3.create merge table tt(t int);alter table tt add table t1;alter table tt add table t2;
4. delete from tt where t=1;
### Actual Results:
sql>delete from tt where t=1;
DELETE FROM: cannot delete from merge table 'tt'
### Expected Results:
merge table should be able to be deleted from, otherwise users need to iterate every sub table to delete, it's very complicated for users to do so if merge table has a number of sub tables.
I am using default branch, downloaded on Jun 9 2015.
mserver5 --version
MonetDB 5 server v11.20.0 (64-bit, 64-bit oids, 128-bit integers)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 251.9GiB available memory, 16 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1e 11 Feb 2013 (compiled with OpenSSL 1.0.1e-fips 11 Feb 2013)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: mwan@stones01.scilens.private (x86_64-unknown-linux-gnu)
Compilation: gcc -O3 -pipe -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code -D_FORTIFY_SOURCE=2
Linking : /usr/bin/ld -m elf_x86_64
## Comment 25380
Date: 2017-06-08 17:44:45 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [52df84bcf8ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=52df84bcf8ba) made by Martin van Dinther <martin.van.dinther@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52df84bcf8ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=52df84bcf8ba)
Changeset description:
Add test script for feature request / bug #3743
## Comment 26710
Date: 2018-12-04 09:49:39 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [00ab6503524c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=00ab6503524c) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=00ab6503524c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=00ab6503524c)
Changeset description:
With partitioned tables handling addition, we can now support delete statements in non-partitioned tables as well. This fixes bug #3743.
| DELETE FROM merge table not supported. | https://api.github.com/repos/MonetDB/MonetDB/issues/3743/comments | 0 | 2020-11-30T13:02:43Z | 2024-06-27T12:07:38Z | https://github.com/MonetDB/MonetDB/issues/3743 | 753,460,694 | 3,743 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-22 02:24:20 +0200
From: Raffy <<raffy>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2017-12-20 22:15:31 +0100
## Comment 20935
Date: 2015-06-22 02:24:20 +0200
From: Raffy <<raffy>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
This throws a division by zero:
SELECT
count(*) / ((max("end")-min(start)) / 60)
FROM t
GROUP BY s
HAVING max("end")-min(start)<>0 ;
While this does not:
SELECT
count(*) / ((max("end")-min(start)))
FROM t
GROUP BY s
HAVING max("end")-min(start)<>0;
Recreate with:
Reproducible: Always
### Steps to Reproduce:
create table t ("end" timestamp, start timestamp, s text);
insert into t ("2015-03-01 00:00:00.135000", "2015-03-01 00:18:00.258000", "foo");
insert into t ("2015-03-01 00:04:00.135000", "2015-03-01 00:22:00.258000", "bar");
SELECT
count(*) / ((max("end")-min(start)) / 60)
FROM t
GROUP BY s
HAVING max("end")-min(start)<>0 ;
### Actual Results:
Division by zero (which it shouldn't!)
## Comment 20941
Date: 2015-06-22 21:44:01 +0200
From: @njnes
fixed in jul2015 branch
## Comment 21224
Date: 2015-08-28 13:42:57 +0200
From: @sjoerdmullender
Jul2015 has been released.
## Comment 26037
Date: 2017-12-20 22:15:31 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [0276d6b12a9b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0276d6b12a9b) made by Martin Kersten <mk@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=0276d6b12a9b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=0276d6b12a9b)
Changeset description:
Avoid append instructions to disappear
Calling this optimizer after a multiplex expansion
could lead to removal of append() instructions.
The test showing it div_zero.Bug-3742.
| Division By Zero | https://api.github.com/repos/MonetDB/MonetDB/issues/3742/comments | 0 | 2020-11-30T13:02:40Z | 2024-06-27T12:07:37Z | https://github.com/MonetDB/MonetDB/issues/3742 | 753,460,665 | 3,742 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-18 11:07:42 +0200
From: 357416268
To: SQL devs <<bugs-sql>>
Version: 11.21.19 (Jul2015-SP4)
CC: 357416268, @hannesmuehleisen, @njnes, @PedroTadim, @yzchang
Last updated: 2020-03-16 18:37:52 +0100
## Comment 20929
Date: 2015-06-18 11:07:42 +0200
From: 357416268
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.124 Safari/537.36
Build Identifier:
OLD ROW syntax is actually using OLD TABLE.
Reproducible: Always
### Steps to Reproduce:
1.CREATE TRIGGER trtest
BEFORE DELETE ON test1 REFERENCING OLD ROW AS oldrow
FOR EACH ROW INSERT INTO test2 SELECT * FROM oldrow;
2.select * from test1;
+------+
| t |
+======+
| 1 |
| 2 |
| 3 |
+------+
table test2 is empty.
### Actual Results:
3. sql>delete from test1 where t=1;
1 affected row (37.359ms)
sql>select * from test2;
+------+
| t |
+======+
| 1 |
| 2 |
| 3 |
+------+
3 tuples (0.388ms)
so all the rows of test1 are copied to test2.
### Expected Results:
only one row t=1 should be inserted into test2.
Actually I am using default branch downloaded on Jun 9 2015, v11.20.0.
## Comment 21111
Date: 2015-08-08 17:25:32 +0200
From: @njnes
trigger implementation indeed needs work..
## Comment 21288
Date: 2015-09-28 12:48:33 +0200
From: @hannesmuehleisen
Issue also occurs on NEW ROW
## Comment 21289
Date: 2015-09-28 12:49:29 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [79c7cc23262e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=79c7cc23262e) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=79c7cc23262e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=79c7cc23262e)
Changeset description:
Updates to trigger insert test case to consider multiple rows in table. This extends Bug #3741. Spotted by Mark.
## Comment 27601
Date: 2020-03-16 18:37:35 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [4d2d38fdc3d5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4d2d38fdc3d5) made by Pedro Ferreira <pedro.ferreira@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [https//devmonetdborg/hg/MonetDB?cmd=changeset;node=4d2d38fdc3d5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=https//devmonetdborg/hg/MonetDB?cmd=changeset;node=4d2d38fdc3d5)
Changeset description:
Added fixes for bug related to bug #3741, ie when an error happens in the body of a trigger, throw the error. The trigger_action test is giving a wrong result, but I'm looking into it
| TRIGGER REFERENCING OLD ROW is using all rows in old table. | https://api.github.com/repos/MonetDB/MonetDB/issues/3741/comments | 0 | 2020-11-30T13:02:38Z | 2024-06-27T12:07:36Z | https://github.com/MonetDB/MonetDB/issues/3741 | 753,460,637 | 3,741 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-16 03:58:57 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2015-08-28 13:42:20 +0200
## Comment 20923
Date: 2015-06-16 03:58:57 +0200
From: @skinkie
Created attachment 337
Add the external epoch function for timestamp with time zone
With the latest default branch epoch(now()) does not operate anymore. It seems because now includes a timezone.
> Attached file: [timestamp-with-zone.diff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3740_timestamp-with-zone.diff_337) (application/octet-stream, 395 bytes)
> Description: Add the external epoch function for timestamp with time zone
## Comment 20948
Date: 2015-06-28 13:36:54 +0200
From: @njnes
fixed ie applied patch..
## Comment 21210
Date: 2015-08-28 13:42:20 +0200
From: @sjoerdmullender
Jul2015 has been released.
| select epoch(now()); types timestamptz(7,0) and bigint(64,0) are not equal | https://api.github.com/repos/MonetDB/MonetDB/issues/3740/comments | 0 | 2020-11-30T13:02:35Z | 2024-06-27T12:07:36Z | https://github.com/MonetDB/MonetDB/issues/3740 | 753,460,609 | 3,740 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-15 13:39:35 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2017-02-22 09:43:21 +0100
## Comment 20922
Date: 2015-06-15 13:39:35 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
a NULL inside the () gets no respect
Reproducible: Always
### Steps to Reproduce:
correctly (i think) returns both
> dbGetQuery( db , "SELECT * FROM ( VALUES ( 1 , 2 ) , ( 3 , NULL ) ) AS z ( L1 , L2 ) WHERE L2 IN ( 2 , NULL )" )
l1 l2
1 1 2
2 3 NA
INCORRECTLY recodes the second row as "no" even though it should be "yes"
> dbGetQuery( db , "SELECT CASE WHEN L2 IN ( 2 , NULL ) THEN 'yes' ELSE 'no' END FROM ( VALUES ( 1 , 2 ) , ( 3 , NULL ) ) AS z ( L1 , L2 ) " )
ifthenelse_isnull_or_=_l2
1 yes
2 no
>
>
### Actual Results:
see reproduction
### Expected Results:
"yes" "yes"
nuthin. thanks!
## Comment 20946
Date: 2015-06-28 10:17:09 +0200
From: @njnes
Anthony. The problems is the handling of nulls. Null != Null in (most) of sql's statements. We incorrectly matched null's in 'in' handling. This is fixed now in the jul2015 branch
## Comment 21196
Date: 2015-08-28 13:41:57 +0200
From: @sjoerdmullender
Jul2015 has been released.
## Comment 25052
Date: 2017-02-22 09:43:21 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [f5282a08aeef](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f5282a08aeef) 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=f5282a08aeef](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f5282a08aeef)
Changeset description:
Generate algebra.thetasubselect instead of algebra.subselect.
thetaselect never matches nil, select may in certain conditions match
nil. It's easier to use thetaselect than to work around select.
This causes test null_is_null.Bug-3739 to behave properly again.
| CASE statements do not handle NULLs in the IN () operator properly | https://api.github.com/repos/MonetDB/MonetDB/issues/3739/comments | 0 | 2020-11-30T13:02:33Z | 2024-06-27T12:07:35Z | https://github.com/MonetDB/MonetDB/issues/3739 | 753,460,579 | 3,739 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-12 18:09:44 +0200
From: Frédéric Jolliton <<frederic.jolliton+monetdb>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:42:52 +0200
## Comment 20921
Date: 2015-06-12 18:09:44 +0200
From: Frédéric Jolliton <<frederic.jolliton+monetdb>>
We're studying MonetDB for some time now, but we found yet another bug that worry us. We found that an article[1] on the MonetDB mailing list from 10 (ten) years ago reported the exact same problem. So, maybe it's a regression, or that nobody use SAVEPOINT (or we are using them incorrectly.)
Step to reproduce (here on command line, but same from a Python using the MonetDB modules):
> $ mclient test
> START TRANSACTION;
> CREATE TABLE foo (a int);
> SAVEPOINT sp;
> RELEASE SAVEPOINT sp;
> COMMIT;
> SELECT * FROM foo;
[ok]
Start another session:
> $ mclient test
> SELECT * FROM foo;
SELECT: no such table 'foo'
The table seems to vanish at some point.
We got more curious error while testing this (like the table being listed in the system table `tables', but DROP test; reported that it was unknown.) At some other point, instead of getting the error "No such table" we got something completly unrelated: "monetdb.exceptions.DatabaseError: CREATE FUNCTION: name 'right_shift' (inet, inet) already in use". That is really puzzling.
I can provide more details if necessary. We made some automated tests to reproduce that.
Are we doing something wrong? We tested that both on Oct2014-SP4 and development.
[1] https://www.monetdb.org/pipermail/developers-list/2005-September/000154.html
## Comment 20951
Date: 2015-07-01 17:10:47 +0200
From: @njnes
savepoint had multiple problems (which should now be fixed). Added the test.
## Comment 20959
Date: 2015-07-02 18:08:15 +0200
From: Frédéric Jolliton <<frederic.jolliton+monetdb>>
Wonderful! We're going to test that next week.
## Comment 21219
Date: 2015-08-28 13:42:52 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Database inconsistency when using savepoint | https://api.github.com/repos/MonetDB/MonetDB/issues/3738/comments | 0 | 2020-11-30T13:02:31Z | 2024-06-27T12:07:34Z | https://github.com/MonetDB/MonetDB/issues/3738 | 753,460,551 | 3,738 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-11 12:30:11 +0200
From: Jerry Evans <<g4>>
To: Merovingian devs <<bugs-merovingian>>
Version: 11.21.19 (Jul2015-SP4)
Last updated: 2016-04-11 11:24:27 +0200
## Comment 20919
Date: 2015-06-11 12:30:11 +0200
From: Jerry Evans <<g4>>
Would it be possible to add the header files for requisite 3rd party libraries to the Monet tarballs? This would vastly simplify building/debugging on Windows. Right now there is a considerable amount of pain involved in acquiring/building/installing matching versions of the lib/dll files on Windows.
BR.
Jerry
## Comment 20924
Date: 2015-06-16 14:36:49 +0200
From: @sjoerdmullender
I have made available the compiled libraries that we use to build the MonetDB suite. See http://dev.monetdb.org/Windows/ and descend into the Libraries subdirectory.
Is this enough for you?
## Comment 20925
Date: 2015-06-16 16:03:31 +0200
From: Jerry Evans <<g4>>
Hello Sjoerd, that looks very promising except for Apache complaining :)
'The requested URL /Windows/ was not found on this server.'
BR.
## Comment 20926
Date: 2015-06-16 17:21:59 +0200
From: @sjoerdmullender
Sorry, make that http://dev.monetdb.org/downloads/Windows
## Comment 20927
Date: 2015-06-16 17:53:01 +0200
From: Jerry Evans <<g4>>
Nearly :)
'You don't have permission to access /downloads/Windows/Libraries/libs-win64.zip on this server.'
## Comment 20928
Date: 2015-06-16 23:05:05 +0200
From: @sjoerdmullender
Now it works.
Sorry for that.
## Comment 20930
Date: 2015-06-19 13:25:29 +0200
From: Jerry Evans <<g4>>
Hello Sjoerd
Excellent, thank you. I really hope this means the project gets more feedback from Windows developers.
I'll try some builds and report back.
BR.
Jerry
| Simplify building on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/3737/comments | 0 | 2020-11-30T13:02:29Z | 2024-06-28T13:14:37Z | https://github.com/MonetDB/MonetDB/issues/3737 | 753,460,528 | 3,737 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-10 08:48:01 +0200
From: Wiest Dennis <<Dennis.Wiest>>
To: SQL devs <<bugs-sql>>
Version: 11.19.15 (Oct2014-SP4)
CC: @njnes
Last updated: 2015-08-28 13:41:48 +0200
## Comment 20912
Date: 2015-06-10 08:48:01 +0200
From: Wiest Dennis <<Dennis.Wiest>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
Hello,
I'm new here. I have the following problem. I have a database that looks like this (see end of email). Now I want to issue the following query.
Select b. * FROM open_auctions o, b bidder WHERE (select b3.INCREASE from bidder b3 where b3.id = (select min (b3a.id) from bidder b3a where b3a.open_auction_id = o.open_auction_id)) * 2 <= (Select b2.INCREASE from bidder b2 where b2.id = (SELECT MAX (b2a.id) from bidder b2a where b2a.open_auction_id = o.open_auction_id)) AND o.open_auction_id = b.open_auction_id;
The database crashes. If I divide the query individually and settled it works flawlessly.
Other complex query also work. Only in this query crashes the database. Can anyone help me further?
I installed MonetDB 11:19:11 64 bits on Redhat. 6
Thanks and Regards
Dennis
CREATE TABLE closed_auctions (
id int NOT NULL AUTO_INCREMENT,
seller varchar(255) NOT NULL,
buyer varchar(255) NOT NULL,
itemref varchar(255) NOT NULL,
price double NOT NULL,
date varchar(255) NOT NULL,
quantitiy int NOT NULL,
type varchar(255) NOT NULL,
PRIMARY KEY (id)
);
INSERT INTO `open_auctions` (`id`, `open_auction_id`, `initial`, `reserve`, `aktuell`, `privacy`, `itemref`, `seller`, `quantity`, `type`, `start`, `ende`) VALUES
(1, 'open_auction0', 210.62, 1540.75, 263.12, 'No', 'item0', 'person11', 1, 'Regular', '02/27/1998', '03/09/1999'),
(2, 'open_auction1', 69.64, 398.65, 168.64, '', 'item2', 'person10', 1, 'Featured', '06/14/1998', '02/27/1999'),
(3, 'open_auction2', 13.9, 0, 16.9, 'No', 'item3', 'person11', 1, 'Featured', '07/16/2000', '10/22/2000'),
(4, 'open_auction3', 17.12, 0, 179.12, '', 'item5', 'person13', 1, 'Featured', '02/01/2001', '07/22/1999'),
(5, 'open_auction4', 38.21, 116.91, 219.71, 'No', 'item7', 'person11', 4, 'Regular, Dutch', '08/05/2000', '01/09/1999'),
(6, 'open_auction5', 75.95, 174.84, 116.45, 'No', 'item9', 'person7', 1, 'Featured', '01/27/2001', '10/08/1999'),
(7, 'open_auction6', 67.27, 0, 77.77, 'Yes', 'item10', 'person14', 1, 'Featured', '12/15/2001', '07/13/1999'),
(8, 'open_auction7', 35.53, 133.36, 73.03, 'Yes', 'item12', 'person16', 1, 'Regular', '04/06/2001', '04/11/2000'),
(9, 'open_auction8', 92.54, 0, 101.54, '', 'item13', 'person12', 1, 'Regular', '10/20/1998', '02/04/2001'),
(10, 'open_auction9', 9.88, 0, 137.38, '', 'item14', 'person10', 1, 'Featured', '06/16/1998', '12/05/2000'),
(11, 'open_auction10', 86.28, 0, 239.28, 'Yes', 'item16', 'person8', 1, 'Featured', '06/26/2000', '02/04/1998'),
(12, 'open_auction11', 4.12, 24.53, 38.62, '', 'item17', 'person12', 1, 'Regular', '11/03/1999', '03/02/2000');
CREATE TABLE bidder (
id int NOT NULL AUTO_INCREMENT,
open_auction_id varchar(255) NOT NULL,
date varchar(255) NOT NULL,
time varchar(255) NOT NULL,
personref varchar(255) NOT NULL,
increase double NOT NULL,
PRIMARY KEY (id)
);
--
-- Daten für Tabelle `bidder`
--
INSERT INTO `bidder` (`id`, `open_auction_id`, `date`, `time`, `personref`, `increase`) VALUES
(1, 'open_auction0', '06/13/2001', '13:16:15', 'person0', 18),
(2, 'open_auction0', '09/18/2000', '11:29:44', 'person23', 12),
(3, 'open_auction0', '01/07/1998', '10:23:59', 'person14', 18),
(4, 'open_auction0', '07/10/2001', '14:00:39', 'person16', 4.5),
(5, 'open_auction1', '11/12/1998', '11:23:38', 'person20', 4.5),
(6, 'open_auction1', '10/02/2000', '22:48:00', 'person4', 15),
(7, 'open_auction1', '12/04/1998', '22:29:38', 'person23', 1.5),
(8, 'open_auction1', '06/22/1999', '12:43:47', 'person19', 15),
(9, 'open_auction1', '12/02/2001', '13:38:51', 'person15', 45),
(10, 'open_auction1', '11/12/2001', '04:50:27', 'person9', 6),
(11, 'open_auction1', '05/21/2001', '08:02:16', 'person5', 12),
(12, 'open_auction2', '12/04/2000', '14:03:16', 'person5', 3),
(13, 'open_auction3', '09/03/2000', '22:45:30', 'person8', 10.5),
(14, 'open_auction3', '08/18/1998', '17:13:40', 'person22', 25.5),
(15, 'open_auction3', '06/05/1998', '11:57:56', 'person19', 16.5),
(16, 'open_auction3', '09/20/1999', '00:39:18', 'person5', 46.5),
(17, 'open_auction3', '10/03/2001', '01:08:59', 'person23', 58.5),
(18, 'open_auction3', '02/17/2001', '07:13:32', 'person20', 4.5),
(19, 'open_auction4', '10/19/1998', '09:00:31', 'person7', 33),
(20, 'open_auction4', '03/11/2001', '01:59:02', 'person8', 9),
(21, 'open_auction4', '04/16/2001', '23:37:09', 'person8', 6),
(22, 'open_auction4', '03/06/1999', '12:19:57', 'person5', 4.5),
(23, 'open_auction4', '02/01/2000', '09:37:51', 'person21', 18),
(24, 'open_auction4', '01/09/1999', '19:31:44', 'person1', 31.5),
(25, 'open_auction4', '11/11/2001', '05:24:08', 'person16', 27),
(26, 'open_auction4', '11/19/1998', '16:16:17', 'person10', 7.5),
(27, 'open_auction4', '04/05/1999', '00:37:15', 'person17', 7.5),
(28, 'open_auction4', '09/14/1999', '12:00:43', 'person12', 37.5),
(29, 'open_auction5', '07/07/2000', '08:53:00', 'person15', 6),
(30, 'open_auction5', '08/06/2001', '10:16:15', 'person13', 4.5),
(31, 'open_auction5', '08/23/1999', '08:26:06', 'person17', 30),
(32, 'open_auction6', '01/23/2000', '17:14:42', 'person1', 10.5),
(33, 'open_auction7', '10/14/1999', '14:39:18', 'person16', 27),
(34, 'open_auction7', '05/19/1999', '23:51:16', 'person14', 9),
(35, 'open_auction7', '03/27/1999', '19:14:39', 'person23', 1.5),
(36, 'open_auction8', '04/26/2001', '00:41:04', 'person12', 9),
(37, 'open_auction9', '04/03/1999', '19:09:46', 'person22', 18),
(38, 'open_auction9', '01/21/1999', '08:14:44', 'person19', 19.5),
(39, 'open_auction9', '11/24/1999', '02:12:12', 'person11', 12),
(40, 'open_auction9', '01/07/2001', '05:33:55', 'person7', 9),
(41, 'open_auction9', '07/28/2000', '00:57:52', 'person16', 16.5),
(42, 'open_auction9', '01/28/2000', '20:24:02', 'person23', 1.5),
(43, 'open_auction9', '05/13/2001', '02:45:46', 'person13', 1.5),
(44, 'open_auction9', '12/06/2000', '15:18:07', 'person21', 24),
(45, 'open_auction9', '08/16/1998', '09:27:27', 'person14', 3),
(46, 'open_auction9', '06/18/2001', '19:57:53', 'person7', 3),
(47, 'open_auction9', '12/13/2001', '09:01:23', 'person2', 12),
(48, 'open_auction9', '03/18/2001', '08:59:02', 'person13', 7.5),
(49, 'open_auction10', '08/14/1998', '16:33:46', 'person23', 33),
(50, 'open_auction10', '03/24/1998', '11:45:48', 'person3', 1.5),
(51, 'open_auction10', '10/08/1998', '06:20:35', 'person1', 45),
(52, 'open_auction10', '01/12/1998', '21:43:02', 'person3', 15),
(53, 'open_auction10', '03/02/2001', '20:20:33', 'person0', 9),
(54, 'open_auction10', '03/01/2000', '10:08:07', 'person23', 10.5),
(55, 'open_auction10', '07/19/2001', '00:50:29', 'person6', 9),
(56, 'open_auction10', '10/04/2001', '00:58:25', 'person4', 3),
(57, 'open_auction10', '11/27/1998', '00:15:23', 'person21', 27),
(58, 'open_auction11', '05/16/1998', '15:08:01', 'person1', 15),
(59, 'open_auction11', '05/08/2000', '06:44:20', 'person3', 4.5),
(60, 'open_auction11', '10/22/2001', '15:34:49', 'person4', 15);
Reproducible: Always
### Steps to Reproduce:
1. Create Tables
2. Insert Data
3. Execute Query looking on Details
### Actual Results:
The Database Crashed and gives this in the log file
2015-06-10 06:39:38 MSG merovingian[7145]: Merovingian 1.7 (Oct2014-SP3) starting
2015-06-10 06:39:38 MSG merovingian[7145]: monitoring dbfarm /mnt/u60/home/axlavs/dennis/monetdb
2015-06-10 06:39:58 MSG merovingian[7145]: accepting connections on TCP socket 0.0.0.0:50000
2015-06-10 06:39:58 MSG merovingian[7145]: accepting connections on UNIX domain socket /tmp/.s.monetdb.50000
2015-06-10 06:40:18 MSG discovery[7145]: listening for UDP messages on :50000
2015-06-10 06:40:18 MSG control[7145]: accepting connections on UNIX domain socket /tmp/.s.merovingian.50000
2015-06-10 06:40:18 MSG discovery[7145]: new neighbour weac-cn2.axl.intra (weac-cn2.axl.intra)
2015-06-10 06:40:20 MSG discovery[7145]: new database mapi:monetdb://weac-cn2.axl.intra:50000/xmarktest (ttl=660s)
2015-06-10 06:40:20 MSG discovery[7145]: new database mapi:monetdb://weac-cn2.axl.intra:50000/aixm (ttl=660s)
2015-06-10 06:40:20 MSG discovery[7145]: new database mapi:monetdb://weac-cn2.axl.intra:50000/xmark (ttl=660s)
2015-06-10 06:40:49 MSG merovingian[7145]: starting database 'xmarktest', up min/avg/max: 33m/2d/4d, crash average: 0.00 0.80 0.30 (11-2=9)
2015-06-10 06:40:49 MSG merovingian[7145]: proxying client (local) for database 'xmarktest' to mapi:monetdb:///mnt/u60/home/axlavs/dennis/monetdb/xmarktest/.mapi.sock?database=xmarktest
2015-06-10 06:40:49 MSG merovingian[7145]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2015-06-10 06:40:49 MSG xmarktest[12823]: arguments: /usr/bin/mserver5 --dbpath=/mnt/u60/home/axlavs/dennis/monetdb/xmarktest --set merovingian_uri=mapi:monetdb://weac-cn2.axl.intra:50000/xmarktest --set mapi_open=false --set mapi_port=0 --set mapi_usock=/mnt/u60/home/axlavs/dennis/monetdb/xmarktest/.mapi.sock --set monet_vault_key=/mnt/u60/home/axlavs/dennis/monetdb/xmarktest/.vaultkey --set gdk_nr_threads=32 --set max_clients=64 --set sql_optimizer=default_pipe --set monet_daemon=yes
2015-06-10 06:40:49 MSG xmarktest[12823]: MonetDB 5 server v11.19.11 "Oct2014-SP3"
2015-06-10 06:40:49 MSG xmarktest[12823]: Serving database 'xmarktest', using 32 threads
2015-06-10 06:40:49 MSG xmarktest[12823]: Compiled for x86_64-redhat-linux-gnu/64bit with 64bit OIDs dynamically linked
2015-06-10 06:40:49 MSG xmarktest[12823]: Found 62.883 GiB available main-memory.
2015-06-10 06:40:49 MSG xmarktest[12823]: Copyright (c) 1993-July 2008 CWI.
2015-06-10 06:40:49 MSG xmarktest[12823]: Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
2015-06-10 06:40:49 MSG xmarktest[12823]: Visit http://www.monetdb.org/ for further information
2015-06-10 06:40:49 MSG xmarktest[12823]: Listening for UNIX domain connection requests on mapi:monetdb:///mnt/u60/home/axlavs/dennis/monetdb/xmarktest/.mapi.sock
2015-06-10 06:40:49 MSG xmarktest[12823]: MonetDB/GIS module loaded
2015-06-10 06:40:49 MSG xmarktest[12823]: MonetDB/SQL module loaded
2015-06-10 06:40:49 MSG merovingian[7145]: proxying client (local) for database 'xmarktest' to mapi:monetdb:///mnt/u60/home/axlavs/dennis/monetdb/xmarktest/.mapi.sock?database=xmarktest
2015-06-10 06:40:49 MSG merovingian[7145]: target connection is on local UNIX domain socket, passing on filedescriptor instead of proxying
2015-06-10 06:41:04 MSG merovingian[7145]: database 'xmarktest' (12823) was killed by signal SIGSEGV
### Expected Results:
Execute this Query like other Systems. Mysql Oracle etc...
## Comment 20913
Date: 2015-06-10 10:00:54 +0200
From: @njnes
could you also add the open_auctions create table statement.
## Comment 20914
Date: 2015-06-10 10:04:44 +0200
From: Wiest Dennis <<Dennis.Wiest>>
CREATE TABLE open_auctions (
id int NOT NULL AUTO_INCREMENT,
open_auction_id varchar(255) NOT NULL,
initial double NOT NULL,
reserve double NOT NULL,
aktuell double NOT NULL,
privacy varchar(255) NOT NULL,
itemref varchar(255) NOT NULL,
seller varchar(255) NOT NULL,
quantity double NOT NULL,
type varchar(255) NOT NULL,
start varchar(255) NOT NULL,
ende varchar(255) NOT NULL,
PRIMARY KEY (id)
);
sorry my mistake
## Comment 20915
Date: 2015-06-10 10:50:20 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [38c03afee6e7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=38c03afee6e7) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=38c03afee6e7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=38c03afee6e7)
Changeset description:
fixed bug #3736, protect agains empty expression lists
## Comment 20916
Date: 2015-06-10 10:51:31 +0200
From: @njnes
fixed in the stable branch. Added more protection against empty expression lists. Possibly the query will need some more optimization tricks. So lets us know if the performance isn't what you expect.
## Comment 20917
Date: 2015-06-10 11:00:40 +0200
From: Wiest Dennis <<Dennis.Wiest>>
Thanks Niels,
is its fixed in the sourcecode 11.19.11 ?? Or in the newest sourcecode?
Dennis
## Comment 20918
Date: 2015-06-10 11:24:13 +0200
From: @sjoerdmullender
It's fixed in the Oct2014 branch, in time for an Oct2014-SP5 release, if that ever materializes. Otherwise it will be in the next feature release.
## Comment 21187
Date: 2015-08-28 13:41:48 +0200
From: @sjoerdmullender
Jul2015 has been released.
| crash if mclient disconnects abruptly during a query | https://api.github.com/repos/MonetDB/MonetDB/issues/3736/comments | 0 | 2020-11-30T13:02:26Z | 2024-06-27T12:07:32Z | https://github.com/MonetDB/MonetDB/issues/3736 | 753,460,494 | 3,736 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-09 15:28:05 +0200
From: Guillaume Savary <<guillaume.savary>>
To: clients devs <<bugs-clients>>
Version: -- development
Last updated: 2015-08-28 13:41:53 +0200
## Comment 20911
Date: 2015-06-09 15:28:05 +0200
From: Guillaume Savary <<guillaume.savary>>
It seems you cannot connect to the server with unix_socket. The hostname is forced to 'localhost'.
Here is the patch to apply on python2. (Do the same for python3) :
diff --git a/clients/python2/monetdb/mapi.py b/clients/python2/monetdb/mapi.py
index 1535836..1e6e515 100644
--- a/clients/python2/monetdb/mapi.py
+++ b/clients/python2/monetdb/mapi.py
@@ -73,7 +73,7 @@ class Connection(object):
hostname = None
if not unix_socket and os.path.exists("/tmp/.s.monetdb.%i" % port):
unix_socket = "/tmp/.s.monetdb.%i" % port
- elif not hostname:
+ elif not unix_socket and not hostname:
hostname = 'localhost'
self.hostname = hostname
## Comment 21069
Date: 2015-07-30 13:07:42 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [c1ba05ee9a5e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c1ba05ee9a5e) 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=c1ba05ee9a5e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c1ba05ee9a5e)
Changeset description:
Applied patch from bug #3735.
## Comment 21070
Date: 2015-07-30 13:08:18 +0200
From: @sjoerdmullender
Thanks. Your patch looks good.
## Comment 21192
Date: 2015-08-28 13:41:53 +0200
From: @sjoerdmullender
Jul2015 has been released.
| python connection with unix_socket | https://api.github.com/repos/MonetDB/MonetDB/issues/3735/comments | 0 | 2020-11-30T13:02:24Z | 2024-06-27T12:07:31Z | https://github.com/MonetDB/MonetDB/issues/3735 | 753,460,474 | 3,735 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-03 14:35:11 +0200
From: Robin Cijvat <<robin.cijvat>>
To: clients devs <<bugs-clients>>
Version: 11.21.19 (Jul2015-SP4)
Last updated: 2016-04-11 11:18:32 +0200
## Comment 20904
Date: 2015-06-03 14:35:11 +0200
From: Robin Cijvat <<robin.cijvat>>
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Build Identifier:
Try running this with the NodeJS client:
create table t (a string);
insert into t values ('\t'), ('\\t');
If you check out the contents of table t now, you see that both tuples have '\t' (tab) in them.
Simple fixes for this clash with the use case on the quoting fun from the test file, so be careful there.
Reproducible: Always
| NodeJS client: Inserting backslashes into the database does not work properly | https://api.github.com/repos/MonetDB/MonetDB/issues/3734/comments | 0 | 2020-11-30T13:02:21Z | 2024-06-28T13:14:37Z | https://github.com/MonetDB/MonetDB/issues/3734 | 753,460,450 | 3,734 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-06-02 21:15:07 +0200
From: Marvin Wang <<marvin>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-08-28 13:42:08 +0200
## Comment 20902
Date: 2015-06-02 21:15:07 +0200
From: Marvin Wang <<marvin>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
create table test (c1 int);
insert into test values(1);
SELECT * FROM test WHERE (true OR c1 = 3) AND c1 = 2; /* should return nothing*/
Reproducible: Always
### Steps to Reproduce:
create table test (c1 int);
insert into test values(1);
SELECT * FROM test WHERE (true OR c1 = 3) AND c1 = 2; /* should return nothing*/
### Actual Results:
return rows that should not match
### Expected Results:
should return nothing
## Comment 20907
Date: 2015-06-07 14:11:32 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [bdb78936d2ac](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=bdb78936d2ac) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bdb78936d2ac](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=bdb78936d2ac)
Changeset description:
fixed bug #3733, ie handle (constant (true/false) or predicate) expressions better.
## Comment 20908
Date: 2015-06-07 14:13:10 +0200
From: @njnes
fixed by handling or expressions with constants better
## Comment 21203
Date: 2015-08-28 13:42:08 +0200
From: @sjoerdmullender
Jul2015 has been released.
| "(TRUE OR <Exp>) AND <Exp>" is evaluated incorrectly | https://api.github.com/repos/MonetDB/MonetDB/issues/3733/comments | 0 | 2020-11-30T13:02:19Z | 2024-06-27T12:07:28Z | https://github.com/MonetDB/MonetDB/issues/3733 | 753,460,416 | 3,733 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-29 15:08:02 +0200
From: Richard Hughes <<richard.monetdb>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-08-28 13:42:00 +0200
## Comment 20899
Date: 2015-05-29 15:08:02 +0200
From: Richard Hughes <<richard.monetdb>>
Created attachment 335
proposed fix
3,984 bytes in 18 blocks are definitely lost in loss record 1,879 of 2,145
at 0x4C28C20: malloc (vg_replace_malloc.c:296)
by 0x5478F28: GDKmalloc_prefixsize (gdk_utils.c:652)
by 0x5478F28: GDKmallocmax (gdk_utils.c:678)
by 0x5478F28: GDKmalloc (gdk_utils.c:701)
by 0x4E78530: pushArgument (mal_instruction.c:1603)
by 0x4F8DDA0: mat_topn (opt_mergetable.c:1367)
by 0x4F91497: OPTmergetableImplementation (opt_mergetable.c:1541)
by 0x4FA5AF3: OPTwrapper (opt_wrapper.c:176)
by 0x4F9FE5B: optimizeMALBlock (opt_support.c:292)
by 0xDBD2E95: addQueryToCache (sql_optimizer.c:283)
by 0xDBD2630: backend_dumpproc (sql_gencode.c:2703)
by 0xDBB6FB8: SQLparser (sql_scenario.c:2535)
by 0x4E96018: runPhase (mal_scenario.c:526)
by 0x4E96018: runScenarioBody (mal_scenario.c:561)
by 0x4E96CCC: runScenario (mal_scenario.c:590)
by 0x4E97157: MSserveClient (mal_session.c:450)
by 0x4E9774E: MSscheduleClient (mal_session.c:330)
by 0x4F3C545: doChallenge (mal_mapi.c:192)
by 0x5502F4E: thread_starter (gdk_system.c:535)
by 0x669F0A3: start_thread (pthread_create.c:309)
by 0x699A04C: clone (clone.S:111)
[line numbers are against Oct2014 head as of today (66be10fc2789), i.e. http://dev.monetdb.org/hg/MonetDB/file/9bfe2441d4a3/monetdb5/optimizer/opt_mergetable.c]
I'm not actually sure what query caused this - I noticed memory leaking so I just ran an entire day's worth of queries under valgrind to see what came out. If you need more information then let me know and I'll try to narrow it down a bit better.
The attached patch fixes what I reckon is causing the leak of 'pck', and also tweaks the handling of 'gpck' which looks wrong to me as well (although I don't know what query to run to cause that code path to execute). Please check my work carefully because I'm not very confident about the correctness of this patch.
> Attached file: [opt_mergetable-leak.diff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3732_opt_mergetable-leak.diff_335) (text/plain, 775 bytes)
> Description: proposed fix
## Comment 20909
Date: 2015-06-08 13:57:08 +0200
From: Richard Hughes <<richard.monetdb>>
Here's a repro for you:
create table foo (a int);
insert into foo (a) select * from generate_series(cast(0 as int),5000);
select a from foo order by a limit 10;
The select statement will cause:
232 bytes in 1 blocks are definitely lost in loss record 1,473 of 1,966
at 0x4C28C20: malloc (vg_replace_malloc.c:296)
by 0x5478F28: GDKmalloc_prefixsize (gdk_utils.c:652)
by 0x5478F28: GDKmallocmax (gdk_utils.c:678)
by 0x5478F28: GDKmalloc (gdk_utils.c:701)
by 0x4E78530: pushArgument (mal_instruction.c:1603)
by 0x4F8DDA0: mat_topn (opt_mergetable.c:1367)
by 0x4F91497: OPTmergetableImplementation (opt_mergetable.c:1541)
by 0x4FA5AF3: OPTwrapper (opt_wrapper.c:176)
by 0x4F9FE5B: optimizeMALBlock (opt_support.c:292)
by 0xDBD2E95: addQueryToCache (sql_optimizer.c:283)
by 0xDBD2630: backend_dumpproc (sql_gencode.c:2703)
by 0xDBB6FB8: SQLparser (sql_scenario.c:2535)
by 0x4E96018: runPhase (mal_scenario.c:526)
by 0x4E96018: runScenarioBody (mal_scenario.c:561)
by 0x4E96CCC: runScenario (mal_scenario.c:590)
by 0x4E97157: MSserveClient (mal_session.c:450)
by 0x4E9774E: MSscheduleClient (mal_session.c:330)
by 0x4F3C545: doChallenge (mal_mapi.c:192)
by 0x5502F4E: thread_starter (gdk_system.c:535)
by 0x669F0A3: start_thread (pthread_create.c:309)
by 0x699A04C: clone (clone.S:111)
## Comment 20991
Date: 2015-07-10 21:20:58 +0200
From: @njnes
fixed in jul2015 branch, the generators optimizer leaked
## Comment 20998
Date: 2015-07-14 11:46:23 +0200
From: Richard Hughes <<richard.monetdb>>
Still reproducible in Jul2015 (3f8fe587d596), I'm afraid.
My repro in Comment 1 is flawed. Change the insert to:
insert into foo (a) select * from generate_series(cast(0 as int),500000);
and you can reproduce without forcemito. It's definitely the select statement that's doing it because I'm restarting mserver5 between the insert and select.
184 bytes in 1 blocks are definitely lost in loss record 1,327 of 1,811
at 0x4C28C20: malloc (vg_replace_malloc.c:296)
by 0x56B6487: GDKmalloc_prefixsize (gdk_utils.c:641)
by 0x56B653E: GDKmallocmax (gdk_utils.c:667)
by 0x56B6646: GDKmalloc (gdk_utils.c:690)
by 0x4E8543B: pushArgument (mal_instruction.c:1582)
by 0x5045E7D: mat_topn (opt_mergetable.c:1371)
by 0x5046DD9: OPTmergetableImplementation (opt_mergetable.c:1548)
by 0x505D8F8: OPTwrapper (opt_wrapper.c:149)
by 0x5058787: optimizeMALBlock (opt_support.c:262)
by 0xF488011: addQueryToCache (sql_optimizer.c:294)
by 0xF485BA5: backend_dumpproc (sql_gencode.c:2804)
by 0xF451D9B: SQLparser (sql_scenario.c:1178)
## Comment 21068
Date: 2015-07-29 17:30:28 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [3ded79fe4907](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3ded79fe4907) 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=3ded79fe4907](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3ded79fe4907)
Changeset description:
Don't claim instruction was pushed when it wasn't.
ml->v[piv] refers to the instruction "pck" that was added by the
mat_add_var call. That instruction is never added to the MAL plan.
This should fix bug #3732.
## Comment 21071
Date: 2015-07-30 13:09:10 +0200
From: @sjoerdmullender
I'll go out on a limb and say this bug has now been fixed.
## Comment 21072
Date: 2015-07-31 11:16:10 +0200
From: Richard Hughes <<richard.monetdb>>
Confirmed. Thanks Sjoerd.
## Comment 21197
Date: 2015-08-28 13:42:00 +0200
From: @sjoerdmullender
Jul2015 has been released.
| memory leak (of InstrRecord) in opt_mergetable | https://api.github.com/repos/MonetDB/MonetDB/issues/3732/comments | 0 | 2020-11-30T13:02:16Z | 2024-06-27T12:07:27Z | https://github.com/MonetDB/MonetDB/issues/3732 | 753,460,378 | 3,732 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-28 21:01:37 +0200
From: Raffy <<raffy>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-06-22 22:32:17 +0200
## Comment 20898
Date: 2015-05-28 21:01:37 +0200
From: Raffy <<raffy>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier:
As a non-system user on a non-system schema, using the left_shift does not work:
select * from ip_range where ip << inet '10.0.0.0/8’
SELECT: no such binary operator 'left_shift(inet,inet)'
Doing the same table as moentdb user with the same query, works as intended.
Workaround that works:
select * from test where sys.left_shift(a, inet '10.0.0.0/8');
Reproducible: Always
### Steps to Reproduce:
use a non system user and a non-sys schema
create table test (a inet);
insert into test (a) values ('10.0.0.1’);
select * from test where a << inet '10.0.0.0/8’;
SELECT: no such binary operator 'left_shift(inet,inet)'
## Comment 20901
Date: 2015-06-02 13:51:03 +0200
From: @njnes
fixed, we now always pass the proper schema info (ie sys).
| left shift for IP addresses not available to non-system users | https://api.github.com/repos/MonetDB/MonetDB/issues/3731/comments | 0 | 2020-11-30T13:02:14Z | 2024-06-27T12:07:26Z | https://github.com/MonetDB/MonetDB/issues/3731 | 753,460,352 | 3,731 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-28 09:58:52 +0200
From: Anthony Damico <<ajdamico>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: ajdamico, @hannesmuehleisen, @njnes
Last updated: 2015-08-28 13:41:54 +0200
## Comment 20895
Date: 2015-05-28 09:58:52 +0200
From: Anthony Damico <<ajdamico>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
if you have a column with only two rows, the SAMPLE function does not pick each approximately 50% of the time. something is biasing the SAMPLE draws.
Reproducible: Always
### Steps to Reproduce:
here's the sql command.
SELECT * FROM ( SELECT 1 AS col UNION ALL SELECT 2 AS col ) AS temp SAMPLE 1;
but you have to run it a thousand times, however you prefer. here's the R code to do that with MonetDB.R--
here's a reproducible example using R code to repeat the sampling 1000 times. in both SAMPLE examples below, the database pulls the 2 less than 200 times out of 1000. shouldn't it be close to 500 out of 1000? this seems not random (misleading to users?) sorry if i'm misunderstanding something.. thank you!!
start in an empty directory somewhere
setwd( "C:/My Directory/MonetDB" )
START OF SETUP - no editing required
library(MonetDB.R)
batfile <-
monetdb.server.setup(
database.directory = paste0( getwd() , "/MonetDB" ) ,
monetdb.program.path =
ifelse(
.Platform$OS.type == "windows" ,
"C:/Program Files/MonetDB/MonetDB5" ,
""
) ,
dbname = "test" ,
dbport = 50000
)
pid <- monetdb.server.start( batfile )
db <- dbConnect( MonetDB.R() , "monetdb://localhost:50000/test" , wait = TRUE )
END OF SETUP
dbGetQuery( db , "SELECT 1 AS col UNION ALL SELECT 2 AS col" )
out <- NULL
for ( i in 1:1000 ){
out <- c( out , dbGetQuery( db , "SELECT * FROM ( SELECT 1 AS col UNION ALL SELECT 2 AS col ) AS temp SAMPLE 0.5" ) )
}
not random
table( unlist( out ) )
1 2
880 120
out <- NULL
for ( i in 1:1000 ){
out <- c( out , dbGetQuery( db , "SELECT * FROM ( SELECT 1 AS col UNION ALL SELECT 2 AS col ) AS temp SAMPLE 1" ) )
}
ALSO not random
table( unlist( out ) )
1 2
856 144
### Actual Results:
in both of the above examples of R output, more than 4 out of 5 draws were 1s instead of 2s.
### Expected Results:
half 1s half 2s
## Comment 20900
Date: 2015-06-02 13:50:32 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [91c472eabc48](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=91c472eabc48) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=91c472eabc48](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=91c472eabc48)
Changeset description:
fixed bug #3730, ie always pass the schema ('sys') for operators
## Comment 20903
Date: 2015-06-03 14:20:44 +0200
From: @hannesmuehleisen
Looking into this, in particular the behaviour of rand() on our beloved Windows.
## Comment 20905
Date: 2015-06-03 15:26:08 +0200
From: @hannesmuehleisen
Could not reproduce on Windows 7 Professional (64bits) with MonetDB Oct2014-SP3, both 32 and 64bits. Also could not find any flaw with random number generator on Windows.
## Comment 21114
Date: 2015-08-10 20:41:20 +0200
From: Anthony Damico <<ajdamico>>
sorry, this has not been fixed on windows using the Jul2015 release
> table( unlist( out ) )
1 2
832 168
> table( unlist( out ) )
1 2
830 170
MonetDB 5 server v11.21.1 "Jul2015"
Serving database 'test', using 8 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 15.914 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
Start processing logs sql/sql_logs version 52200
Finished processing logs sql/sql_logs
MonetDB/SQL module loaded
>
## Comment 21116
Date: 2015-08-11 14:56:41 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [29e2ba371d58](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=29e2ba371d58) 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=29e2ba371d58](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=29e2ba371d58)
Changeset description:
On Windows, rand() is per thread, so call srand on thread start.
This should fix bug #3730.
## Comment 21118
Date: 2015-08-11 15:22:27 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [5c206e0510fe](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5c206e0510fe) made by Hannes Muehleisen <hannes@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5c206e0510fe](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5c206e0510fe)
Changeset description:
Attempt at a test case for Bug #3730
## Comment 21162
Date: 2015-08-23 19:45:49 +0200
From: Anthony Damico <<ajdamico>>
just tested this- looks like it's been solved on the latest testing version. thanks thanks!!
MonetDB 5 server v11.21.3 "Jul2015"
Serving database 'test', using 8 threads
Compiled for x86_64-pc-winnt/64bit with 64bit OIDs dynamically linked
Found 15.914 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
Start processing logs sql/sql_logs version 52200
Finished processing logs sql/sql_logs
MonetDB/SQL module loaded
>
## Comment 21193
Date: 2015-08-28 13:41:54 +0200
From: @sjoerdmullender
Jul2015 has been released.
| SAMPLE function not sampling randomly | https://api.github.com/repos/MonetDB/MonetDB/issues/3730/comments | 0 | 2020-11-30T13:02:12Z | 2024-06-27T12:07:25Z | https://github.com/MonetDB/MonetDB/issues/3730 | 753,460,324 | 3,730 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-26 08:06:05 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-05-27 10:52:34 +0200
## Comment 20885
Date: 2015-05-26 08:06:05 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Build Identifier:
After pulling the latest Oct2014 code I have noticed that my import scripts failed this morning. I quickly figured out that the cause was invalid column names. My queries create a new table using CREATE TABLE newtable AS SELECT ... WITH DATA; The following quick test shows what is unexpected:
CREATE TABLE "sys"."a" (
"a" INTEGER
);
MonetDB:
select cast(a as text) from a;
+------+
| L1 |
+======+
| 1 |
+------+
PostgreSQL:
select cast(a as text) from a;
a
---
1
I wouldn't expect such functionality to change within a stable release.
Reproducible: Always
MonetDB 5 server v11.19.14 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -O3 -pipe -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 20890
Date: 2015-05-27 10:02:39 +0200
From: @njnes
a function call (cast) was made, sql doesn't define what column names to use in that case.
## Comment 20892
Date: 2015-05-27 10:52:34 +0200
From: @skinkie
(In reply to comment 1)
> a function call (cast) was made, sql doesn't define what column names to use
> in that case.
What was the rationale to change the behavior?
| Within the Oct2014 casts don't take the labels of their original column names anymore | https://api.github.com/repos/MonetDB/MonetDB/issues/3729/comments | 0 | 2020-11-30T13:02:08Z | 2024-06-28T13:14:36Z | https://github.com/MonetDB/MonetDB/issues/3729 | 753,460,279 | 3,729 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-26 07:46:10 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
Duplicates: #3727
Last updated: 2015-05-26 08:39:44 +0200
## Comment 20884
Date: 2015-05-26 07:46:10 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Build Identifier:
When currently performing a topn (limit n) on a union all or union table, the union is first computed. Given that only the first n samples are asked the operation might succeed by just operating the limit on the first table in the union (all). Hence: saving a lot of effort. The success of the operation can be computed if the length of any of the tables in the union is less than the topn requested.
Reproducible: Always
## Comment 20888
Date: 2015-05-26 08:39:44 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #3727 ***
| Perform topn before union (all) | https://api.github.com/repos/MonetDB/MonetDB/issues/3728/comments | 0 | 2020-11-30T13:02:05Z | 2024-06-28T07:19:45Z | https://github.com/MonetDB/MonetDB/issues/3728 | 753,460,234 | 3,728 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-26 07:45:19 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @PedroTadim
Last updated: 2020-08-26 11:44:50 +0200
## Comment 20883
Date: 2015-05-26 07:45:19 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Build Identifier:
When currently performing a topn (limit n) on a union all or union table, the union is first computed. Given that only the first n samples are asked the operation might succeed by just operating the limit on the first table in the union (all). Hence: saving a lot of effort. The success of the operation can be computed if the length of any of the tables in the union is less than the topn requested.
Reproducible: Always
## Comment 20889
Date: 2015-05-26 08:39:44 +0200
From: @sjoerdmullender
*** Bug #3728 has been marked as a duplicate of this bug. ***
| Perform topn before union (all) | https://api.github.com/repos/MonetDB/MonetDB/issues/3727/comments | 0 | 2020-11-30T13:02:03Z | 2024-06-27T12:07:22Z | https://github.com/MonetDB/MonetDB/issues/3727 | 753,460,205 | 3,727 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-26 02:33:04 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
Duplicates: #3725
Last updated: 2015-05-26 08:38:40 +0200
## Comment 20882
Date: 2015-05-26 02:33:04 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Build Identifier:
create table a (a integer);
create table b (a integer);
insert into a values (1);
select * from a left join (select a, 20 from b) as x using (a);
I expect:
1, NULL
In MonetDB I get:
+------+------+
| a | L2 |
+======+======+
| 1 | 20 |
+------+------+
1 tuple (4.655ms)
In PostgreSQL I get:
a | ?column?
---+----------
1 |
(1 row)
My original code depends on summing a column that should be 0 if the values are null. For some reason all values were 1, indicating a row was always joinable. It seems the above query has a problem with the constant, which in my own code was a true or 1.
Reproducible: Always
MonetDB 5 server v11.17.22 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 20886
Date: 2015-05-26 08:38:40 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #3725 ***
| LEFT JOIN bug with CONST value | https://api.github.com/repos/MonetDB/MonetDB/issues/3726/comments | 0 | 2020-11-30T13:02:00Z | 2024-06-28T13:14:35Z | https://github.com/MonetDB/MonetDB/issues/3726 | 753,460,178 | 3,726 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-26 02:31:13 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2016-01-22 13:51:48 +0100
## Comment 20881
Date: 2015-05-26 02:31:13 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/43.0.2357.65 Safari/537.36
Build Identifier:
create table a (a integer);
create table b (a integer);
insert into a values (1);
select * from a left join (select a, 20 from b) as x using (a);
I expect:
1, NULL
In MonetDB I get:
+------+------+
| a | L2 |
+======+======+
| 1 | 20 |
+------+------+
1 tuple (4.655ms)
In PostgreSQL I get:
a | ?column?
---+----------
1 |
(1 row)
My original code depends on summing a column that should be 0 if the values are null. For some reason all values were 1, indicating a row was always joinable. It seems the above query has a problem with the constant, which in my own code was a true or 1.
Reproducible: Always
MonetDB 5 server v11.17.22 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 20887
Date: 2015-05-26 08:38:40 +0200
From: @sjoerdmullender
*** Bug #3726 has been marked as a duplicate of this bug. ***
## Comment 20891
Date: 2015-05-27 10:45:23 +0200
From: @njnes
we pushed up the project with the constant through a left join. This is not correct. ie fixed.
## Comment 20893
Date: 2015-05-27 10:59:39 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e0163d1455fc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e0163d1455fc) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e0163d1455fc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e0163d1455fc)
Changeset description:
fixed bug #3725, ie don't push projections up through outer joins
## Comment 21740
Date: 2016-01-22 13:51:48 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [7e4e36ee55f0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7e4e36ee55f0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7e4e36ee55f0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7e4e36ee55f0)
Changeset description:
cleaner solutions for bug #3725 (ie push up projections in outerjoins)
| LEFT JOIN bug with CONST value | https://api.github.com/repos/MonetDB/MonetDB/issues/3725/comments | 0 | 2020-11-30T13:01:58Z | 2024-06-27T12:07:20Z | https://github.com/MonetDB/MonetDB/issues/3725 | 753,460,157 | 3,725 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-11 17:20:09 +0200
From: @swingbit
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-08-28 13:42:54 +0200
## Comment 20861
Date: 2015-05-11 17:20:09 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Build Identifier:
While looking at a different issue, I noticed with gdb that lsize and rsize as computed in BATsubjoin are way too large.
/* some statistics to help us decide */
lsize = (BUN) (BATcount(l) * (Tsize(l) + (l->T->vheap ? l->T->vheap->size : 0) + 2 * sizeof(BUN)));
rsize = (BUN) (BATcount(r) * (Tsize(r) + (r->T->vheap ? r->T->vheap->size : 0) + 2 * sizeof(BUN)));
I suspect a parenthesis is misplaced and this should be:
lsize = (BUN) (BATcount(l) * (Tsize(l)) + (l->T->vheap ? l->T->vheap->size : 0) + 2 * sizeof(BUN));
rsize = (BUN) (BATcount(r) * (Tsize(r)) + (r->T->vheap ? r->T->vheap->size : 0) + 2 * sizeof(BUN));
Reproducible: Always
## Comment 20992
Date: 2015-07-10 21:30:22 +0200
From: @njnes
your so right, applied the changes to the jul2015 branch
## Comment 21222
Date: 2015-08-28 13:42:54 +0200
From: @sjoerdmullender
Jul2015 has been released.
| Wrong size calculation in BATsubjoin | https://api.github.com/repos/MonetDB/MonetDB/issues/3724/comments | 0 | 2020-11-30T13:01:55Z | 2024-06-27T12:07:19Z | https://github.com/MonetDB/MonetDB/issues/3724 | 753,460,132 | 3,724 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-11 15:45:50 +0200
From: Richard Hughes <<richard.monetdb>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-06-22 22:32:22 +0200
## Comment 20860
Date: 2015-05-11 15:45:50 +0200
From: Richard Hughes <<richard.monetdb>>
To reproduce:
sql>create table foo (a int);
sql>select b from(select 1,1=1,1,1,1 from foo union all select 1,null,1,1,1)as t(a,b,c,d,e);
Expected result:
null
Actual result:
mserver5: rel_bin.c:2548: rel2bin_groupby: Assertion `0' failed.
Aborted
That seems to be the simplest I can get the query. Removing some of those apparently-superfluous columns stops the assertion.
This used to work. Bisected to:
changeset: 55349:c891240ec139
branch: Oct2014
user: Niels Nes <niels@cwi.nl>
date: Sun Apr 19 21:50:46 2015 +0200
summary: on project rewrite check if the rewriten project expression
http://dev.monetdb.org/hg/MonetDB/rev/c891240ec139
## Comment 20863
Date: 2015-05-13 15:28:43 +0200
From: @njnes
fixed, added missing reset of a hash table after relational rewrites (renames).
## Comment 20864
Date: 2015-05-13 16:49:14 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [0b63993ab0ed](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0b63993ab0ed) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0b63993ab0ed](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0b63993ab0ed)
Changeset description:
added test for bug #3723
## Comment 20865
Date: 2015-05-13 16:49:19 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [3030f18c2fc0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3030f18c2fc0) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3030f18c2fc0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3030f18c2fc0)
Changeset description:
fixed bug #3723 (cleanup hash after renaming expressions)
| Assertion failure in rel_bin.c:2548: rel2bin_groupby: Assertion `0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/3723/comments | 0 | 2020-11-30T13:01:53Z | 2024-06-27T12:07:18Z | https://github.com/MonetDB/MonetDB/issues/3723 | 753,460,099 | 3,723 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-08 16:25:58 +0200
From: @swingbit
To: Merovingian devs <<bugs-merovingian>>
Version: -- development
Last updated: 2016-04-11 11:44:07 +0200
## Comment 20859
Date: 2015-05-08 16:25:58 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Build Identifier:
I'm sure I'm not the first who asks for this and I'm sure there have been good technical reasons not to implement a monedbd service for Windows so far.
However I'd like to say that the absence of it is not a minor issue and that perhaps it is time to try and tackle such technical issues.
If you decided not to support Windows at all, you'd have my personal sympathy. Regrettably however, Windows still represents the most popular choice especially in SMEs, also in the server segment.
Since you do put effort in supporting Windows, I must point out that the absence of monetdbd makes MonetDB far less usable in practice for non-trivial deployments. This is what we are observing with our clients. They won't switch to Linux, but we struggle deploying solutions with MonetDB as backend.
Reproducible: Always
| monetdbd for Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/3722/comments | 0 | 2020-11-30T13:01:51Z | 2024-06-28T07:19:45Z | https://github.com/MonetDB/MonetDB/issues/3722 | 753,460,070 | 3,722 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-08 14:31:50 +0200
From: @sjoerdmullender
To: buildtools devs <<bugs-buildtools>>
Version: 11.19.11 (Oct2014-SP3)
Last updated: 2015-07-29 14:55:16 +0200
## Comment 20857
Date: 2015-05-08 14:31:50 +0200
From: @sjoerdmullender
There are some dependency problems in the MonetDB -dev packages which makes that they conflict with each other.
## Comment 20858
Date: 2015-05-08 14:38:52 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [72cc1e3b2ebc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=72cc1e3b2ebc) 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=72cc1e3b2ebc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=72cc1e3b2ebc)
Changeset description:
Fixed dependency problems.
Bug #3721.
| dependency problems in -dev packages | https://api.github.com/repos/MonetDB/MonetDB/issues/3721/comments | 0 | 2020-11-30T13:01:48Z | 2024-06-27T12:07:17Z | https://github.com/MonetDB/MonetDB/issues/3721 | 753,460,032 | 3,721 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-08 08:19:49 +0200
From: Vijay Krishna <<vijayakrishna55>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-06-22 22:32:13 +0200
## Comment 20853
Date: 2015-05-08 08:19:49 +0200
From: Vijay Krishna <<vijayakrishna55>>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36
Build Identifier:
I am using MonetDB Jan2014 SP1, running on MacOS. I have a table like this.
sql>select * from two;
+------+----------------------------------------------------------------------------------------------
| id | name | istrue | joindate | jointime | count |
+======+====================================================
| 1 | null | false | 2017-12-08 | 2014-06-30 14:05:31.000000 | 2 |
| 2 | vijay | false | 2017-12-08 | 2014-06-30 14:05:59.000000 | 3 |
| 3 | krish | true | 2017-12-08 | 2014-06-30 14:06:17.000000 | 5 |
| 4 | bat | true | null | null | null |
| 5 | gotham | false | null | null | null |
| 6 | wayne | false | null | null | 3 |
+------+-------------------------------------------------------------------------------------------------
6 tuples (3.504ms)
I tried to do a join on this table with the same table with the following query and got this result.
sql>select two.id, two.name, two.count, twoAlias.id as id2, twoAlias.name as name2 from two left join two twoAlias on two.count=twoAlias.id;
+------+--------------------------------------------------------------------------------------------------+
| id | name | count | id2 | name2
+=============================================================+
| 1 | null | 2 | 2 | vijay |
| 2 | vijay | 3 | 3 | krish |
| 3 | krish | 5 | 5 | gotham |
| 4 | bat | null | 3 | krish |
| 5 | gotham | null | null | null |
| 6 | wayne | 3 | null | null |
+------+----------------------------------------------------------------------------------------------------+
6 tuples (5.605ms)
As it could be seen clearly, this join is clearly resulting in a wrong output at the 4th row. The join criterion two.count=twoAlias.id is satisfied in the first 3 rows, but are clearly violated in the 4th row, where in the values in the join columns (count and id2 here) are clearly found to be different. Hence the join rows are not matching.
Reproducible: Always
### Steps to Reproduce:
1.Create a table as above.
2.Do a select query by joining with the same table.
Eg - select two.id, two.name, two.count, twoAlias.id as id2, twoAlias.name as name2 from two left join two twoAlias on two.count=twoAlias.id;
3.Results will not be correct.
### Actual Results:
sql>select two.id, two.name, two.count, twoAlias.id as id2, twoAlias.name as name2 from two left join two twoAlias on two.count=twoAlias.id;
+------+--------------------------------------------------------------------------------------------------+
| id | name | count | id2 | name2
+=============================================================+
| 1 | null | 2 | 2 | vijay |
| 2 | vijay | 3 | 3 | krish |
| 3 | krish | 5 | 5 | gotham |
| 4 | bat | null | 3 | krish |
| 5 | gotham | null | null | null |
| 6 | wayne | 3 | null | null |
+------+----------------------------------------------------------------------------------------------------+
### Expected Results:
I expected that the output would be
+------+--------------------------------------------------------------------------------------------------+
| id | name | count | id2 | name2
+=============================================================+
| 1 | null | 2 | 2 | vijay |
| 2 | vijay | 3 | 3 | krish |
| 3 | krish | 5 | 5 | gotham |
| 4 | bat | null | null | null |
| 5 | gotham | null | null | null |
| 6 | wayne | 3 | 3 | krish |
+------+----------------------------------------------------------------------------------------------------+
6 tuples (5.605ms)
## Comment 20866
Date: 2015-05-15 12:05:03 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [443209cc4b86](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=443209cc4b86) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=443209cc4b86](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=443209cc4b86)
Changeset description:
added test for bug #3720
## Comment 20871
Date: 2015-05-20 18:31:05 +0200
From: @njnes
Test added and runs correct
| Incorrect results on joining with same table | https://api.github.com/repos/MonetDB/MonetDB/issues/3720/comments | 0 | 2020-11-30T13:01:46Z | 2024-06-27T12:07:16Z | https://github.com/MonetDB/MonetDB/issues/3720 | 753,460,011 | 3,720 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-07 18:36:41 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
Last updated: 2015-06-22 22:32:23 +0200
## Comment 20851
Date: 2015-05-07 18:36:41 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
SQL query
SELECT count(*) FROM t1 AS x WHERE x.c;
causes assertion failure
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB 5 server v11.19.11 "Oct2014-SP3")
2. start mclient
3. run SQL:
CREATE TABLE t1(a INTEGER, b INTEGER, c INTEGER, d INTEGER, e INTEGER);
INSERT INTO t1(e,c,b,d,a) VALUES(103,102,100,101,104);
INSERT INTO t1(a,c,d,e,b) VALUES(107,106,108,109,105);
INSERT INTO t1(e,d,b,a,c) VALUES(110,114,112,111,113);
INSERT INTO t1(d,c,e,a,b) VALUES(116,119,117,115,118);
SELECT count(*) FROM t1 AS x;
SELECT count(*) FROM t1 AS x WHERE x.c;
-- this last query causes the assertion failure
### Actual Results:
bash-4.2$ ./start_mserver5.sh
builtin opt gdk_dbpath = /export/scratch1/dinther/Downloads/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt gdk_debug = 10
MonetDB 5 server v11.19.11 "Oct2014-SP3"
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
> SQL catalog created, loading sql scripts once
loading sql script: 09_like.sql
loading sql script: 10_math.sql
loading sql script: 11_times.sql
loading sql script: 12_url.sql
loading sql script: 13_date.sql
loading sql script: 14_inet.sql
loading sql script: 15_querylog.sql
loading sql script: 16_tracelog.sql
loading sql script: 19_cluster.sql
loading sql script: 20_vacuum.sql
loading sql script: 21_dependency_functions.sql
loading sql script: 22_clients.sql
loading sql script: 23_skyserver.sql
loading sql script: 24_zorder.sql
loading sql script: 25_debug.sql
loading sql script: 26_sysmon.sql
loading sql script: 39_analytics.sql
loading sql script: 40_geom.sql
loading sql script: 40_json.sql
loading sql script: 41_jsonstore.sql
loading sql script: 45_uuid.sql
loading sql script: 46_gsl.sql
loading sql script: 75_storagemodel.sql
loading sql script: 80_statistics.sql
loading sql script: 80_udf.sql
loading sql script: 85_bam.sql
loading sql script: 90_generator.sql
loading sql script: 99_system.sql
mserver5: ../../MonetDB-11.19.11/gdk/gdk_bat.c:2841: BATassertHeadProps: Assertion `!b->H->key || cmp != 0' failed.
bash-4.2$ mclient
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.19.11 (Oct2014-SP3), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE TABLE t1(a INTEGER, b INTEGER, c INTEGER, d INTEGER, e INTEGER);
operation successful (1.617ms)
sql>INSERT INTO t1(e,c,b,d,a) VALUES(103,102,100,101,104);
1 affected row (2.626ms)
sql>INSERT INTO t1(a,c,d,e,b) VALUES(107,106,108,109,105);
1 affected row (6.187ms)
sql>INSERT INTO t1(e,d,b,a,c) VALUES(110,114,112,111,113);
1 affected row (1.226ms)
sql>INSERT INTO t1(d,c,e,a,b) VALUES(116,119,117,115,118);
1 affected row (1.280ms)
sql>SELECT count(*) FROM t1 AS x;
+------+
| L1 |
+======+
| 4 |
+------+
1 tuple (1.231ms)
sql>SELECT count(*) FROM t1 AS x WHERE x.c;
sql>
bash-4.2$
### Expected Results:
no assertion failure.
Also reproducable on default branch version
## Comment 20852
Date: 2015-05-07 21:06:54 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [68f26b54b3d4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=68f26b54b3d4) 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=68f26b54b3d4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=68f26b54b3d4)
Changeset description:
When converting to Boolean, sortedness and keyness get lost.
This fixes bug #3719.
Also added test.
| Assertion failure in /MonetDB-11.19.11/gdk/gdk_bat.c:2841: BATassertHeadProps: Assertion `!b->H->key || cmp != 0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/3719/comments | 0 | 2020-11-30T13:01:43Z | 2024-06-27T12:07:15Z | https://github.com/MonetDB/MonetDB/issues/3719 | 753,459,977 | 3,719 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-05-07 18:14:16 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.19.11 (Oct2014-SP3)
CC: @njnes
Last updated: 2015-06-22 22:32:26 +0200
## Comment 20850
Date: 2015-05-07 18:14:16 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
Using SQL:
CREATE merge TABLE mt (i int);
ALTER TABLE mt ADD TABLE blablah;
ALTER TABLE mt DROP TABLE blablah;
is a accepted without an error when the table blablah does not exist.
I expect an error to be returned.
Also when using a fully qualified table name (with schema name prefix) the
ALTER TABLE mt DROP TABLE myschema.mytable
is NOT supported (returns an error).
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB 5 server v11.19.11 "Oct2014-SP3")
2. start mclient
3. execute SQL:
CREATE merge TABLE mt (i int);
ALTER TABLE mt ADD TABLE blablah;
ALTER TABLE mt ADD TABLE blablah;
-- both are accepted without an error
ALTER TABLE mt DROP TABLE blablah;
ALTER TABLE mt DROP TABLE blablah;
-- both are accepted without an error
ALTER TABLE mt ADD TABLE bam.t2;
ALTER TABLE mt ADD TABLE bam.t2;
-- both are accepted without an error
ALTER TABLE mt DROP TABLE bam.t2;
-- this returns: Error: syntax error, unexpected '.', expecting SCOLON in: "alter table mt drop table bam."
DROP TABLE mt;
### Actual Results:
bash-4.2$ ./start_mserver5.sh
builtin opt gdk_dbpath = /export/scratch1/dinther/Downloads/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt gdk_debug = 10
MonetDB 5 server v11.19.11 "Oct2014-SP3"
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
>
bash-4.2$ mclient
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.19.11 (Oct2014-SP3), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>CREATE merge TABLE mt (i int);
operation successful (1.446ms)
sql>ALTER TABLE mt ADD TABLE blablah;
operation successful (0.449ms)
sql>ALTER TABLE mt ADD TABLE blablah;
operation successful (0.260ms)
sql>-- both are accepted without an error
sql>ALTER TABLE mt DROP TABLE blablah;
operation successful (0.206ms)
sql>ALTER TABLE mt DROP TABLE blablah;
operation successful (0.207ms)
sql>-- both are accepted without an error
sql>
sql>ALTER TABLE mt ADD TABLE bam.t2;
operation successful (0.225ms)
sql>ALTER TABLE mt ADD TABLE bam.t2;
operation successful (0.213ms)
sql>-- both are accepted without an error
sql>ALTER TABLE mt DROP TABLE bam.t2;
syntax error, unexpected '.', expecting SCOLON in: "alter table mt drop table bam."
sql>-- this returns: Error: syntax error, unexpected '.', expecting SCOLON in: "alter table mt drop table bam."
sql>DROP TABLE mt;
operation successful (0.594ms)
sql>
### Expected Results:
An error msg for all
ALTER TABLE <merge table> ADD TABLE <data table>
and
ALTER TABLE <merge table> DROP TABLE <data table>
statements where the <data table> does not exist in current or specified schema.
Also it should support (and test on existance) fully qualified table names (so with schema name prefix) for both the merge table and the data table names.
## Comment 20867
Date: 2015-05-15 12:45:17 +0200
From: @njnes
added extra check for non existing tables.
## Comment 20869
Date: 2015-05-15 12:50:13 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [7fe602576cf5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7fe602576cf5) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7fe602576cf5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7fe602576cf5)
Changeset description:
added tests for bug #3715, 3718 and also output for 3720
fixed bug #3718 (ie check for unknown tables)
| Adding and dropping a non existing tablename to/from a merge table is accepted without an error | https://api.github.com/repos/MonetDB/MonetDB/issues/3718/comments | 0 | 2020-11-30T13:01:41Z | 2024-06-27T12:07:14Z | https://github.com/MonetDB/MonetDB/issues/3718 | 753,459,945 | 3,718 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-24 13:33:35 +0200
From: karthik <<karthik_sitaram>>
To: clients devs <<bugs-clients>>
Version: 11.21.19 (Jul2015-SP4)
Last updated: 2016-04-11 11:18:37 +0200
## Comment 20843
Date: 2015-04-24 13:33:35 +0200
From: karthik <<karthik_sitaram>>
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E; MS-RTC LM 8)
Build Identifier:
We have problems connecting to a MonetDB Cluster via Apache Spark using JDBC. Connection to a database that is not clustered works. But when we try to connect to a clustered MonetDB database via Apache Spark, it fails with a "unhandled result type error". The entire query is given below
PREPARE SELECT * FROM (select count(*) from customer)v1 WHERE 1=0
http://stackoverflow.com/questions/29747500/apache-spark-fails-to-connect-to-monetdb-cluster-using-jdbc-driver
Reproducible: Always
### Steps to Reproduce:
1.Setup a funnel or a monetdb cluster
2.issue statement via jdbc PREPARE SELECT * FROM (select count(*) from customer)v1 WHERE 1=0
3.Software gives unhandled result type error
### Actual Results:
Software gives unhandled result type error
val v1 = hiveContext.load("jdbc",Map("url" -> "jdbc:monetdb://1.1.1.1/tpch1?user=monetdb&password=monetdb","dbtable" -> "(select count(*) from customer)v1"))
**java.sql.SQLException: node */tpch/1/monet returned unhandled result type**
java.sql.SQLException: node */tpch/2/monet returned unhandled result type
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2536)
at nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:2284)
at nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:508)
at nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:349)
at nl.cwi.monetdb.jdbc.MonetPreparedStatement.<init>(MonetPreparedStatement.java:118)
at nl.cwi.monetdb.jdbc.MonetConnection.prepareStatement(MonetConnection.java:901)
at nl.cwi.monetdb.jdbc.MonetConnection.prepareStatement(MonetConnection.java:825)
at org.apache.spark.sql.jdbc.JDBCRDD$.resolveTable(JDBCRDD.scala:96)
at org.apache.spark.sql.jdbc.JDBCRelation.<init>(JDBCRelation.scala:125)
at org.apache.spark.sql.jdbc.DefaultSource.createRelation(JDBCRelation.scala:114)
at org.apache.spark.sql.sources.ResolvedDataSource$.apply(ddl.scala:290)
at org.apache.spark.sql.SQLContext.load(SQLContext.scala:679)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:23)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:28)
at $iwC$$iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:30)
at $iwC$$iwC$$iwC$$iwC$$iwC.<init>(<console>:32)
at $iwC$$iwC$$iwC$$iwC.<init>(<console>:34)
at $iwC$$iwC$$iwC.<init>(<console>:36)
at $iwC$$iwC.<init>(<console>:38)
at $iwC.<init>(<console>:40)
at <init>(<console>:42)
at .<init>(<console>:46)
at .<clinit>(<console>)
at .<init>(<console>:7)
at .<clinit>(<console>)
at $print(<console>)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.spark.repl.SparkIMain$ReadEvalPrint.call(SparkIMain.scala:1065)
at org.apache.spark.repl.SparkIMain$Request.loadAndRun(SparkIMain.scala:1338)
at org.apache.spark.repl.SparkIMain.loadAndRunReq$1(SparkIMain.scala:840)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:871)
at org.apache.spark.repl.SparkIMain.interpret(SparkIMain.scala:819)
at org.apache.spark.repl.SparkILoop.reallyInterpret$1(SparkILoop.scala:856)
at org.apache.spark.repl.SparkILoop.interpretStartingWith(SparkILoop.scala:901)
at org.apache.spark.repl.SparkILoop.command(SparkILoop.scala:813)
at org.apache.spark.repl.SparkILoop.processLine$1(SparkILoop.scala:656)
at org.apache.spark.repl.SparkILoop.innerLoop$1(SparkILoop.scala:664)
at org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$loop(SparkILoop.scala:669)
at org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply$mcZ$sp(SparkILoop.scala:996)
at org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:944)
at org.apache.spark.repl.SparkILoop$$anonfun$org$apache$spark$repl$SparkILoop$$process$1.apply(SparkILoop.scala:944)
at scala.tools.nsc.util.ScalaClassLoader$.savingContextLoader(ScalaClassLoader.scala:135)
at org.apache.spark.repl.SparkILoop.org$apache$spark$repl$SparkILoop$$process(SparkILoop.scala:944)
at org.apache.spark.repl.SparkILoop.process(SparkILoop.scala:1058)
at org.apache.spark.repl.Main$.main(Main.scala:31)
at org.apache.spark.repl.Main.main(Main.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:569)
at org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:166)
at org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:189)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:110)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
JDBC Log
RD 1429856293844: read final block: 67 bytes RX 1429856293845:
bwnthqobupI3CPY:merovingian:9:RIPEMD160,SHA256,SHA1,MD5:LIT:SHA512: RD 1429856293845: inserting prompt TD 1429856293846: write final block: 99 bytes TX 1429856293846: BIG:merovingian:{SHA256}7070477fd396595c929386453a32ac5059a9b76976e54dab3fbb7a8f5299bd25:sql:tpch1: RD 1429856293847: read final block: 0 bytes RX 1429856293847: RD 1429856293847: inserting prompt TD 1429856293847: write final block: 49 bytes TX 1429856293847: sSET TIME ZONE INTERVAL '+05:30' HOUR TO MINUTE ; RD 1429856293848: read final block: 3 bytes RX 1429856293848: &3
RD 1429856293848: inserting prompt TD 1429856293855: write final block: 15 bytes TX 1429856293855: Xreply_size 250 RD 1429856293855: read final block: 0 bytes RX 1429856293855: RD 1429856293855: inserting prompt TD 1429856293855: write final block: 68 bytes TX 1429856293855: sPREPARE SELECT * FROM (select count(*) from customer)v1 WHERE 1=0 ; RD 1429856293856: read final block: 52 bytes RX 1429856293856: !node */tpch/2/monet returned unhandled result type
RD 1429856293856: inserting prompt
| merovingian funnel fails with error unhandled result type error | https://api.github.com/repos/MonetDB/MonetDB/issues/7445/comments | 1 | 2020-11-30T13:01:38Z | 2024-06-07T12:43:00Z | https://github.com/MonetDB/MonetDB/issues/7445 | 2,094,262,808 | 7,445 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-23 16:01:57 +0200
From: Martin van Dinther <<martin.van.dinther>>
To: SQL devs <<bugs-sql>>
Version: 11.19.9 (Oct2014-SP2)
CC: @njnes
Last updated: 2015-08-28 13:43:03 +0200
## Comment 20836
Date: 2015-04-23 16:01:57 +0200
From: Martin van Dinther <<martin.van.dinther>>
User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build Identifier:
SQL "alter table m drop table t1;"
where table t1 does no longer exist (as it is dropped before) causes a segmentation fault. Instead it should return an error.
Also it appears that running "alter table m drop table t1;" twice is also accepted without a warning or error. I would like to receive an error instead.
Reproducible: Always
### Steps to Reproduce:
1. start mserver5 (MonetDB 5 server v11.19.9 "Oct2014-SP2")
2. start mclient
3. execute SQL commands:
create table t1 (i int);
create table t2 (i int);
create merge table m (i int);
alter table m add table t1;
alter table m add table t2;
alter table m drop table t1;
alter table m drop table t1;
DROP table t1;
alter table m drop table t1;
-- this last alter table m statement causes the segmentation fault
-- if it doesn't try also:
select * from m;
### Actual Results:
builtin opt gdk_dbpath = /export/scratch1/dinther/Downloads/INSTALL/var/monetdb5/dbfarm/demo
builtin opt gdk_debug = 0
builtin opt gdk_vmtrim = no
builtin opt monet_prompt = >
builtin opt monet_daemon = no
builtin opt mapi_port = 50000
builtin opt mapi_open = false
builtin opt mapi_autosense = false
builtin opt sql_optimizer = default_pipe
builtin opt sql_debug = 0
cmdline opt gdk_debug = 10
MonetDB 5 server v11.19.9 "Oct2014-SP2"
Serving database 'demo', using 8 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 15.590 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2015 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/GIS module loaded
MonetDB/SQL module loaded
> SQL catalog created, loading sql scripts once
loading sql script: 09_like.sql
loading sql script: 10_math.sql
loading sql script: 11_times.sql
loading sql script: 12_url.sql
loading sql script: 13_date.sql
loading sql script: 14_inet.sql
loading sql script: 15_querylog.sql
loading sql script: 16_tracelog.sql
loading sql script: 19_cluster.sql
loading sql script: 20_vacuum.sql
loading sql script: 21_dependency_functions.sql
loading sql script: 22_clients.sql
loading sql script: 23_skyserver.sql
loading sql script: 24_zorder.sql
loading sql script: 25_debug.sql
loading sql script: 26_sysmon.sql
loading sql script: 39_analytics.sql
loading sql script: 40_geom.sql
loading sql script: 40_json.sql
loading sql script: 41_jsonstore.sql
loading sql script: 45_uuid.sql
loading sql script: 46_gsl.sql
loading sql script: 75_storagemodel.sql
loading sql script: 80_statistics.sql
loading sql script: 80_udf.sql
loading sql script: 85_bam.sql
loading sql script: 90_generator.sql
loading sql script: 99_system.sql
./start_mserver5.sh: line 5: 11423 Segmentation fault
bash-4.2$ mclient
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.19.9 (Oct2014-SP2), 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>create table t1 (i int);
operation successful (1.612ms)
sql>create table t2 (i int);
operation successful (1.145ms)
sql>create merge table m (i int);
operation successful (0.716ms)
sql>alter table m add table t1;
operation successful (0.526ms)
sql>alter table m add table t2;
operation successful (0.471ms)
sql>alter table m drop table t1;
operation successful (0.180ms)
sql>alter table m drop table t1;
operation successful (0.672ms)
sql>alter table m drop table t1;
operation successful (0.620ms)
sql>DROP table t1;
operation successful (6.437ms)
sql>DROP table t1;
DROP TABLE: no such table 't1'
sql>alter table m drop table t1;
operation successful (0.612ms)
sql>alter table m drop table t1;
sql>
bash-4.2$
### Expected Results:
after the SQLs:
alter table m add table t2;
alter table m drop table t1;
alter table m drop table t1;
I expect to get an error msg stating that table t1 cannot be dropped from merge table m as it is not part of the merge table definition.
after the SQLs:
DROP table t1;
alter table m drop table t1;
I expect to get an error msg stating that table t1 does not exist.
See also bug #3703
## Comment 20842
Date: 2015-04-24 13:16:29 +0200
From: @njnes
fixed in default, also added a test to the mergetable set
## Comment 21229
Date: 2015-08-28 13:43:03 +0200
From: @sjoerdmullender
Jul2015 has been released.
| alter table my_merge_table drop table t1; crashes mserver5 with Segmentation fault | https://api.github.com/repos/MonetDB/MonetDB/issues/3716/comments | 0 | 2020-11-30T13:01:35Z | 2024-06-27T12:07:12Z | https://github.com/MonetDB/MonetDB/issues/3716 | 753,459,868 | 3,716 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-23 14:37:49 +0200
From: Pete Hollobon <<pete>>
To: SQL devs <<bugs-sql>>
Version: 11.19.9 (Oct2014-SP2)
CC: @njnes, pete
Last updated: 2015-06-22 22:32:20 +0200
## Comment 20835
Date: 2015-04-23 14:37:49 +0200
From: Pete Hollobon <<pete>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36
Build Identifier:
Adding a new column and setting its NOT NULL constraint within a transaction crashes the server:
CREATE TABLE bugexample (
id INTEGER
);
START TRANSACTION;
ALTER TABLE bugexample ADD COLUMN newcolumn integer;
ALTER TABLE bugexample ALTER COLUMN newcolumn SET NOT NULL;
COMMIT;
Removing the transaction around the =ALTER TABLE= commands results it in completing correctly.
Reproducible: Always
### Steps to Reproduce:
1. Run the SQL above
### Actual Results:
Server crashes (SIGSEGV)
### Expected Results:
Column added not null after transaction commit.
## Comment 20840
Date: 2015-04-24 11:09:47 +0200
From: @njnes
test added and fixed bug by checking for existence of update bat.
## Comment 20868
Date: 2015-05-15 12:50:10 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [7fe602576cf5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7fe602576cf5) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7fe602576cf5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7fe602576cf5)
Changeset description:
added tests for bug #3715, 3718 and also output for 3720
fixed bug #3718 (ie check for unknown tables)
| Crash with two ALTER TABLE statements in a transaction | https://api.github.com/repos/MonetDB/MonetDB/issues/3715/comments | 0 | 2020-11-30T13:01:33Z | 2024-06-27T12:07:11Z | https://github.com/MonetDB/MonetDB/issues/3715 | 753,459,849 | 3,715 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-23 09:31:56 +0200
From: Clint Cummins <<ccummins>>
To: buildtools devs <<bugs-buildtools>>
Version: 11.21.19 (Jul2015-SP4)
Last updated: 2016-06-03 09:18:13 +0200
## Comment 20834
Date: 2015-04-23 09:31:56 +0200
From: Clint Cummins <<ccummins>>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.89 Safari/537.36
Build Identifier:
I have been using MonetDB on Windows 7 x64 for awhile now,
and the precompiled version has been working very well
(we have tested it on some of our large data with over 4 billion rows).
I recently built MonetDB-11.19.9 (Oct2014-SP2) on windows x64,
but mserver5.exe crashes when I try any simple test.
The last message from mserver5.exe with the default sql_debug=0 is:
loading sql script: 09_like.sql
The last message from mserver5.exe with --set "sql_debug=32767" is:
mvc_create_func like
(This is the first SQL command in the first sql script file.)
By inserting fprintf commands, I traced the crash to the statement:
free(c.fdin->buf);
The calling stack is:
compileOptimizer() - monetdb5\optimizer\opt_pipes.c - line 486
addOptimizerPipe() - monetdb5\optimizer\opt_pipes.c - line 517
addOptimizers() - sql\backends\monet5\sql_optimizer.c - line 225
addQueryToCache() - sql\backends\monet5\sql_optimizer.c - line 278
SQLstatementIntern() - sql\backends\monet5\sql_scenario.c - line 1824
SQLinitClient() - sql\backends\monet5\sql_scenario.c - line 1531
I am hoping you might have some ideas on what may have gone wrong in my build.
I followed the very helpful instructions in
buildtools\doc\windowsbuild.rst (I also converted it to html)
It was slightly incomplete or outdated in places, but I worked past those problems,
and the instructions were mostly very helpful.
(One of the out of date parts said that Java 5 was needed, but Java5 does not work
with the very latest 1/2015 JDBC code, so I used Java 7 instead).
I used the Intel C++ compiler version 15.0.2.179 Build 20150121
[Intel Parallel Studio XE 2015 Update 2 Composer Edition (package 179)]
with Microsoft Visual Studio 10.0 [2010 x64],
and Microsoft VC version 16.0.30319.1 2/19/2010 , but I think only the Intel is used?
Thanks,
Clint
Reproducible: Always
### Steps to Reproduce:
1. start mserver5.exe
2. start mclient.exe
### Actual Results:
mserver5 crashes when processing the first SQL statement in the first auto SQL script file ( 09_like.sql ).
No error message; it just stops, and mclient is then disconnected.
### Expected Results:
mserver5 should process all the auto SQL script files, then give me a prompt
so I can issue my own sql commands.
Below are my environmental variables, build commands, and modified part of NT\rules.msc:
==== environmental variables (setb.bat) ====
rem Intel Compiler options for MonetDB build
set CC=icl -Qstd=c99 -GR- -Qsafeseh-
set CCX=icl -Qstd=c99 -GR- -Qsafeseh-
rem MonetDB build variables
set SOURCE=C:\Software\clint-sw\MonetDB-11.19.9
set BUILD=%SOURCE%\build
set PREFIX=%SOURCE%\install
rem add to Path
rem vi/vim
set Path=%ProgramFiles%\vim72;%Path%
rem Python already in path
rem Bison, Diff, Patch - Bison needs path without spaces
set Path=C:\GnuWin32\bin;%Path%
rem Java
set JAVA_HOME=C:\Program Files\Java\jdk1.7.0_25
set Path=%JAVA_HOME%\bin;C:\Program Files\Java\jre7;%Path%
rem Apache Ant (used with Java)
set Path=%ProgramFiles%\apache-ant-1.9.4\bin;%Path%
rem PHP binary - used for testing
set Path=C:\Program Files\PHP;%Path%
rem Libraries with component DLLs used by MonetDB build
rem PCRE
set Path=C:\Program Files\PCRE\bin;%Path%
rem OpenSSL
set Path=C:\Libraries\openssl-1.0.1l.win64\bin;%Path%
rem libxml2
set Path=C:\Libraries\libxml2-2.9.2.win64\bin;%Path%
rem geos
set Path=C:\Libraries\geos-3.4.2.win64\bin;%Path%
rem iconv
set Path=C:\Libraries\iconv-1.11.1.win64\bin;%Path%
rem zlib
set Path=C:\Libraries\zlib-1.2.8.win64\bin;%Path%
rem bzip2
set Path=C:\Libraries\bzip2-1.0.6.win64\bin;%Path%
rem R - for embedded R
set Path=C:\Program Files\R\R-3.1.3\bin\x64;%Path%
rem For testing MonetDB
set Path=%PREFIX%\lib\MonetDB5;%Path%
set Path=%PREFIX%\bin;%PREFIX%\lib;%Path%
rem Python module search path
set PYTHONPATH=%PREFIX%\lib\site-packages;%PYTHONPATH%
rem Build params
set Build_params=NDEBUG=1 HAVE_GDK=1 HAVE_MONETDB5=1 HAVE_SQL=1 HAVE_GEOM=1 HAVE_JAVA=1 HAVE_JAVAJDBC=1
set Build_params=%Build_params% HAVE_TESTING=1 HAVE_PYTHON=1 HAVE_ICONV=1 HAVE_PCRE=1
set Build_params=%Build_params% HAVE_OPENSSL=1 HAVE_PERL=1 HAVE_LIBZ=1 HAVE_LIBBZ2=1
set Build_params=%Build_params% HAVE_ATOMIC_OPS=1 HAVE_LIBR=1
===================
==== build command (nmake1.bat) ====
nmake /nologo /f ..\NT\Makefile "prefix=%PREFIX%" %Build_params%
===================
==== install command (nmake2.bat) ====
nmake /nologo /f ..\NT\Makefile "prefix=%PREFIX%" %Build_params% install
===================
==== modified portion of NT\rules.msc ====
!IFNDEF bits
!IF defined(BITS32)
bits=32
!ELSEIF defined(BITS64)
bits=64
!ELSE
default:
modified by Clint - 64 bit default
bits=64
!ENDIF
!ENDIF
!IF $(bits) == 32
!IFNDEF BITS32
BITS32=True
BITSMCHN=X86
!ENDIF
!ELSEIF $(bits) == 64
!IFNDEF BITS64
BITS64=True
BITSMCHN=X64
!ENDIF
!ENDIF
!IFDEF DEBUG
DEBUGLIB=d
!ELSE
DEBUGLIB=
!ENDIF
!IFDEF DEBUG
force W_CFLAGS off in debug builds: using icc, you get way more
warnings about casts which results in the code being uncompilable
W_CFLAGS =
!ENDIF
!IFDEF ENABLE_STRICT
strict mode: treat warnings as errors
W_CFLAGS = -WX
!ENDIF
This is the location of pthreads for Win32,
see http://sources.redhat.com/pthreads-win32/
Note that pthreads are no longer used to compile MonetDB (although
it might still work).
PTHREAD =
!IFNDEF PTHREAD_INCS
PTHREAD_INCS =
!ENDIF
!IFNDEF PTHREAD_LIBS
PTHREAD_LIBS =
!ENDIF
ODBCINST_LIBS = odbccp32.lib user32.lib
ODBC_LIBS = odbc32.lib
!IFNDEF PYTHON2BASE
modified by Clint
PYTHON2BASE=C:\Program Files\Python27
!ENDIF
!IFNDEF PYTHON2LIB
PYTHON2LIB=python27.lib
!ENDIF
PYTHON2_LIBDIR=share\MonetDB\python
!IFNDEF PYTHON3BASE
PYTHON3BASE=C:\Python32
!ENDIF
!IFNDEF PYTHON3LIB
PYTHON3LIB=python32.lib
!ENDIF
PYTHON3_LIBDIR=share\MonetDB\python3
!IFDEF HAVE_PERL
!IFNDEF LIBPERL
!IF $(bits) == 32
LIBPERL = C:\Perl
!ELSE
LIBPERL = C:\Perl64
!ENDIF
!ENDIF
!IFNDEF PERLLIB
Clint notes - file on next line does not exist. There is a libperl520.a
PERLLIB = perl510.lib
!ENDIF
PERL_INCS = -I$(LIBPERL)\lib\CORE -DWIN32
PERL_LIBS = $(LIBPERL)\lib\CORE\$(PERLLIB)
PERL_LIBDIR = share\MonetDB\perl
!ENDIF
!IFDEF HAVE_PCRE
This is the location of the PCRE library
!IFNDEF LIBPCRE
LIBPCRE = C:\Program Files\PCRE
!ENDIF
pcre_LIBS = "$(LIBPCRE)\lib\pcre$(DEBUGLIB).lib"
pcre_CFLAGS = -DHAVE_LIBPCRE "-I$(LIBPCRE)\include"
!ENDIF
!IFDEF HAVE_OPENSSL
This is the location of the OpenSSL library
!IFNDEF LIBOPENSSL
Clint changed:
LIBOPENSSL = C:\openssl-0.9.8k.win$(bits)
LIBOPENSSL = C:\Libraries\openssl-1.0.1l.win$(bits)
!ENDIF
openssl_LIBS = "$(LIBOPENSSL)\lib\ssleay32.lib" "$(LIBOPENSSL)\lib\libeay32.lib"
openssl_CFLAGS = -DHAVE_OPENSSL "-I$(LIBOPENSSL)\include"
!ENDIF
!IFDEF HAVE_ICONV
This is the location of the ICONV library
!IFNDEF LIBICONV
Clint changed:
LIBICONV = C:\iconv-1.9.2.win$(bits)
LIBICONV = C:\Libraries\iconv-1.11.1.win$(bits)
!ENDIF
LTLIBICONV = "$(LIBICONV)\lib\iconv$(DEBUGLIB).lib"
ICONV_CFLAGS = -DHAVE_ICONV "-I$(LIBICONV)\include"
!ENDIF
!IFDEF HAVE_ATOMIC_OPS
!IFNDEF LIBATOMIC_OPS
Clint changed:
LIBATOMIC_OPS = C:\atomic_ops-7.2
LIBATOMIC_OPS = C:\Libraries\libatomic_ops-7.4.2\src
!ENDIF
ATOMIC_OPS_CFLAGS = -DHAVE_LIBATOMIC_OPS "-I$(LIBATOMIC_OPS)"
!endif
!IFDEF HAVE_LIBZ
This is the location of the ZLIB library
!IFNDEF LIBZLIB
Clint changed:
LIBZLIB = C:\zlib-1.2.3.win$(bits)
LIBZLIB = C:\Libraries\zlib-1.2.8.win$(bits)
!ENDIF
!IFNDEF LIBZLIBFILE
LIBZLIBFILE=zlib1
!ENDIF
zlib_LIBS = "$(LIBZLIB)\lib\$(LIBZLIBFILE)$(DEBUGLIB).lib"
zlib_CFLAGS = -DHAVE_LIBZ "-I$(LIBZLIB)\include"
!ENDIF
!IFDEF HAVE_LIBBZ2
This is the location of the BZIP2 library
!IFNDEF LIBBZIP2
Clint changed:
LIBBZIP2 = C:\bzip2-1.0.5.win$(bits)
LIBBZIP2 = C:\Libraries\bzip2-1.0.6.win$(bits)
!ENDIF
BZ_LIBS = "$(LIBBZIP2)\lib\libbz2$(DEBUGLIB).lib"
BZ_CFLAGS = -DHAVE_LIBBZ2 "-I$(LIBBZIP2)\include"
!ENDIF
This is the location of the libxml2 library
!IFNDEF LIBXML2
Clint changed:
LIBXML2 = C:\libxml2-2.6.30.win$(bits)
LIBXML2 = C:\Libraries\libxml2-2.9.2.win$(bits)
!ENDIF
Clint changed:
libxml2_CFLAGS = "-I$(LIBXML2)\include" $(zlib_CFLAGS) $(ICONV_CFLAGS)
libxml2_CFLAGS = "-I$(LIBXML2)\include\libxml2" $(zlib_CFLAGS) $(ICONV_CFLAGS)
libxml2_LIBS = "$(LIBXML2)\lib\libxml2$(DEBUGLIB).lib" $(zlib_LIBS) $(ICONV_LIBS)
!IFNDEF LIBGEOS
Clint changed:
LIBGEOS = C:\geos-3.0.win$(bits)
LIBGEOS = C:\Libraries\geos-3.4.2.win$(bits)
!ENDIF
!IFDEF DEBUG
GEOS_LIBS = $(LIBGEOS)\lib\geos_c_i$(GEOSDEBUGLIB).lib
!ELSE
GEOS_LIBS = $(LIBGEOS)\lib\geos_c_i.lib
!ENDIF
GEOS_INCS = -I$(LIBGEOS)\include
!IFNDEF RUBY_DIR
RUBY_DIR = lib\ruby\gems\1.9.1
!ENDIF
!IFDEF HAVE_LIBR
This is the location of the R library
libr_LIBDEP = R.lib
!IFNDEF LIBR
modified by Clint
LIBR = c:\Program Files\R\R-3.1.3
!ENDIF
!IFDEF BITS32
RDLL=bin\i386\R.dll
!ELSE
RDLL=bin\x64\R.dll
!ENDIF
===================
## Comment 21066
Date: 2015-07-29 16:39:06 +0200
From: @sjoerdmullender
I can't really say what is wrong with your build, but I can give you a suggestion on how to find out more.
It sounds like you can start the server, but when you connect the first client, it crashes?
If this is the case, start the server, then attach the Visual Studio debugger (start VS, and using the menu Debug -> Attach (or something like that) attach to the process). After attaching, run the client. If the server crashes, you should see that in the debugger, at which time you can look at the stack trace and at the values of variables.
## Comment 21626
Date: 2015-12-02 09:45:59 +0100
From: Clint Cummins <<ccummins>>
In early November, I tried again on this, inserting printf calls to find the crash point. Eventually I saw it was crashing when trying to free() a bstream pointer that had become zero. I inserted a printf into bstream_create() (stream.c), and it stopped crashing and runs fine. So I am tempted to guess that the compiler (Intel C++ 15.0.2.179) is optimizing too aggressively?
## Comment 21876
Date: 2016-03-12 01:36:06 +0100
From: Clint Cummins <<ccummins>>
The problem went away, when I built the newer version MonetDB-11.21.13,
with the same compiler, and same library settings.
Although I used the supplied component libraries (Intel VS_2010).
Now it builds and runs fine.
## Comment 22193
Date: 2016-06-03 09:18:13 +0200
From: @sjoerdmullender
Problem seems to have gone away (and was not reproducible by us).
| mserver5 crashes on any simple test, processing 09_like.sql | https://api.github.com/repos/MonetDB/MonetDB/issues/3714/comments | 0 | 2020-11-30T13:01:30Z | 2024-06-28T13:14:35Z | https://github.com/MonetDB/MonetDB/issues/3714 | 753,459,807 | 3,714 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-22 21:41:14 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.17.13 (Jan2014-SP1)
CC: @njnes
Last updated: 2015-06-22 22:32:19 +0200
## Comment 20831
Date: 2015-04-22 21:41:14 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
Consider the TPCH sf1 script below, where sf1.load contains the relevant COPYs.
Consistently, we need to wait for 9 seconds on a trivial load:
COPY 5 RECORDS INTO region from '/export/scratch2/mk/tpch/SF-1/data/region.tbl' USING DELIMITERS '|', '|\n' LOCKED;
5 affected rows (9.5s)
compared to the rest of the load:
25 affected rows (695.376ms)
10000 affected rows (1.0s)
150000 affected rows (2.1s)
800000 affected rows (5.1s)
1500000 affected rows (5.4s)
6001215 affected rows (23.4s)
The subsequent alter script runs fine, also for the first instruction
operation successful (6.341ms)
If I place a sleep of 15 seconds after tpch_schema.sql,
I get the same results
If I explicitly stop the server and let it be restarted
by the load script, I don't see the delay.
Seems that the tpch_schema.sql transaction does not propagate the catalog updates immediately, giving this unexpected delay. (who triggers the wait?)
Reproducible: Always
### Steps to Reproduce:
monetdb stop sf1
monetdb destroy sf1 -f
monetdb create sf1
monetdb release sf1
time mclient -d sf1 -ei tpch_schema.sql
time mclient -d sf1 -ei sf1.load
time mclient -d sf1 -ei tpch_alter.sql
## Comment 20832
Date: 2015-04-22 22:17:38 +0200
From: @sjoerdmullender
I can reproduce the problem.
However, if I do the load UNLOCKED (i.e. not LOCKED), the problem disappears.
From looking at strace output I get the distinct impression that it has something to do with committing data. When using LOCKED, after the schema initialization I see that the first data file is loaded, but before that query returns, there are a lot of BATs that get written and fdatasync()ed. All in all that takes a long time. Without LOCKED I don't see the long list of BATs getting synchronized to disk.
Here are the timings of my CREATE script immediately followed by loading with LOCKED:
create schema
operation successful (20.326ms)
operation successful (16.295ms)
operation successful (15.564ms)
operation successful (16.778ms)
operation successful (15.954ms)
operation successful (24.331ms)
operation successful (16.029ms)
operation successful (24.783ms)
load data
5 affected rows (13195.189ms)
25 affected rows (1165.221ms)
10000 affected rows (1542.335ms)
150000 affected rows (2803.931ms)
200000 affected rows (2359.778ms)
800000 affected rows (4972.089ms)
1500000 affected rows (5651.299ms)
6001215 affected rows (19125.609ms)
And here without LOCKED:
create schema
operation successful (19.183ms)
operation successful (16.115ms)
operation successful (15.683ms)
operation successful (16.322ms)
operation successful (16.175ms)
operation successful (16.586ms)
operation successful (16.048ms)
operation successful (24.764ms)
load data
5 affected rows (163.523ms)
25 affected rows (191.679ms)
10000 affected rows (421.709ms)
150000 affected rows (1959.259ms)
200000 affected rows (1585.701ms)
800000 affected rows (4225.754ms)
1500000 affected rows (5308.068ms)
6001215 affected rows (16584.857ms)
## Comment 20844
Date: 2015-04-24 13:41:11 +0200
From: @njnes
changes to the logger caused extra delay. BUNfnd(.., neg-cand list) may
help. Also a vacuum of the catalog table is needed.
## Comment 20845
Date: 2015-04-24 15:21:34 +0200
From: @njnes
we use a hash(again) instead of nestedloop (the deleted list is still in efficient)
| Long startup cost for simple session | https://api.github.com/repos/MonetDB/MonetDB/issues/3713/comments | 0 | 2020-11-30T13:01:27Z | 2024-06-27T12:07:09Z | https://github.com/MonetDB/MonetDB/issues/3713 | 753,459,767 | 3,713 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-22 21:19:33 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.17.13 (Jan2014-SP1)
CC: @njnes
Last updated: 2015-06-22 22:32:21 +0200
## Comment 20829
Date: 2015-04-22 21:19:33 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:37.0) Gecko/20100101 Firefox/37.0
Build Identifier:
In one window the 254 files of airtraffic are loaded one by one into a merge table.
In another window progress is monitored using a query. Then it can happen
that the mclient simply quits without output.
....
working session
....
sql>select * from tables where name ilike '%ontime%';
+-------+---------------+-----------+-------+------+--------+---------------+--------+-----------+
| id | name | schema_id | query | type | system | commit_action | access | temporary |
+=======+===============+===========+=======+======+========+===============+========+===========+
| 7365 | ontime | 2000 | null | 3 | false | 0 | 0 | 0 |
| 7460 | ontime1988_1 | 2000 | null | 0 | false | 0 | 1 | 0 |
.....
| 10880 | ontime1991_1 | 2000 | null | 0 | false | 0 | 1 | 0 |
| 10975 | ontime1991_2 | 2000 | null | 0 | false | 0 | 0 | 0 |
+-------+---------------+-----------+-------+------+--------+---------------+--------+-----------+
39 tuples (5.8s)
sql>^C
stopped and restart session
mk@vienna::/export/scratch1/mk/default/package/sql/test/mergetables/Tests> mclient -d airtraffic
Welcome to mclient, the MonetDB/SQL interactive terminal (unreleased)
Database: MonetDB v11.20.0 (unreleased), 'mapi:monetdb://vienna.ins.cwi.nl:50000/airtraffic'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>select * from tables where name ilike '%ontime%';
sql>
mk@vienna::/export/scratch1/mk/default/package/sql/test/mergetables/Tests>
It can even happen that establishing a new connection fails as well.
Reproducible: Sometimes
## Comment 20830
Date: 2015-04-22 21:21:50 +0200
From: @mlkersten
Putting the debugger on the server and attempting a new session gives the following trace.
0 0x000000378a035877 in raise () from /lib64/libc.so.6
1 0x000000378a036f68 in abort () from /lib64/libc.so.6
2 0x000000378a02e7d6 in __assert_fail_base () from /lib64/libc.so.6
3 0x000000378a02e882 in __assert_fail () from /lib64/libc.so.6
4 0x00007f7c5acd191c in schema_table_find (s=0x7f7c301106b0, ot=0x7f7c444916a0) at /export/scratch1/mk/default//package/sql/storage/store.c:2082
5 0x00007f7c5acd19c3 in table_find (tr=0x7f7c300016a0, flag=0, ot=0x7f7c444916a0, omt=0x7f7c30120460) at /export/scratch1/mk/default//package/sql/storage/store.c:2099
6 0x00007f7c5acd5062 in reset_changeset (tr=0x7f7c300016a0, fs=0x7f7c30120548, pfs=0x2b0b328, b=0x7f7c30120460, rf=0x0, fd=0x7f7c5acd1928 <table_find>) at /export/scratch1/mk/default//package/sql/storage/store.c:3056
7 0x00007f7c5acd55d1 in reset_table (tr=0x7f7c300016a0, ft=0x7f7c30120460, pft=0x2b0b240) at /export/scratch1/mk/default//package/sql/storage/store.c:3150
8 0x00007f7c5acd4e51 in reset_changeset (tr=0x7f7c300016a0, fs=0x7f7c301106e0, pfs=0x2aa1be0, b=0x7f7c301106b0, rf=0x7f7c5acd5494 <reset_table>, fd=0x7f7c5acd19de <table_dup>)
at /export/scratch1/mk/default//package/sql/storage/store.c:3028
9 0x00007f7c5acd5a96 in reset_schema (tr=0x7f7c300016a0, fs=0x7f7c301106b0, pfs=0x2aa1bb0) at /export/scratch1/mk/default//package/sql/storage/store.c:3224
10 0x00007f7c5acd4e51 in reset_changeset (tr=0x7f7c300016a0, fs=0x7f7c300016d0, pfs=0x298f910, b=0x298f8e0, rf=0x7f7c5acd57c7 <reset_schema>, fd=0x7f7c5acd24c4 <schema_dup>)
at /export/scratch1/mk/default//package/sql/storage/store.c:3028
11 0x00007f7c5acd5ba0 in reset_trans (tr=0x7f7c300016a0, ptr=0x298f8e0) at /export/scratch1/mk/default//package/sql/storage/store.c:3241
12 0x00007f7c5acddee7 in sql_trans_begin (s=0x7f7c48002f70) at /export/scratch1/mk/default//package/sql/storage/store.c:5142
13 0x00007f7c5ac41343 in mvc_trans (m=0x7f7c4810e980) at /export/scratch1/mk/default//package/sql/server/sql_mvc.c:169
14 0x00007f7c5ab885b1 in monet5_user_get_def_schema (m=0x7f7c4810e980, user=0) at /export/scratch1/mk/default//package/sql/backends/monet5/sql_user.c:424
## Comment 20838
Date: 2015-04-24 09:42:25 +0200
From: @mlkersten
Fixed.
## Comment 20839
Date: 2015-04-24 11:04:05 +0200
From: @njnes
fixed by a split of the reset_table code (ie first al tables then the table parts of a merge table).
| Concurrency issue on querying the SQL catalog | https://api.github.com/repos/MonetDB/MonetDB/issues/3712/comments | 0 | 2020-11-30T13:01:25Z | 2024-06-27T12:07:08Z | https://github.com/MonetDB/MonetDB/issues/3712 | 753,459,729 | 3,712 |
[
"MonetDB",
"MonetDB"
] | Date: 2015-04-22 14:23:26 +0200
From: @skinkie
To: clients devs <<bugs-clients>>
Version: 11.21.19 (Jul2015-SP4)
CC: martin.van.dinther
Last updated: 2016-06-23 10:24:12 +0200
## Comment 20827
Date: 2015-04-22 14:23:26 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.90 Safari/537.36
Build Identifier:
For some reason sending a query such as select * from tables limit 1; takes about 30s. I have attached a pcap file.
Reproducible: Always
MonetDB 5 server v11.19.8 (64-bit, 64-bit oids)
This is an unreleased version
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2014 MonetDB B.V., all rights reserved
Visit http://www.monetdb.org/ for further information
Found 31.4GiB available memory, 8 available cpu cores
Libraries:
libpcre: 8.33 2013-05-28 (compiled with 8.33)
openssl: OpenSSL 1.0.1h 5 Jun 2014 (compiled with OpenSSL 1.0.1h 5 Jun 2014)
libxml2: 2.9.1 (compiled with 2.9.1)
Compiled by: skinkie@bigdata.openebs.nl (x86_64-unknown-linux-gnu)
Compilation: gcc -g -Werror -Wall -Wextra -W -Werror-implicit-function-declaration -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wformat=2 -Wno-format-nonliteral -Winit-self -Winvalid-pch -Wmissing-declarations -Wmissing-format-attribute -Wmissing-prototypes -Wold-style-definition -Wpacked -Wunknown-pragmas -Wvariadic-macros -fstack-protector-all -Wstack-protector -Wpacked-bitfield-compat -Wsync-nand -Wjump-misses-init -Wmissing-include-dirs -Wlogical-op -Wunreachable-code
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64
## Comment 20828
Date: 2015-04-22 14:25:40 +0200
From: @skinkie
Created attachment 333
JDBC Pcap output.
> Attached file: [jdbc.pcap](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_3711_jdbc.pcap_333) (application/octet-stream, 56150 bytes)
> Description: JDBC Pcap output.
## Comment 22138
Date: 2016-05-12 16:50:45 +0200
From: Martin van Dinther <<martin.van.dinther>>
Hi Stefan,
Analysing the jdbc.pcap file it shows that for each entered SQL query it also sends an SQL catalog query for each of the query result columns, so in the case of: select * from tables limit 1;
it also sends 9 additional queries to the server. This explains why it takes considerable more time (than for instance mclient) before it shows the query result data in the console.
I have analysed where and why this is done and implemented a fix.
The fix eliminates the need to send the additional SQL catalog queries, so the response should be much better in the next release of JdbcClient.
## Comment 22139
Date: 2016-05-12 16:53:08 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [e6a60eeea1cc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e6a60eeea1cc) made by Martin van Dinther <martin.van.dinther@monetdbsolutions.com> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e6a60eeea1cc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e6a60eeea1cc)
Changeset description:
Improved JdbcClient program when presenting query data to console.
It used to send an SQL catalog query for each query result column
which slowed down the interactive response considerably.
These additonal SQL catalog queries have been eliminated.
This fixes Bug #3711
| JDBC connection using jdbcclient.jar is very slow | https://api.github.com/repos/MonetDB/MonetDB/issues/3711/comments | 0 | 2020-11-30T13:01:22Z | 2024-06-27T12:07:07Z | https://github.com/MonetDB/MonetDB/issues/3711 | 753,459,698 | 3,711 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.