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: 2010-07-13 14:24:28 +0200
From: @romulogoncalves
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @drstmane
Duplicates: #104
Last updated: 2010-08-20 14:04:05 +0200
## Comment 14380
Date: 2010-07-13 14:24:28 +0200
From: @romulogoncalves
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
A selection with lengthened nested arithmetic expression crashes the mserver.
SELECT (1+(1+(1+....
Reproducible: Always
### Steps to Reproduce:
1.start mserver
2.Run mclient -lsql < <attached_file.sql>
3.
### Actual Results:
crashes mserver
### Expected Results:
% . table_name
% sql_add_single_value name
% tinyint type
% 1 length
[ 2000 ]
>[New Thread 0x7fffdfae7710 (LWP 5997)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdfae7710 (LWP 5997)]
0x00007fffe036137e in sa_destroy (sa=0x7fffd0007638)
at /ufs/goncalve/MonetDB/current/sql/src/common/sql_mem.mx:136
136 GDKfree(sa->blks[i]);
(gdb) up
1 0x00007fffe02d96cb in cq_delete (clientid=1, q=0x7fffd056f848)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_qc.mx:117
117 sa_destroy(q->sa);
(gdb) bt
0 0x00007fffe036137e in sa_destroy (sa=0x7fffd0007638)
at /ufs/goncalve/MonetDB/current/sql/src/common/sql_mem.mx:136
1 0x00007fffe02d96cb in cq_delete (clientid=1, q=0x7fffd056f848)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_qc.mx:117
2 0x00007fffe02d97a7 in qc_destroy (cache=0x7fffd00075d8)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_qc.mx:147
3 0x00007fffe02f3f72 in mvc_destroy (m=0x7fffd0005468)
at /ufs/goncalve/MonetDB/current/sql/src/server/sql_mvc.mx:761
4 0x00007fffe02abde2 in SQLexitClient (c=0x605b38)
at /ufs/goncalve/MonetDB/current/sql/src/backends/monet5/sql_scenario.mx:530
5 0x00007ffff7d230db in runScenarioBody (c=0x605b38)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:670
6 0x00007ffff7d23131 in runScenario (c=0x605b38)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_scenario.mx:682
7 0x00007ffff7cd6fe7 in MSserveClient (dummy=0x605b38)
at /ufs/goncalve/MonetDB/current/MonetDB5/src/mal/mal_session.mx:473
8 0x000000399f406a3a in start_thread () from /lib64/libpthread.so.0
9 0x000000399e8de77d in clone () from /lib64/libc.so.6
10 0x0000000000000000 in ?? ()
## Comment 14381
Date: 2010-07-13 14:24:57 +0200
From: @romulogoncalves
Created attachment 15
SQL code to re-create the bug
> Attached file: [bug2.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2610_bug2.sql_15) (text/plain, 8010 bytes)
> Description: SQL code to re-create the bug
## Comment 14382
Date: 2010-07-13 14:51:23 +0200
From: @drstmane
see also
- bug #1616 (was SF 1907048) --- appears to work fine, now:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/huge_math_expre.SF-1907048.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/huge_math_expre.SF-1907048.err.00.html
- bug #104 (was SF 921173) --- has been disable in
http://dev.monetdb.org/hg/MonetDB/rev/2288e44f8cb2
## Comment 14383
Date: 2010-07-13 14:54:08 +0200
From: @sjoerdmullender
This is already covered in SQL test src/test/BugDay_2005-10-06_2.9.3 huge_expression_and_column_name.SF-921173
## Comment 14384
Date: 2010-07-13 14:54:16 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #104 ***
| selection of big arithmetic expression | https://api.github.com/repos/MonetDB/MonetDB/issues/2610/comments | 0 | 2020-11-30T11:05:53Z | 2024-06-28T13:20:34Z | https://github.com/MonetDB/MonetDB/issues/2610 | 753,381,266 | 2,610 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-13 14:13:41 +0200
From: @romulogoncalves
To: SQL devs <<bugs-sql>>
Version: 2.40.1 (Oct2010) [obsolete]
CC: @njnes
Last updated: 2011-03-28 17:31:41 +0200
## Comment 14377
Date: 2010-07-13 14:13:41 +0200
From: @romulogoncalves
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
The insertion into a table with 818 columns where all the columns are type char(1) crashes the mserver.
Reproducible: Always
### Steps to Reproduce:
1. start mserver
2. run mclient -lsql < <attached_file.sql>
3.
### Actual Results:
mserver crashes
### Expected Results:
successful insertion
(gdb)
0 0x00007fffe02d7e24 in bin_optimizer (c=0x0, s=0x0)
at /ufs/goncalve/MonetDB/current/sql/src/server/bin_optimizer.mx:247
247 {
(gdb) l
242 }
243
244
245 stmt *
246 bin_optimizer(mvc *c, stmt *s)
247 {
248 if (s->optimized >= 3) {
249 if (s->rewritten)
250 return stmt_dup(s->rewritten);
251 else
(gdb) p s
$1 = (stmt *) 0x0
(gdb) up
1 0x00007fffe02d9309 in bin_optimizer (c=0x7fffd0005468, s=0x7fffd35fea08)
at /ufs/goncalve/MonetDB/current/sql/src/server/bin_optimizer.mx:586
586 stmt *ns = bin_optimizer(c, os);
(gdb) p os
$2 = (stmt *) 0x7fffd35fe958
(gdb)
## Comment 14378
Date: 2010-07-13 14:15:37 +0200
From: @romulogoncalves
Created attachment 14
The sql code re-create the bug
> Attached file: [bug1.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2609_bug1.sql_14) (text/plain, 25273 bytes)
> Description: The sql code re-create the bug
## Comment 14845
Date: 2010-08-30 09:23:21 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15237
Date: 2010-12-01 22:45:31 +0100
From: @njnes
test added to BugTracker-2010
## Comment 15238
Date: 2010-12-01 22:46:06 +0100
From: @njnes
fixed by flattening the stmt tree.
## Comment 15246
Date: 2010-12-02 10:44:33 +0100
From: @njnes
Changeset [e43c907a644b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e43c907a644b) 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=e43c907a644b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e43c907a644b)
Changeset description:
added test for bug #2609
## Comment 15652
Date: 2011-03-28 17:31:41 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
| insert into large number of columns | https://api.github.com/repos/MonetDB/MonetDB/issues/2609/comments | 0 | 2020-11-30T11:05:51Z | 2024-06-27T11:48:32Z | https://github.com/MonetDB/MonetDB/issues/2609 | 753,381,237 | 2,609 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-13 13:06:32 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes, @yzchang
Last updated: 2016-04-11 11:46:54 +0200
## Comment 14376
Date: 2010-07-13 13:06:32 +0200
From: @grobian
We need the following functions (of which some trivial):
ln
cbrt
radians
degrees
stddev
variance
round
trunc
md5 (sha1, sha256, sha512, rmd160)
bit_length
## Comment 14744
Date: 2010-08-20 14:26:46 +0200
From: @grobian
radians and degrees are already provided by src/sql/math.sql (and automagically loaded upon server creation)
## Comment 14848
Date: 2010-08-30 09:23:22 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15691
Date: 2011-03-28 17:36:35 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16045
Date: 2011-07-29 11:00:08 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16284
Date: 2011-09-16 15:10:42 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17697
Date: 2012-08-24 14:56:08 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18116
Date: 2012-11-27 15:25:09 +0100
From: @yzchang
No test needed for feature request
| Missing various functions used by Hibernate | https://api.github.com/repos/MonetDB/MonetDB/issues/2608/comments | 0 | 2020-11-30T11:05:47Z | 2024-06-28T13:40:40Z | https://github.com/MonetDB/MonetDB/issues/2608 | 753,381,200 | 2,608 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-13 12:47:40 +0200
From: @yzchang
To: GDK devs <<bugs-common>>
Version: 1.40.1 (Oct2010) [obsolete]
CC: @drstmane, @skinkie
Last updated: 2010-11-15 09:39:10 +0100
## Comment 14375
Date: 2010-07-13 12:47:40 +0200
From: @yzchang
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.7) Gecko/20100701 Firefox/3.6.7
Build Identifier:
Running the query 'select min(vcnt), max(vcnt), avg(vcnt) from tofsims_naive_direct_valuecount;' using the HEAD branch with '--set sql_optimizer=nov2009_pipe' triggers an assertion in BBPfree. This error does not occur when the default_pipe is used, and it does not occur in the Feb2010 and Jun2010 branched (using the nov2009_pipe).
The HEAD branch was installed yesterday afternoon around 16:00 using 'monetdb-install.sh --prefix=[...] --enable-sql --enable-geom --enable-debug'
Reproducible: Always
### Steps to Reproduce:
1. copy the dbfarm from /export/scratch1/zhang/MonetDB-current/var/MonetDB5/dbfarm/demo/ from the INS1 machine 'slippy'. It is ~16GB.
2. start: gdb --args mserver5 --set sql_optimizer=nov2009_pipe
3. start: mclient -ls -t and run the query 'select min(vcnt), max(vcnt), avg(vcnt) from tofsims_naive_direct_valuecount;'
4. wait until you get a SIGABRT
If copying dbfarm from slippy doesn't work, it can be built as the following:
1. copy the raw data from the INS1 machine 'jarl': /export/scratch0/zhang/tofsims/tofsims.*
2. execute these sql stmts:
create table tofsims_naive_direct (x int, y int, val int);
copy into tofsims_naive_direct from ('[pathto]/tofsims.x', '[pathto]/tofsims.y', '[pathto]/tofsims.v');
create view tofsims_naive_direct_valuecount as select x,y,count(val) as vcnt from tofsims_naive_direct group by x, y;
### Actual Results:
Output of GDB that might be interesting:
Starting program: /export/scratch1/zhang/MonetDB-current/bin/mserver5 --set sql_optimizer=nov2009_pipe
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffea656710 (LWP 23086)]
MonetDB server v5.21.0, based on kernel v1.39.0
Serving database 'demo', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 7.752 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /export/scratch1/zhang/MonetDB-current/etc/monetdb5.conf)
WARNING: LoaderException:loadLibrary:Loading error 'libmseed.so.2: cannot open shared object file: No such file or directory' from within file 'vault'
[New Thread 0x7fffdf87e710 (LWP 23091)]
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.39.0 loaded
[New Thread 0x7fffdf67d710 (LWP 23092)]
MonetDB/GIS module v0.19.0 loaded
>[New Thread 0x7fffdf47c710 (LWP 23095)]
[New Thread 0x7fffdf27b710 (LWP 23096)]
[New Thread 0x7fffdf07a710 (LWP 23097)]
[New Thread 0x7fffdee79710 (LWP 23098)]
[New Thread 0x7fffdec78710 (LWP 23099)]
>mserver5: gdk_bbp.c:2257: BBPfree: Assertion `b->P->sharecnt == 0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffea656710 (LWP 23086)]
0x000000334a2326c5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-6.fc12.x86_64 cyrus-sasl-lib-2.1.23-9.fc12.x86_64 geos-3.2.1-1.fc12.x86_64 glibc-2.11.2-1.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-7.fc12.x86_64 libcurl-7.19.7-10.fc12.x86_64 libgcc-4.4.4-10.fc12.x86_64 libidn-1.9-5.x86_64 libselinux-2.0.90-5.fc12.x86_64 libssh2-1.2.4-1.fc12.x86_64 libstdc++-4.4.4-10.fc12.x86_64 libuuid-2.16.2-9.fc12.x86_64 libxml2-2.7.6-2.fc12.x86_64 libxslt-1.1.26-1.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64 nspr-4.8.4-2.fc12.x86_64 nss-3.12.6-7.fc12.x86_64 nss-softokn-freebl-3.12.6-2.fc12.1.x86_64 nss-util-3.12.6-1.fc12.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0a-1.fc12.x86_64 pcre-7.8-3.fc12.x86_64 raptor-1.4.18-5.fc12.x86_64 readline-6.0-3.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
### Expected Results:
+------+-------+------------------------+
| L5 | L6 | L7 |
+======+=======+========================+
| 1 | 20509 | 1.7357339598738226 |
+------+-------+------------------------+
1 tuple
Sjoer has helped me to hunt the bug. The assertion was triggered by that BBPfree was called by BBPtrims to free a BAT with sharecnt == 1. Most probably, this BAT has been (incorrectly) added to 'bbptrim' because 'BBPtrimmable' does not check the 'sharecnt' of a BAT.
What supprises me a bit is that (without gdb) the assertion does not cause mserver5 to exit. With gdb, it can be seen that the thread that raises the assertion is a kind of stuck, and since all other threads are waiting for this thread, it causes mserver5 to hang.
## Comment 14404
Date: 2010-07-15 05:01:56 +0200
From: @skinkie
This bug [do notice the different linenumbers] hits me now too, with nothing more than a select * from mytable query. And having the default_pipe selected.
/opt/monetdb-testing/bin/mserver5 --dbinit="include sphinx;" --dbname="rechtspraak" --dbfarm=/mnt/data/monetdb-testing --set mapi_port=60003 --set sql_optimizer=default_pipe
MonetDB server v5.21.0, based on kernel v1.39.0
Serving database 'rechtspraak', using 2 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 3.865 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /opt/monetdb-testing/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:60003/
MonetDB/SQL module v2.39.0 loaded
>mserver5: ../../../src/gdk/gdk_bbp.mx:2367: BBPfree: Assertion `b->P->sharecnt == 0' failed.
Afgebroken
query;
select id, ljn, gepubliceerd, instantie, datum, publicatie, zaaknummers, uitspraak, conclusie, zittingsplaats, rechtsgebied, sector, soort, indicatie, kop from uitspraken
(yes that is required for full text search)
MonetDB server v5.21.0 (64-bit), based on kernel v1.39.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-testing
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: skinkie@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
## Comment 14406
Date: 2010-07-15 09:06:44 +0200
From: @drstmane
FYI:
re. "[do notice the different linenumbers]":
different line numbers are due to different files:
Jennie: gdk_bbp.c (pre-bootstrapped .c file from super source ball)
Stefan: gdk_bbp.mx (original .mx source file from HG repository)
## Comment 15133
Date: 2010-10-28 13:24:18 +0200
From: @grobian
Jennie recalls this bug was fixed.
| GDK: gdk_bbp.c:2257: BBPfree: Assertion `b->P->sharecnt == 0' failed | https://api.github.com/repos/MonetDB/MonetDB/issues/2607/comments | 0 | 2020-11-30T11:05:44Z | 2024-06-27T11:48:30Z | https://github.com/MonetDB/MonetDB/issues/2607 | 753,381,159 | 2,607 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-13 11:11:32 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
Last updated: 2010-08-30 09:18:07 +0200
## Comment 14373
Date: 2010-07-13 11:11:32 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9
Build Identifier:
In queries like
(SELECT ...) {UNION|EXCEPT|INTERSECT} (SELECT ...) ORDER BY ...;
the ORDER BY statement is ignored.
Reproducible: Always
### Steps to Reproduce:
sql>create table t1 (a int);
operation successful
sql>insert into t1 values (1);
1 affected row
sql>insert into t1 values (2);
1 affected row
sql>select * from t1;
+------+
| a |
+======+
| 1 |
| 2 |
+------+
2 tuples
ORDER BY is ignored:
sql>plan select * from t1 union all select * from t1 order by a;
% .plan table_name
% rel name
% clob type
% 44 length
union (
| project (
| | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| ) [ t1.a ],
| project (
| | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| ) [ t1.a ]
) [ a ]
sql>select * from t1 union all select * from t1 order by a;
+------+
| a |
+======+
| 1 |
| 2 |
| 1 |
| 2 |
+------+
4 tuples
sql>plan (select * from t1 union all select * from t1) order by a;
% .plan table_name
% rel name
% clob type
% 44 length
union (
| project (
| | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| ) [ t1.a ],
| project (
| | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| ) [ t1.a ]
) [ a ]
sql>(select * from t1 union all select * from t1) order by a;
+------+
| a |
+======+
| 1 |
| 2 |
| 1 |
| 2 |
+------+
4 tuples
sql>plan (select * from t1) union all (select * from t1) order by a;
% .plan table_name
% rel name
% clob type
% 44 length
union (
| project (
| | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| ) [ t1.a ],
| project (
| | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| ) [ t1.a ]
) [ a ]
sql>(select * from t1) union all (select * from t1) order by a;
+------+
| a |
+======+
| 1 |
| 2 |
| 1 |
| 2 |
+------+
4 tuples
ORDER BY is respected:
sql>plan select * from (select * from t1 union all select * from t1) as t
order by a;
% .plan table_name
% rel name
% clob type
% 46 length
project (
| union (
| | project (
| | | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| | ) [ t1.a ],
| | project (
| | | table(sys.t1) [ t1.a, t1.%TID% NOT NULL ]
| | ) [ t1.a ]
| ) [ a as t.a ]
) [ t.a ASC ] [ t.a ]
sql>select * from (select * from t1 union all select * from t1) as t order
by a;
+------+
| a |
+======+
| 1 |
| 1 |
| 2 |
| 2 |
+------+
4 tuples
### Actual Results:
ORDER BY is ignored
### Expected Results:
ORDER BY should be respected
The Feb2010 release showed the same behavior.
These two recent changes by Niels disabled these (and possibly other) query constructs completely, resulting in errors like
"ORDER BY: missing select operator"
http://dev.monetdb.org/hg/MonetDB/rev/bbe7f874d29b
http://dev.monetdb.org/hg/MonetDB/rev/77151d685024
While I believe that these query constructs are syntactically correct, Niels' intensions to disable them (and might have been that they are not yet supported by MonetDB.
To restore the Feb2010 behavior (for the UNION, EXCEPT & INTERSECT cases), I applied these changes:
http://dev.monetdb.org/hg/MonetDB/rev/35ebc65eb74c
http://dev.monetdb.org/hg/MonetDB/rev/e399a0ffae31
(the latter accidentally hidden in an other checkin).
## Comment 14374
Date: 2010-07-13 11:46:06 +0200
From: @drstmane
Changeset [43b62989158b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=43b62989158b) 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=43b62989158b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=43b62989158b)
Changeset description:
test for bug #2606 "ORDER BY over UNION / EXCEPT / INTERSECT is ignored"
## Comment 14560
Date: 2010-07-30 08:24:28 +0200
From: @drstmane
Fixed by Niels in http://dev.monetdb.org/hg/MonetDB/rev/3d5b55f4aebd
Thanks!
## Comment 14808
Date: 2010-08-30 09:18:07 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| ORDER BY over UNION / EXCEPT / INTERSECT is ignored | https://api.github.com/repos/MonetDB/MonetDB/issues/2606/comments | 0 | 2020-11-30T11:05:41Z | 2024-06-27T11:48:29Z | https://github.com/MonetDB/MonetDB/issues/2606 | 753,381,126 | 2,606 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-09 16:24:36 +0200
From: @grobian
To: clients devs <<bugs-clients>>
Version: -- development
CC: @yzchang
Last updated: 2016-04-11 11:41:46 +0200
## Comment 14344
Date: 2010-07-09 16:24:36 +0200
From: @grobian
Mapi lacks the ability to retrieve warnings received.
The motd should be removed, as it is no longer issued by mserver, and it should be replaced by a warning stack (motd is accidentially triggered on warnings).
The warning stack can then be read by e.g. mclient after each statement executed and printed. The stack must then be cleared by the application (mclient) when it was read.
## Comment 14849
Date: 2010-08-30 09:23:50 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15659
Date: 2011-03-28 17:34:14 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16017
Date: 2011-07-29 10:57:52 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16258
Date: 2011-09-16 15:07:29 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17657
Date: 2012-08-24 14:50:25 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18109
Date: 2012-11-27 15:16:26 +0100
From: @yzchang
No test for feature request
| functions to retrieve warnings from the server in Mapi | https://api.github.com/repos/MonetDB/MonetDB/issues/2605/comments | 0 | 2020-11-30T11:05:38Z | 2024-06-28T13:40:39Z | https://github.com/MonetDB/MonetDB/issues/2605 | 753,381,077 | 2,605 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-09 13:25:36 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2010-08-30 09:18:00 +0200
## Comment 14304
Date: 2010-07-09 13:25:36 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.86 Safari/533.4
Build Identifier:
select kvk from kvk where kvk not in (select kvk from kvk_nieuw union select
kvk from kvk_extra union select kvk from kvk_extra_nieuw);
kvk_nieuw does not exist here; sub expression executes as part and results in a proper error:
SELECT: no such table 'kvk_nieuw'
0x00007fffe43eb143 in rel_logical_exp (sql=0x147b068, rel=0x0, sc=0x167c278,
f=1) at ../../../src/server/rel_select.mx:2655
warning: Source file is more recent than executable.
2655 r = rel_value_exp(sql, &rel,
sval, f, ek);
(gdb) bt
0 0x00007fffe43eb143 in rel_logical_exp (sql=0x147b068, rel=0x0,
sc=0x167c278, f=1) at ../../../src/server/rel_select.mx:2655
1 0x00007fffe43f1c8c in rel_select_exp (sql=0x147b068, rel=0xab7ba8,
outer=0x0, sn=0x167c378, ek=...) at ../../../src/server/rel_select.mx:4410
2 0x00007fffe43f3233 in rel_query (sql=0x147b068, rel=0x0, sq=0x167c378,
toplevel=1, ek=...) at ../../../src/server/rel_select.mx:4730
3 0x00007fffe43f46b2 in rel_subquery (sql=0x147b068, rel=0x0, sq=0x167c378,
ek=...) at ../../../src/server/rel_select.mx:5073
4 0x00007fffe43f472c in rel_selects (sql=0x147b068, s=0x167c378) at
../../../src/server/rel_select.mx:5084
5 0x00007fffe43e2ade in rel_semantic (sql=0x147b068, s=0x167c378) at
../../../src/server/rel_semantic.mx:336
6 0x00007fffe43484c3 in sql_symbol2stmt (c=0x147b068, sym=0x167c378) at
../../../../src/backends/monet5/sql.mx:1362
7 0x00007fffe43945f6 in SQLparser (c=0x605878) at
../../../../src/backends/monet5/sql_scenario.mx:1275
8 0x00007ffff7b04fb2 in runPhase (c=0x605878, phase=1) at
../../../src/mal/mal_scenario.mx:604
9 0x00007ffff7b050ea in runScenarioBody (c=0x605878) at
../../../src/mal/mal_scenario.mx:646
10 0x00007ffff7b05371 in runScenario (c=0x605878) at
../../../src/mal/mal_scenario.mx:682
11 0x00007ffff7ab92af in MSserveClient (dummy=0x605878) at
../../../src/mal/mal_session.mx:473
12 0x00007ffff57a9547 in start_thread () from /lib/libpthread.so.0
13 0x00007ffff48db28d in clone () from /lib/libc.so.6
(gdb) q
Reproducible: Always
## Comment 14308
Date: 2010-07-09 13:37:21 +0200
From: @drstmane
"warning: Source file is more recent than executable."
Are you sure your build & testing environment is clean and consistent?
## Comment 14309
Date: 2010-07-09 13:39:15 +0200
From: @drstmane
While your debugger back-traces reveal the location where the segfault happens,
printing also the values of all variables used by the statement that segfault could help to also locate the actual reason for the segfault.
## Comment 14311
Date: 2010-07-09 13:43:26 +0200
From: @drstmane
a much simple way to reproduce the segfault:
create table t1 (a int);
-> operation successful
select * from t1;
-> 0 tuples
select * from t2;
-> SELECT: no such table 't2'
select * from t1 where a in (select b from t2);
-> server segfault
(also with Jun2010)
## Comment 14312
Date: 2010-07-09 13:46:37 +0200
From: @drstmane
and here's a gdb log with sources that match the compiled binaries and hence reveals the correct location of the segfault
$ gdb mserver5
GNU gdb (GDB) Fedora (7.0.1-48.fc12)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/HG/Jun2010/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/bin/mserver5...done.
(gdb) r
Starting program: /net/rig.ins.cwi.nl/export/scratch0/manegold/Monet/HG/Jun2010/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/bin/mserver5
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffea65b710 (LWP 17587)]
MonetDB server v5.20.3, based on kernel v1.38.2
Serving database 'demo', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 7.751 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/HG/Jun2010/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/etc/monetdb5.conf)
[New Thread 0x7fffdf89b710 (LWP 17588)]
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.38.3 loaded
[New Thread 0x7fffdf69a710 (LWP 17589)]
MonetDB/GIS module v0.18.1 loaded
>[New Thread 0x7fffdf499710 (LWP 17591)]
[New Thread 0x7fffdf298710 (LWP 17592)]
[New Thread 0x7fffdf097710 (LWP 17593)]
[New Thread 0x7fffdee96710 (LWP 17594)]
[New Thread 0x7fffdec95710 (LWP 17595)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdf499710 (LWP 17591)]
0x00007fffe03285ff in rel_logical_exp (sql=0x7fffd0005438, rel=0x0, sc=0x7fffd00d60d8, f=1) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_select.mx:2657
2657 if (!is_project(rel->op)) {
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-6.fc12.x86_64 cyrus-sasl-lib-2.1.23-9.fc12.x86_64 geos-3.2.1-1.fc12.x86_64 glibc-2.11.2-1.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-7.fc12.x86_64 libcurl-7.19.7-10.fc12.x86_64 libgcc-4.4.4-10.fc12.x86_64 libidn-1.9-5.x86_64 libselinux-2.0.90-5.fc12.x86_64 libssh2-1.2.4-1.fc12.x86_64 libstdc++-4.4.4-10.fc12.x86_64 libuuid-2.16.2-9.fc12.x86_64 libxml2-2.7.6-2.fc12.x86_64 libxslt-1.1.26-1.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64 nspr-4.8.4-2.fc12.x86_64 nss-3.12.6-7.fc12.x86_64 nss-softokn-freebl-3.12.6-2.fc12.1.x86_64 nss-util-3.12.6-1.fc12.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0a-1.fc12.x86_64 pcre-7.8-3.fc12.x86_64 raptor-1.4.18-5.fc12.x86_64 readline-6.0-3.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) bt
0 0x00007fffe03285ff in rel_logical_exp (sql=0x7fffd0005438, rel=0x0, sc=0x7fffd00d60d8, f=1) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_select.mx:2657
1 0x00007fffe032f203 in rel_select_exp (sql=0x7fffd0005438, rel=0x7fffd008a568, outer=0x0, sn=0x7fffd00d61d8, ek=...) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_select.mx:4425
2 0x00007fffe03307a9 in rel_query (sql=0x7fffd0005438, rel=0x0, sq=0x7fffd00d61d8, toplevel=1, ek=...) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_select.mx:4745
3 0x00007fffe0331c28 in rel_subquery (sql=0x7fffd0005438, rel=0x0, sq=0x7fffd00d61d8, ek=...) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_select.mx:5088
4 0x00007fffe0331ca2 in rel_selects (sql=0x7fffd0005438, s=0x7fffd00d61d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_select.mx:5099
5 0x00007fffe031ff5d in rel_semantic (sql=0x7fffd0005438, s=0x7fffd00d61d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/server/rel_semantic.mx:336
6 0x00007fffe028545f in sql_symbol2stmt (c=0x7fffd0005438, sym=0x7fffd00d61d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql.mx:1340
7 0x00007fffe02d1856 in SQLparser (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql_scenario.mx:1203
8 0x00007ffff7d22c92 in runPhase (c=0x605b38, phase=1) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:604
9 0x00007ffff7d22dca in runScenarioBody (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:646
10 0x00007ffff7d23051 in runScenario (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:682
11 0x00007ffff7cd6f0d in MSserveClient (dummy=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_session.mx:473
12 0x000000347c406a3a in start_thread () from /lib64/libpthread.so.0
13 0x000000347b8de77d in clone () from /lib64/libc.so.6
14 0x0000000000000000 in ?? ()
(gdb) li
2652 sql->errstr[0] = 0;
2653
2654 /* TODO remove null checking (not needed in correlated case because of the semi/anti join) ! */
2655 rel = left = rel_dup(left);
2656 r = rel_value_exp(sql, &rel, sval, f, ek);
2657 if (!is_project(rel->op)) {
2658 rel = rel_project(rel, NULL);
2659 rel_project_add_exp(sql, rel, r);
2660 }
2661 z = rel;
(gdb) p rel
$1 = (sql_rel *) 0x0
(gdb)
## Comment 14314
Date: 2010-07-09 13:59:23 +0200
From: @skinkie
(In reply to comment 1)
> "warning: Source file is more recent than executable."
>
> Are you sure your build & testing environment is clean and consistent?
Since the only thing since I touched the openkvk machine today was replying and showing errors. And the request in the unixODBC-bug of a month ago required a recompilation without my fix, it is pretty obvious that I don't have n-trees on my machine for each bug that I submit.
(In reply to comment 2)
> While your debugger back-traces reveal the location where the segfault happens,
> printing also the values of all variables used by the statement that segfault
> could help to also locate the actual reason for the segfault.
Could you elaborate what values /can/, /should/ and /must/ be shown and how this can be achieved from within gdb? It would be a great addition to the debugging and monetdb-internals documentation.
I'm not talking about randomly type print <<somevariable>> present in the list for that stackdepth.
## Comment 14317
Date: 2010-07-09 14:40:47 +0200
From: @drstmane
There is no need to have "n-trees" on your machine and I surely did not ask for that. However, debugger traces do not make any sense if the source code available when running the debugger is not the very same version of the source code that the binaries that the debugger runs are compiled from. Basically, the compiled code contains references to the original source code that allow the debugger to show the code that is executed. If the source code has been changed between compiling it and running the compiled binaries in the debugger, these references might/will not point to the correct lines any more. Consequently, debugger traces are useless in that case. That's why the debugger warns you if your source are new then the binaries and hence potentially modified since compilation. If you compare your trace to mine, you'll notice that the reported location of the segfault differs. I'm pretty sure, though, the segfault in you case happened in the statement as in my case; however, since your source seems to have been modified since their compilation, the debugger points to a wrong line/statement. --- This is not critique, just a hint. To locate and fix bugs, we need sufficient and *accurate* information. Incorrect information is misleading and delays/prevents bug fixing.
Most frequent candidates for segfault are, e.g., null-pointer dereferences;
hence looking for pointer dereferences in the very statement where the segfault occurs --- provided the configuration is clean and sound, i.e., source code matches binaries; see above --- and printing the pointers values is a good starting point.
E.g., in my log the segfault is reported in the statement
2657 if (!is_project(rel->op)) {
Obviously, rel is a pointer that is dereferenced here; hence
(gdb) p rel
$1 = (sql_rel *) 0x0
reveals that indeed rel being a null-pointer causes the segfault, here.
(Now it's our task to find out why rel is null, and whether we either need to prevent that or correctly deal with it ...)
## Comment 14671
Date: 2010-08-13 02:21:00 +0200
From: @skinkie
Can do something like this?
diff -r [65a029afacb5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=65a029afacb5) sql/src/server/rel_select.mx
--- a/sql/src/server/rel_select.mx Thu Aug 12 12:44:23 2010 +0200
+++ b/sql/src/server/rel_select.mx Fri Aug 13 02:20:16 2010 +0200
@@ -2656,12 +2656,14 @@
/* TODO remove null checking (not needed in correlated case because of the semi/anti join) ! */
rel = left = rel_dup(left);
r = rel_value_exp(sql, &rel, sval, f, ek);
- if (!is_project(rel->op)) {
- rel = rel_project(rel, NULL);
- rel_project_add_exp(sql, rel, r);
+ if (r) {
+ if (!is_project(rel->op)) {
+ rel = rel_project(rel, NULL);
+ rel_project_add_exp(sql, rel, r);
+ }
+ z = rel;
+ correlated = 1;
}
- z = rel;
- correlated = 1;
}
if (!r || !(r=rel_check_type(sql, st, r, type_equal))) {
exp_destroy(r);
## Comment 14739
Date: 2010-08-19 18:28:03 +0200
From: @njnes
Changeset [2565be77974c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2565be77974c) 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=2565be77974c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2565be77974c)
Changeset description:
check for return values properly (should solve bug #2604)
## Comment 14740
Date: 2010-08-19 18:33:20 +0200
From: @njnes
Changeset [f63520ed7cb9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f63520ed7cb9) 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=f63520ed7cb9](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f63520ed7cb9)
Changeset description:
added test for Bug #2604
## Comment 14794
Date: 2010-08-30 09:18:00 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| segfault having non existing table IN (...) | https://api.github.com/repos/MonetDB/MonetDB/issues/2604/comments | 0 | 2020-11-30T11:05:35Z | 2024-06-27T11:48:26Z | https://github.com/MonetDB/MonetDB/issues/2604 | 753,381,036 | 2,604 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-09 10:57:23 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.5 (Jun2010-SP2) [obsolete]
CC: @mlkersten
Last updated: 2010-11-15 09:39:04 +0100
## Comment 14276
Date: 2010-07-09 10:57:23 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9
Build Identifier:
On Windows, test MonetDB5/src/mal/Tests/tst274.mal produces incomplete or no output at all:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_mal/tst274.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Mic.64.64.d.1-Windows6.0/src_mal/tst274.out.00.html
Reproducible: Always
### Steps to Reproduce:
by nightly testing
or
run test yourself
### Actual Results:
test fails and test output differs from stable one
### Expected Results:
test should work fine, i.e., its output should match the approved stable output
## Comment 14461
Date: 2010-07-18 09:32:54 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_mal/tst274.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Mic.64.64.d.1-Windows6.0/src_mal/tst274.out.00.html
## Comment 14508
Date: 2010-07-21 12:52:05 +0200
From: @drstmane
Changeset [fcc2ce4e1a10](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=fcc2ce4e1a10) 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=fcc2ce4e1a10](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=fcc2ce4e1a10)
Changeset description:
extended tst274 to support analysis of bug #2603
I suspect that on Windows profiler.getTrace()
might return an empty result BAT,
rather than that there is a missing flush
in io.print() ...
## Comment 14511
Date: 2010-07-22 10:35:46 +0200
From: @drstmane
The extended test shows that, in Windows, indeed the result BAT of profiler.getTrace() is empty or contains at most one tuple:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_mal/tst274.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.64.d.1-Windows6.0/src_mal/tst274.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Mic.64.64.d.1-Windows6.0/src_mal/tst274.out.00.html
Hence, the question is what does profiler.getTrace() internally do differently on Windows than on Unix-like systems?
## Comment 14850
Date: 2010-08-30 09:23:59 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 14874
Date: 2010-09-06 15:34:58 +0200
From: @sjoerdmullender
The problem here is that instructions are only added to the trace if they "take time". This, in combination with the limited resolution on Windows of the function GDKusec() which is used to measure how much time an instruction takes, makes that most of the time the instructions aren't added to the trace.
On the Oct2010 branch, I have now changed the implementation of GDKusec() to use QueryPerformanceCounter instead of ftime which should help, but it is certainly not a full-proof solution (i.e. the test still fails, but just "less so").
## Comment 14901
Date: 2010-09-10 16:22:19 +0200
From: @sjoerdmullender
Fixed in the Oct2010 branch.
| test MonetDB5/src/mal/Tests/tst274.mal fails on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2603/comments | 0 | 2020-11-30T11:05:31Z | 2024-06-27T11:48:25Z | https://github.com/MonetDB/MonetDB/issues/2603 | 753,380,985 | 2,603 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-09 00:29:46 +0200
From: Mark Bucciarelli <<mkbucc>>
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
CC: @njnes
Last updated: 2010-08-30 09:17:57 +0200
## Comment 14273
Date: 2010-07-09 00:29:46 +0200
From: Mark Bucciarelli <<mkbucc>>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier:
Save following sql to the file t3.sql and run mclient
as below.
CREATE TABLE "test"."tbl1" (
"id" int NOT NULL,
"id1" int NOT NULL,
"id2" int NOT NULL,
"name" varchar(300) NOT NULL,
CONSTRAINT "test_id_pkey" PRIMARY KEY ("id"),
CONSTRAINT "test_id1_name_unique" UNIQUE ("id1", "name")
)
;
INSERT INTO tbl1 VALUES (1, 1, 1, 'one')
;
SELECT
(1) as "a"
FROM
tbl1
WHERE
id1 = 2;
;
SELECT
(1) as "a"
FROM
tbl1
WHERE (
id1 = 1
AND name = 'one'
AND NOT id = 1
)
;
DROP TABLE "test"."tbl1"
;
Reproducible: Always
### Steps to Reproduce:
1. create t3.sql as noted above
2. run as noted below in results.
### Actual Results:
$ mclient -u test -l sql -d test t3.sql
password:
[ 1 ]
% . table_name
% a name
% tinyint type
% 1 length
% . table_name
% a name
% tinyint type
% 1 length
[ 1 ]
$
### Expected Results:
$ mclient -u test -l sql -d test t3.sql
password:
[ 1 ]
% . table_name
% a name
% tinyint type
% 1 length
% . table_name
% a name
% tinyint type
% 1 length
$
## Comment 14275
Date: 2010-07-09 09:18:22 +0200
From: @njnes
Changeset [0fc84c670ac1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0fc84c670ac1) 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=0fc84c670ac1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0fc84c670ac1)
Changeset description:
fixed bug #2602
relational optimizer incorrectly removed expressions, when trying to use
the indices.
## Comment 14785
Date: 2010-08-30 09:17:57 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| WHERE clause with AND NOT is broken | https://api.github.com/repos/MonetDB/MonetDB/issues/2602/comments | 0 | 2020-11-30T11:05:29Z | 2024-06-27T11:48:24Z | https://github.com/MonetDB/MonetDB/issues/2602 | 753,380,950 | 2,602 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-08 20:50:29 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2011-01-25 15:39:02 +0100
## Comment 14266
Date: 2010-07-08 20:50:29 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
It would be lovely to have some sort of segfault and sigabort handlers that can show the last actions of all the modules. Most simply I would envision the last xquery or sql query executed.
Reproducible: Always
## Comment 15437
Date: 2011-01-25 15:39:02 +0100
From: @grobian
this is hard to do, but patches are welcome.
| Segfault handler that shows last action for each module | https://api.github.com/repos/MonetDB/MonetDB/issues/2601/comments | 0 | 2020-11-30T11:05:25Z | 2024-06-28T13:40:38Z | https://github.com/MonetDB/MonetDB/issues/2601 | 753,380,908 | 2,601 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-08 16:59:10 +0200
From: Maurice van Keulen <<m.vankeulen>>
To: XQuery devs <<bugs-xquery>>
Version: 11.1.1 (Mar2011) [obsolete]
CC: jan.rittinger, m.vankeulen, @drstmane
Last updated: 2011-04-28 16:38:54 +0200
## Comment 14265
Date: 2010-07-08 16:59:10 +0200
From: Maurice van Keulen <<m.vankeulen>>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3
Build Identifier:
Attached query does not compile. "pf bug-docaccess.xq" returns
fatal error: unexpected document column in doc_access (4)
halted in milgen.brg (do_reduce), line 7660
If you replace "node-name" by "name" it does compile (and it works). The difference is that now the namespace is also in the result and I do not want that.
Reproducible: Always
### Steps to Reproduce:
1. pf bug-docaccess.xq
### Actual Results:
fatal error: unexpected document column in doc_access (4)
halted in milgen.brg (do_reduce), line 7660
### Expected Results:
if executed, the query should return
"v1=1",
"v2=3"
## Comment 14267
Date: 2010-07-08 20:54:04 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi Maurice,
I can't see your attachment here.
...Anyway I could reproduce your problem. I corrected the MIL implementation in the Feb2010, Jun2010, and default branches.
This fix however does not save you from using the correct function---fn:node-name returns an expanded QName instead of a string. What you were looking for is fn:local-name.
## Comment 14290
Date: 2010-07-09 12:51:45 +0200
From: Maurice van Keulen <<m.vankeulen>>
Created attachment 12
Failing query
Forgot to add the failing query
> Attached file: [bug-docaccess.xq](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2600_bug-docaccess.xq_12) (text/plain, 247 bytes)
> Description: Failing query
## Comment 14292
Date: 2010-07-09 12:55:01 +0200
From: Maurice van Keulen <<m.vankeulen>>
Bug indeed fixed: query compiles.
However, when I run it, it now produces the error message
!ERROR: merged_union: BAT/column 2 of table 1 must have a dense head.
!ERROR: CMDmerged_union: operation failed.
But, indeed you are right: I need local-name instead of node-name. If I use local-name, everything works fine. I don't know if you'd like to fix the run-time error, but for me it works now because I use now local-name.
Thanx!
## Comment 14360
Date: 2010-07-10 19:03:09 +0200
From: @drstmane
Changeset [9c253dc27961](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9c253dc27961) 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=9c253dc27961](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9c253dc27961)
Changeset description:
added test for bug #2600
As reported, a query containing node-name() compiles fine after Jan R.'s fix.
However, as reported, such query now triggers a runtime error
(when run without property checking, which it the default):
!ERROR: merged_union: BAT/column 2 of table 1 must have a dense head.
When run with property checking enabled (`Mserver --debug=10`),
the query works fine.
Replacing node-name() by local-name() make the query run fine
with and without property checking.
## Comment 14851
Date: 2010-08-30 09:24:08 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15692
Date: 2011-03-28 17:37:05 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15761
Date: 2011-04-28 16:38:54 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PF: Query with node-name() doesn't compile | https://api.github.com/repos/MonetDB/MonetDB/issues/2600/comments | 0 | 2020-11-30T11:05:22Z | 2024-06-28T13:20:34Z | https://github.com/MonetDB/MonetDB/issues/2600 | 753,380,873 | 2,600 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-08 10:32:56 +0200
From: Likun <<likun121>>
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
CC: @njnes
Last updated: 2010-08-30 09:18:33 +0200
## Comment 14263
Date: 2010-07-08 10:32:56 +0200
From: Likun <<likun121>>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier:
The server crashes with some special prepare statements. It's very easy to reproduce the problem. E.g., input the following sql statements in mclient:
1. create table tt (a int, b int);
2. prepare select * from tt where a>?+1;
I think we can use some other similar expressions to reproduce the problem.
When I search the previous bugs, I find bug #2459 and its solution (http://bugs.monetdb.org/show_bug.cgi?id=2549). According to http://dev.monetdb.org/hg/MonetDB/rev/68a4ee44bdf2, I modify file sql/src/server/rel_select.mx, then the server accepts some expressions, but also crashes in some others. The followings are the test prepare statements and their results:
1. prepare select * from tt where a>?+1; -- crash
2. prepare select * from tt where a>1+?; -- good
3. prepare select * from tt where a>1+?*2; -- crash
4. prepare select * from tt where a>2*?+1; -- good
Reproducible: Always
### Steps to Reproduce:
1. start server and mclient, then input the following sql statements in mclient
2. create table tt (a int, b int);
3. prepare select * from tt where a>?+1; maybe we can use some other similar expressions to reproduce the problem.
4. then the server crashes immediately.
## Comment 14264
Date: 2010-07-08 15:46:21 +0200
From: @drstmane
Changeset [1481eb763890](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1481eb763890) 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=1481eb763890](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1481eb763890)
Changeset description:
added test for bug #2599:
as reported, with
create table tt (a int, b int);
the following two prepare statements appear to work fine:
prepare select * from tt where a>1+?;
prepare select * from tt where a>2*?+1;
but these two crash the server with a segfault:
prepare select * from tt where a>?+1;
prepare select * from tt where a>1+?*2;
## Comment 14268
Date: 2010-07-08 23:40:54 +0200
From: @njnes
Changeset [01ad3c3ad5e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=01ad3c3ad5e8) 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=01ad3c3ad5e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=01ad3c3ad5e8)
Changeset description:
fix bug #2599 in handling parameters in binary functions
## Comment 14274
Date: 2010-07-09 08:38:55 +0200
From: Likun <<likun121>>
I have tried these changes, all is ok, thanks!
(In reply to comment 2)
> Changeset [01ad3c3ad5e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=01ad3c3ad5e8) 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=01ad3c3ad5e8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=01ad3c3ad5e8)
>
> Changeset description:
>
> fix bug #2599 in handling parameters in binary functions
## Comment 14828
Date: 2010-08-30 09:18:33 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| server crashes when prepare statement has expression like "a>?+1" | https://api.github.com/repos/MonetDB/MonetDB/issues/2599/comments | 0 | 2020-11-30T11:05:19Z | 2024-06-27T11:48:21Z | https://github.com/MonetDB/MonetDB/issues/2599 | 753,380,836 | 2,599 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 22:37:11 +0200
From: Mark Bucciarelli <<mkbucc>>
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2010-08-30 09:18:31 +0200
## Comment 14261
Date: 2010-07-07 22:37:11 +0200
From: Mark Bucciarelli <<mkbucc>>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier:
CREATE TABLE "test"."tbl1" (
"id" int NOT NULL,
CONSTRAINT "c1" PRIMARY KEY ("id")
)
;
CREATE TABLE "test"."tbl2" (
"id" int NOT NULL,
"fk" int NOT NULL,
CONSTRAINT "c2" PRIMARY KEY ("id"),
CONSTRAINT "c3" FOREIGN KEY ("fk") REFERENCES "test"."tbl1" ("id")
)
;
INSERT INTO "test"."tbl1" VALUES (1)
;
INSERT INTO "test"."tbl2" VALUES (1,1)
;
DELETE FROM "test"."tbl1";
DROP TABLE "test"."tbl2";
DROP TABLE "test"."tbl1";
Reproducible: Always
### Steps to Reproduce:
1. save sql above to text file
2. create test schema and run the sql
### Actual Results:
$ mclient -u test -l sql -d test t2.sql
password:
[ 1 ]
[ 1 ]
MAPI = test@localhost:50000
QUERY = CREATE TABLE "test"."tbl1" (
"id" int NOT NULL,
CONSTRAINT "c1" PRIMARY KEY ("id")
)
;
CREATE TABLE "test"."tbl2" (
"id" int NOT NULL,
"fk" int NOT NULL,
CONSTRAINT "c2" PRIMARY KEY ("id"),
CONSTRAINT "c3" FOREIGN KEY ("fk") REFERENCES "test"."tbl1" ("id")
)
;
INSERT INTO "test"."tbl1" VALUES (1)
;
INSERT INTO "test"."tbl2" VALUES (1,1)
;
DELETE FROM "test"."tbl1";
DROP TABLE "test"."tbl2";
DROP TABLE "test"."tbl1";
ERROR = !SQLException:assert:DELETE: FOREIGN KEY constraint 'tbl1.c1' violated
$
### Expected Results:
...
ERROR = !SQLException:assert:DELETE: FOREIGN KEY constraint 'tbl2.c3' violated
$
## Comment 14269
Date: 2010-07-08 23:51:29 +0200
From: @njnes
fixed error message
## Comment 14270
Date: 2010-07-09 00:06:51 +0200
From: @njnes
Changeset [0ab107bd24ec](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0ab107bd24ec) 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=0ab107bd24ec](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0ab107bd24ec)
Changeset description:
fixed bug #2598 (ie corrected error message)
## Comment 14348
Date: 2010-07-10 08:17:01 +0200
From: @drstmane
No extra test required as covered by tests
sql/src/test/BugConstraints/Tests/delete_primarykey_1643845.*
sql/src/test/Update_Delete_action/Tests/delete_restrict.*
sql/src/test/Via-m/Tests/event_s11.*
## Comment 14824
Date: 2010-08-30 09:18:31 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| Wrong constraint in error message when delete prohibited due to foreign key | https://api.github.com/repos/MonetDB/MonetDB/issues/2598/comments | 0 | 2020-11-30T11:05:16Z | 2024-06-27T11:48:20Z | https://github.com/MonetDB/MonetDB/issues/2598 | 753,380,804 | 2,598 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 18:15:49 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
Last updated: 2010-08-30 09:18:29 +0200
## Comment 14260
Date: 2010-07-07 18:15:49 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
The output of test sql/src/test/Tests/rank.sql appear to vary a lot across platforms, although I'd expect deterministic output from ROW_NUMBER(), RANK() & DENSE_RANK().
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.64.d.1-Fedora12/src_test/rank.out.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run test yourself
### Actual Results:
test fails, i.e., output differs from approved stable output
### Expected Results:
test should work fine, i.e., output should match approved stable output
## Comment 14367
Date: 2010-07-12 15:22:58 +0200
From: @sjoerdmullender
Changeset [23d41c408edf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=23d41c408edf) 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=23d41c408edf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=23d41c408edf)
Changeset description:
Merge with Jun2010 branch.
See also bug #2597.
## Comment 14370
Date: 2010-07-12 17:13:45 +0200
From: @sjoerdmullender
Changeset [83fa6e2eb7f8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=83fa6e2eb7f8) 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=83fa6e2eb7f8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=83fa6e2eb7f8)
Changeset description:
Fix bug #2597.
The function isMapOp is supposed to be conservative, but it wasn't conservative enough.
Don't treat batcalc.mark_grp and batcalc.rank_grp as map operators.
## Comment 14371
Date: 2010-07-12 17:13:46 +0200
From: @sjoerdmullender
Changeset [d68bb2df0db8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d68bb2df0db8) 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=d68bb2df0db8](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d68bb2df0db8)
Changeset description:
Merge with Jun2010 branch: Fix bug #2597.
The function isMapOp is supposed to be conservative, but it wasn't conservative enough.
Don't treat batcalc.mark_grp and batcalc.rank_grp as map operators.
## Comment 14462
Date: 2010-07-18 09:36:57 +0200
From: @drstmane
TestWeb confirms Sjoerd'\''s fix:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora12/src_test/rank.out.00.html
## Comment 14818
Date: 2010-08-30 09:18:29 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| test sql/src/test/Tests/rank.sql produces varying (wrong?) output on various platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/2597/comments | 0 | 2020-11-30T11:05:13Z | 2024-06-27T11:48:19Z | https://github.com/MonetDB/MonetDB/issues/2597 | 753,380,770 | 2,597 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 17:00:23 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
Last updated: 2010-08-30 09:17:58 +0200
## Comment 14259
Date: 2010-07-07 17:00:23 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
Some TPCH tests fail on some Windows configurations with
Assertion failed: q->argc > 1, file .\..\..\..\src\optimizer\opt_mergetable.mx, line 442
!FATAL: BATSIGabort: signal 22 caught by thread 163315985
or
Assertion failed: r->argc > 1, file .\..\..\..\src\optimizer\opt_mergetable.mx, line 684
!FATAL: BATSIGabort: signal 22 caught by thread 156998321
see
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.32.d.1-Windows6.0/src_benchmarks_tpch/04.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.64.d.1-Windows6.0/src_benchmarks_tpch/04.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Mic.64.64.d.1-Windows6.0/src_benchmarks_tpch/04.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.32.d.1-Windows6.0/src_benchmarks_tpch/12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.64.d.1-Windows6.0/src_benchmarks_tpch/12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Mic.64.32.d.1-Windows6.0/src_benchmarks_tpch/12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Mic.64.64.d.1-Windows6.0/src_benchmarks_tpch/12.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.32.d.1-Windows6.0/src_benchmarks_tpch/21.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.64.d.1-Windows6.0/src_benchmarks_tpch/21.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Mic.64.64.d.1-Windows6.0/src_benchmarks_tpch/21.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.32.d.1-Windows6.0/src_benchmarks_tpch/01-22.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.64.64.d.1-Windows6.0/src_benchmarks_tpch/01-22.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Mic.64.32.d.1-Windows6.0/src_benchmarks_tpch/01-22.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Mic.64.64.d.1-Windows6.0/src_benchmarks_tpch/01-22.err.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run tests on Windows
### Actual Results:
tests fail, i.e., output differs from approved stable output
### Expected Results:
tests should work fine, i.e., output should match approved stable output
## Comment 14435
Date: 2010-07-16 09:32:33 +0200
From: @drstmane
After back-porting a recent mitosis fix from the default branch to the Jun2010 branch, cf., http://dev.monetdb.org/hg/MonetDB/rev/735b133ade47
all TPC-H tests also appear to work fine on Windows, again.
Hence, the problem was probably related to mergetable not coping well with mitosis generating only one single partition ...
## Comment 14441
Date: 2010-07-16 18:54:01 +0200
From: @drstmane
If I understand the mergetable code correctly, both assertions are sanity checks that mat.mew() or mat.pack() calls have more than one argument, which is not the case if mitosis creates only one single partition ("piece").
Hence, preventing mitosis from creating only one single partition ("piece") (as done in http://dev.monetdb.org/hg/MonetDB/rev/735b133ade47 --- at least for non-octopus cases) appears to be necessary and expected/assumed by mergetable.
For plain mitosis + mergetable, I consider this very bug "fixed by preventing" it.
Once octopus comes into play an expects mitosis + mergetable to create (prepare) plans for a single tentacle, only, the mergetable code has to be fixed to cope with that case.
## Comment 14442
Date: 2010-07-16 18:55:22 +0200
From: @drstmane
For the records:
potentially related bugs are
- bug #2557 "SQLException:assert:INSERT INTO: FOREIGN KEY constraint violated on 64-bits"
- bug #2613 "SQL creates wrong MAL code a.o. with GDK_nr_threads=1"
## Comment 14788
Date: 2010-08-30 09:17:58 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| some TPCH tests fail with assertion in opt_mergetable on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2596/comments | 0 | 2020-11-30T11:05:10Z | 2024-06-27T11:48:18Z | https://github.com/MonetDB/MonetDB/issues/2596 | 753,380,737 | 2,596 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T10:59:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/2595/comments | 0 | 2020-11-30T11:05:08Z | 2020-11-30T11:05:09Z | https://github.com/MonetDB/MonetDB/issues/2595 | 753,380,716 | 2,595 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 15:29:53 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 11.9.5 (Apr2012-SP1) [obsolete]
CC: charnik, @njnes
Last updated: 2012-06-19 11:20:12 +0200
## Comment 14252
Date: 2010-07-07 15:29:53 +0200
From: @grobian
create table skyboom (i int, ts timestamp);
select i as boom1, ts as boom2 from skyboom
union
select NULL as boom1, NULL as boom2;
The result is:
types char(0,0) boom1(str) and int(32,0) (int) are not equal
and if we could do an explicit CAST(NULL AS int) instead, it would complain about boom2.
This is a generic problem, as NULL gets typed as char, while it should be casted to any type required, unless explicitly casted to a type. Perhaps a NULL type is required.
## Comment 14841
Date: 2010-08-30 09:23:20 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15683
Date: 2011-03-28 17:36:31 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16035
Date: 2011-07-29 11:00:03 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16273
Date: 2011-09-16 15:10:38 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17261
Date: 2012-05-16 22:49:31 +0200
From: @njnes
Changeset [3012edaf1396](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3012edaf1396) 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=3012edaf1396](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3012edaf1396)
Changeset description:
added test for bug #2594
## Comment 17262
Date: 2012-05-16 22:51:14 +0200
From: @njnes
implemented default NULL as type ANY.
| NULL cannot automatically be casted to every other type | https://api.github.com/repos/MonetDB/MonetDB/issues/2594/comments | 0 | 2020-11-30T11:05:05Z | 2024-06-27T11:48:17Z | https://github.com/MonetDB/MonetDB/issues/2594 | 753,380,684 | 2,594 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 15:13:37 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.40.1 (Oct2010) [obsolete]
CC: @njnes
Last updated: 2011-03-28 17:31:36 +0200
## Comment 14251
Date: 2010-07-07 15:13:37 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
test sql/src/test/Tests/load_dec_as_int.sql.src fails a file sql/src/test/load_dec_as_int.sql is missing:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.GNU.64.64.d.1-Fedora12/mTests10/src/test/.load_dec_as_int.SKIPPED
is seems that the file was never checked in;
the original checkin looks as follows:
"
changeset: 24323:b48e7775f3de
user: Niels Nes <niels@cwi.nl>
date: Tue Dec 11 19:01:21 2007 +0000
files: sql/src/test/Tests/All sql/src/test/Tests/load_dec_as_int.sql.src sql/src/test/Tests/load_dec_as_int.stable.err sql/src/test/Tests/load_dec_as_int.stable.out
description:
add test for a 'new of feature', well we are less stricked on data loading
now. We allow . as a valid number. Some users like to load decimals
I (which sometimes start as .08) into numbers (tiny, small etc integers)
"
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run test yourself
### Actual Results:
test fails due to missing file
### Expected Results:
all required files should be available to make the test work
## Comment 14463
Date: 2010-07-18 09:38:32 +0200
From: @drstmane
Updated URL is
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.GNU.64.64.d.1-Fedora12/mTests10/src/test/.load_dec_as_int.SKIPPED
## Comment 14839
Date: 2010-08-30 09:23:19 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15262
Date: 2010-12-03 21:45:05 +0100
From: @njnes
removed the test. Unable to recover the old real test file.
## Comment 15639
Date: 2011-03-28 17:31:36 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
| test sql/src/test/Tests/load_dec_as_int.sql.src fails a file sql/src/test/load_dec_as_int.sql is missing | https://api.github.com/repos/MonetDB/MonetDB/issues/2593/comments | 0 | 2020-11-30T11:05:03Z | 2024-06-27T11:48:16Z | https://github.com/MonetDB/MonetDB/issues/2593 | 753,380,655 | 2,593 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 14:57:36 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
Last updated: 2010-08-30 09:17:59 +0200
## Comment 14250
Date: 2010-07-07 14:57:36 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
test sql/src/test/BugTracker-2009/Tests/dumping_tables.SF-2776908--optimizers.sql produces different output than it used to;
cf., e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2009/dumping_tables.SF-2776908--optimizers.out.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run test yourself
### Actual Results:
test fails, i.e., output differs from approved stable output
### Expected Results:
test should work fine, i.e., output should match approved stable output
## Comment 14445
Date: 2010-07-16 19:01:41 +0200
From: @drstmane
fixed by Sjoerd in
http://dev.monetdb.org/hg/MonetDB/rev/8c79637bf83d
## Comment 14792
Date: 2010-08-30 09:17:59 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| test sql/src/test/BugTracker-2009/Tests/dumping_tables.SF-2776908--optimizers.sql produces different output | https://api.github.com/repos/MonetDB/MonetDB/issues/2592/comments | 0 | 2020-11-30T11:05:00Z | 2024-06-27T11:48:15Z | https://github.com/MonetDB/MonetDB/issues/2592 | 753,380,618 | 2,592 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 14:55:06 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2010-08-30 09:18:17 +0200
## Comment 14249
Date: 2010-07-07 14:55:06 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
test sql/src/test/VOC/Tests/VOC.SQL.sh fails with
"Connection warning: WARNING: could not read createdb.sql"
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_VOC/VOC.out.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run test yourself
### Actual Results:
test fails, i.e., output differs from approved stable output
### Expected Results:
test should work fine, i.e., output should match approved stable output
## Comment 14303
Date: 2010-07-09 13:23:29 +0200
From: @grobian
This is not related to the test, but more a bug in mclient which is not showing the warnings produced by the server properly.
JdbcClient just properly logs the connection warning it receives from the server, and it indicates another bug, which is a stray/wrong reference to createdb.sql.
I wasn't aware we actually backported autoloading of sql scripts to Jun2010.
## Comment 14306
Date: 2010-07-09 13:26:16 +0200
From: @grobian
And an additional error is that the warning goes to the client (which has nothing to do with it) and not to the server console.
## Comment 14315
Date: 2010-07-09 14:00:25 +0200
From: @grobian
mapilib doesn't actually deal with warnings at all, it just throws them away it seems, so this isn't easily fixed to have mclient report the warning.
## Comment 14345
Date: 2010-07-09 16:26:49 +0200
From: @grobian
the warning was thrown away from jun2010 branch
## Comment 14347
Date: 2010-07-10 08:03:02 +0200
From: @drstmane
File sql/src/sql/createdb.mx and the attempt to load createdb.sql has been removed from the Jun2010 branch, and hence the warning does not longer appear there.
However, the warning still seems to appear with the default development branch:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_VOC/VOC.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/Int.64.64.d.1-Fedora10/src_test_VOC/VOC.out.00.html
## Comment 14362
Date: 2010-07-12 11:26:58 +0200
From: @grobian
Changeset [05bb5ff91db3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=05bb5ff91db3) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=05bb5ff91db3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=05bb5ff91db3)
Changeset description:
add changelog entry for action taken in comment 4 on bug #2591
## Comment 14363
Date: 2010-07-12 11:35:04 +0200
From: @grobian
the bug should manifest itself now as an error on the server console
## Comment 14611
Date: 2010-08-04 12:20:45 +0200
From: @drstmane
fixed in http://dev.monetdb.org/hg/MonetDB/rev/5277744b7885
by adding <sql_builddir>/src/sql to monet_mod_path
such that (also) `RunMtest` (resp. `make check`)
find createdb.sql before it is installed by `make install`
## Comment 14811
Date: 2010-08-30 09:18:17 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| missing/not-found file: "could not read createdb.sql" | https://api.github.com/repos/MonetDB/MonetDB/issues/2591/comments | 0 | 2020-11-30T11:04:56Z | 2024-06-27T11:48:14Z | https://github.com/MonetDB/MonetDB/issues/2591 | 753,380,579 | 2,591 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 14:52:40 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.1.1 (Mar2011) [obsolete]
CC: @njnes
Last updated: 2011-04-28 16:25:33 +0200
## Comment 14248
Date: 2010-07-07 14:52:40 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
test sql/src/test/BugTracker/Tests/mdb_starts_with_sql_debug_64.SF-1999354.py fails with
"
QUERY = SELECT f2(1,2,3);
ERROR = !ERROR: too many digits (3 > 2)
"
on all platform except Debian and Windows:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/mdb_starts_with_sql_debug_64.SF-1999354.err.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run test yourself
### Actual Results:
test fails, i.e., output differs from approved stable output
### Expected Results:
test should work fine, i.e., output should match approved stable output
I'm not sure whether the fact that Debian and Windows are the only platforms without RDF support installed is related or pure coincidence...
## Comment 14262
Date: 2010-07-07 23:25:26 +0200
From: @drstmane
The other difference between our Debian & Windows machines on the one side and all other machines on the other side is that Debian & Windows are single core (Debian) or run MonetDB on purpose single-threaded (--gdk_nr_threads=1 on Windows).
## Comment 14379
Date: 2010-07-13 14:21:07 +0200
From: @drstmane
The test works fine when running single threaded (`Mtest.py -n1 ...`); hence, the bug might well be related to mitosis/mergetable or dataflow.
## Comment 14464
Date: 2010-07-18 09:40:00 +0200
From: @drstmane
Updated URL is:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/mdb_starts_with_sql_debug_64.SF-1999354.err.00.html
## Comment 14550
Date: 2010-07-28 10:51:04 +0200
From: @drstmane
Since today, i.e., most probably since this fix of bug #2626
http://dev.monetdb.org/hg/MonetDB/rev/2b7eec81b411 ,
the error message does no longer occur:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/mdb_starts_with_sql_debug_64.SF-1999354.err.00.html
However, the output still differs (slightly) between multi-threaded & single-threaded execution:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/mdb_starts_with_sql_debug_64.SF-1999354.out.00.html
## Comment 14835
Date: 2010-08-30 09:23:18 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15071
Date: 2010-10-19 15:49:55 +0200
From: @drstmane
With Jun2010, the multi-threaded output still differs from the single-threaded output; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/mdb_starts_with_sql_debug_64.SF-1999354.out.00.html
With Oct2010, output appears to be as expected on all non-Windows systems (both single- & multi-threaded).
On Windows, the test times out as reported in
http://bugs.monetdb.org/show_bug.cgi?id=2699
## Comment 15674
Date: 2011-03-28 17:36:27 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15704
Date: 2011-03-30 13:02:38 +0200
From: @njnes
has been fixed (combination of fixes in the last weeks).
## Comment 15745
Date: 2011-04-28 16:25:33 +0200
From: @sjoerdmullender
The Apr2011 release has been uploaded.
| test sql/src/test/BugTracker/Tests/mdb_starts_with_sql_debug_64.SF-1999354.py fails with "too many digits" | https://api.github.com/repos/MonetDB/MonetDB/issues/2590/comments | 0 | 2020-11-30T11:04:52Z | 2024-06-27T11:48:13Z | https://github.com/MonetDB/MonetDB/issues/2590 | 753,380,535 | 2,590 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 14:46:31 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.5 (Jun2010-SP2) [obsolete]
CC: colleen
Last updated: 2010-11-15 09:39:03 +0100
## Comment 14247
Date: 2010-07-07 14:46:31 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
At least with JDBC, CREATE TABLE & ALTER TABLE statements don't seem to produce any results sets anymore that trigger the "Operation successful" confirmation; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test/bogus-auto-generated-keys.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugDay_2005-10-06_2.9.3/alter_table_describe.SF-1146092.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_VOC/VOC.out.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run tests yourself
### Actual Results:
At least with JDBC, CREATE TABLE & ALTER TABLE statements don't seem to produce any results sets anymore that trigger the "Operation successful" confirmation.
### Expected Results:
All SQL statements that produce no actual results should produce a "fake" result set to indicate whether the were successful or not.
## Comment 14287
Date: 2010-07-09 12:41:38 +0200
From: @grobian
It looks like a create table with a serial (auto_increment) doesn't say operation successful, while a table without such thing (would it be the constraint perhaps) does.
## Comment 14368
Date: 2010-07-12 15:48:07 +0200
From: @grobian
id serial translates into a multi-statement thing, where the schema update status is being overridden by the statement that follows the create statement. Hence because c->type != Q_SCHEMA, but Q_TABLE no resultset is generated (in the MAL-plan even)
## Comment 14369
Date: 2010-07-12 16:06:33 +0200
From: @grobian
Looked further into it, I think it has to do with all constraint stuff. The serial thing creates a constraint (pkey), all alter table things do "ADD PRIMARY KEY". It is yet unclear to me why they don't set type to Q_SCHEMA though, following the code it seems as if it does end up with setting it to Q_SCHEMA.
## Comment 14394
Date: 2010-07-14 10:28:18 +0200
From: @grobian
this is a behaviour regression
## Comment 14465
Date: 2010-07-18 09:40:48 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test/bogus-auto-generated-keys.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugDay_2005-10-06_2.9.3/alter_table_describe.SF-1146092.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_VOC/VOC.out.00.html
## Comment 14610
Date: 2010-08-04 08:51:33 +0200
From: @drstmane
fixed by Niels:
http://dev.monetdb.org/hg/MonetDB/rev/d874dc671793
Thanks!
## Comment 14821
Date: 2010-08-30 09:18:30 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 14871
Date: 2010-09-02 16:00:01 +0200
From: Colleen Mullin <<colleen>>
Still seeing this with CREATE TABLE ... AS ... WITH DATA
No "operation successful" displays after this type of query in mclient.
From within php, this ends up returning as though the query failed, but it has executed successfully and no error message is returned.
A workaround appears to be creating WITH NO DATA and then doing an INSERT SELECT.
## Comment 14872
Date: 2010-09-02 16:10:02 +0200
From: @drstmane
confirmed:
sql>create table t_0 (a int);
operation successful
sql>create table t_1 as select * from t_0 with data;
sql>
Thanks for reporting!
## Comment 14994
Date: 2010-10-06 12:53:41 +0200
From: @sjoerdmullender
Created attachment 42
proposed patch
The problem is as follows.
The "operation successful" message is triggered by the code "&3" which comes from the server. The server sends this code in the function mvc_export_operation(). This function is called from the MAL statement sql.exportOperation() which is generated in the function backend_dumpstmt().
The problem is that in the case of a CREATE TABLE ... WITH DATA query, the generation of the sql.exportOperation() call is skipped.
This skipping happens when the type of operation is not Q_SCHEMA or Q_TRANS (which are resultset-less operations).
The reason why the type is not Q_SCHEMA (which one would expect) is because during the semantic analysis phase, the server sees that a table is being used, and so it sets the type of the query to Q_TABLE (in function subrel_bin()). At the start of the analysis, the type was still Q_SCHEMA.
Two solutions come to mind:
In subrel_bin() (and possibly other place), when the type is to be set to Q_TABLE, check whether it was Q_SCHEMA, and don't set it when it was.
Or, in output_rel_bin() and rel_bin(), remember the old type, and set it back to Q_SCHEMA if that is what it was before subrel_bin() was called.
I tried the latter approach, and it seems to work fine. This bug is fixed, and no other issues pop up that I saw.
> Attached file: [bug2589.patch](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2589_bug2589.patch_42) (text/plain, 866 bytes)
> Description: proposed patch
## Comment 15010
Date: 2010-10-08 10:03:45 +0200
From: @sjoerdmullender
Changeset [e1f9874ac167](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e1f9874ac167) 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=e1f9874ac167](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e1f9874ac167)
Changeset description:
Fix for bug #2589.
The problem is as follows.
The "operation successful" message is triggered by the code "&3" which comes
from the server. The server sends this code in the function
mvc_export_operation(). This function is called from the MAL statement
sql.exportOperation() which is generated in the function backend_dumpstmt().
The problem is that in the case of a CREATE TABLE ... WITH DATA query, the
generation of the sql.exportOperation() call is skipped.
This skipping happens when the type of operation is not Q_SCHEMA or Q_TRANS
(which are resultset-less operations).
The reason why the type is not Q_SCHEMA (which one would expect) is because
during the semantic analysis phase, the server sees that a table is being used,
and so it sets the type of the query to Q_TABLE (in function subrel_bin()). At
the start of the analysis, the type was still Q_SCHEMA.
We now reset the type to Q_SCHEMA after subrel_bin has done its work
(if that is what the type was, of course).
## Comment 15011
Date: 2010-10-08 10:22:48 +0200
From: @sjoerdmullender
Changeset [969c6a514264](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=969c6a514264) 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=969c6a514264](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=969c6a514264)
Changeset description:
Added test for bug #2589.
| CREATE TABLE & ALTER TABLE no longer produce "Operation successful" | https://api.github.com/repos/MonetDB/MonetDB/issues/2589/comments | 0 | 2020-11-30T11:04:48Z | 2024-06-27T11:48:12Z | https://github.com/MonetDB/MonetDB/issues/2589 | 753,380,489 | 2,589 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 14:39:54 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 11.1.1 (Mar2011) [obsolete]
CC: @njnes
Last updated: 2011-04-28 16:25:37 +0200
## Comment 14246
Date: 2010-07-07 14:39:54 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
test sql/src/test/BugTracker/Tests/authorization.SF-1430616.SQL.sh shows different error message than it used to show:
was:
"
Error on line 7: COMMIT: failed
ERROR: COMMIT: transaction is aborted, will ROLLBACK instead
"
is:
"
Error on line 7: SQLException:sql.trans:COMMIT: failed
"
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/authorization.SF-1430616.err.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run test yourself
### Actual Results:
test fails, i.e., output differs from approved stable output
### Expected Results:
test should work fine, i.e., output should match approved stable output
I'm not sure whether the change in the error message was intended.
If so, the new stable output merely needs to be approved.
## Comment 14466
Date: 2010-07-18 09:41:39 +0200
From: @drstmane
Updated URL is:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/authorization.SF-1430616.err.00.html
## Comment 14840
Date: 2010-08-30 09:23:20 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15680
Date: 2011-03-28 17:36:30 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15703
Date: 2011-03-30 13:01:05 +0200
From: @njnes
changes have been (solved and) approved, ie closing
## Comment 15751
Date: 2011-04-28 16:25:37 +0200
From: @sjoerdmullender
The Apr2011 release has been uploaded.
| test sql/src/test/BugTracker/Tests/authorization.SF-1430616.SQL.sh shows different error message | https://api.github.com/repos/MonetDB/MonetDB/issues/2588/comments | 0 | 2020-11-30T11:04:45Z | 2024-06-27T11:48:11Z | https://github.com/MonetDB/MonetDB/issues/2588 | 753,380,451 | 2,588 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 14:34:41 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.5 (Jun2010-SP2) [obsolete]
Last updated: 2010-11-15 09:38:58 +0100
## Comment 14245
Date: 2010-07-07 14:34:41 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
tests
sql/src/test/BugDay_2005-11-09_2.9.3/Tests/hang_on_copy_into.SF-1100504.sql & sql/src/test/BugTracker/Tests/mapi_connect_errors_vanish.SF-1432134.SQL.sh
no longer show the error messages they used to show; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugDay_2005-11-09_2.9.3/hang_on_copy_into.SF-1100504.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/mapi_connect_errors_vanish.SF-1432134.err.00.html
Reproducible: Always
### Steps to Reproduce:
see nightly testing results
or
run tests yourself
### Actual Results:
tests fail, i.e., output differs from approved stable output
### Expected Results:
test shoudl work, i.e., output should match approved stable output
I'm not sure, whether the errors should still occur or not.
If yes, the code needs to be fixed.
If not, the stable output need to be fixed.
## Comment 14467
Date: 2010-07-18 09:42:43 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugDay_2005-11-09_2.9.3/hang_on_copy_into.SF-1100504.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker/mapi_connect_errors_vanish.SF-1432134.err.00.html
## Comment 14837
Date: 2010-08-30 09:23:19 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15064
Date: 2010-10-18 19:52:43 +0200
From: @drstmane
Both tests appear to work fine, again, since Sep 18 2010 in Jun2010, Oct2010 & default.
| tests no longer show the error messages they used to show | https://api.github.com/repos/MonetDB/MonetDB/issues/2587/comments | 0 | 2020-11-30T11:04:42Z | 2024-06-27T11:48:10Z | https://github.com/MonetDB/MonetDB/issues/2587 | 753,380,418 | 2,587 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 13:05:55 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 2.40.1 (Oct2010) [obsolete]
CC: @njnes, @drstmane
Last updated: 2011-03-28 17:31:40 +0200
## Comment 14242
Date: 2010-07-07 13:05:55 +0200
From: @grobian
execute the contents of times.sql:
create procedure times()
external name sql.times;
then issue the following query:
select times();
the server will segfault with:
rogram received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff6eff7710 (LWP 8725)]
0x00007fffdead4881 in _dumpstmt (sql=0x7fff48efa528, mb=0x7fff491c23d8,
s=0x7fff482f7e18)
at /ufs/fabian/scratch/monetdb/Jun2010/sql/src/backends/monet5/sql_gencode.mx:1746
1746 q = pushStr(mb, q, t->type->sqlname);
(gdb) p mb
$1 = (MalBlkPtr) 0x7fff491c23d8
(gdb) p q
$2 = (InstrPtr) 0x7fff4a625188
(gdb) p t->type->sqlname
Cannot access memory at address 0x18
(gdb) p t->type
$3 = (sql_type *) 0x0
(gdb) p t
$4 = (sql_subtype *) 0x7fff48678b68
(gdb)
## Comment 14243
Date: 2010-07-07 13:07:15 +0200
From: @grobian
it seems to be any function that is called like this, not just times().
## Comment 14603
Date: 2010-08-02 16:42:06 +0200
From: @drstmane
here's a quick gdb log (with Jun2010 branch as of today, Mon Aug 02 2010):
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffdf496710 (LWP 18709)]
0x00007fffe02d7853 in _dumpstmt (sql=0x7fffd004abf8, mb=0x7fffd0065b58, s=0x7fffd006e1d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql_gencode.mx:1746
1746 q = pushStr(mb, q, t->type->sqlname);
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-6.fc12.x86_64 cyrus-sasl-lib-2.1.23-9.fc12.x86_64 geos-3.2.1-1.fc12.x86_64 glibc-2.11.2-1.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-7.fc12.x86_64 libcurl-7.19.7-10.fc12.x86_64 libgcc-4.4.4-10.fc12.x86_64 libidn-1.9-5.x86_64 libselinux-2.0.90-5.fc12.x86_64 libssh2-1.2.4-1.fc12.x86_64 libstdc++-4.4.4-10.fc12.x86_64 libuuid-2.16.2-9.fc12.x86_64 libxml2-2.7.6-2.fc12.x86_64 libxslt-1.1.26-1.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64 nspr-4.8.4-2.fc12.x86_64 nss-3.12.6-7.fc12.x86_64 nss-softokn-freebl-3.12.6-2.fc12.1.x86_64 nss-util-3.12.6-1.fc12.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0a-1.fc12.x86_64 pcre-7.8-3.fc12.x86_64 raptor-1.4.18-5.fc12.x86_64 readline-6.0-3.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) bt
0 0x00007fffe02d7853 in _dumpstmt (sql=0x7fffd004abf8, mb=0x7fffd0065b58, s=0x7fffd006e1d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql_gencode.mx:1746
1 0x00007fffe02d89a2 in backend_dumpstmt (be=0x7fffd004abf8, mb=0x7fffd0065b58, s=0x7fffd006e1d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql_gencode.mx:2010
2 0x00007fffe02d91be in backend_dumpproc (be=0x7fffd004abf8, c=0x605b38, cq=0x7fffd0065c58, s=0x7fffd006e1d8) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql_gencode.mx:2131
3 0x00007fffe02cea11 in SQLparser (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/sql/src/backends/monet5/sql_scenario.mx:1210
4 0x00007ffff7d223fa in runPhase (c=0x605b38, phase=1) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:604
5 0x00007ffff7d22532 in runScenarioBody (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:646
6 0x00007ffff7d227b9 in runScenario (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:682
7 0x00007ffff7cd5ef9 in MSserveClient (dummy=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Jun2010/source/MonetDB5/src/mal/mal_session.mx:473
8 0x000000347c406a3a in start_thread () from /lib64/libpthread.so.0
9 0x000000347b8de77d in clone () from /lib64/libc.so.6
10 0x0000000000000000 in ?? ()
(gdb) li
1741 q = newStmt2(mb, sqlRef, exportValueRef);
1742 s->nr = getDestVar(q);
1743 q = pushInt(mb, q, sql->mvc->type);
1744 q = pushStr(mb, q, fqtn);
1745 q = pushStr(mb, q, cn);
1746 q = pushStr(mb, q, t->type->sqlname);
1747 q = pushInt(mb, q, t->digits);
1748 q = pushInt(mb, q, t->scale);
1749 q = pushInt(mb, q, t->type->eclass);
1750 q = pushArgument(mb, q, c->nr);
(gdb) p mb
$1 = (MalBlkPtr) 0x7fffd0065b58
(gdb) p *mb
$2 = {binding = 0x0, help = 0x0, alternative = 0x0, vtop = 8, vsize = 32, var = 0x7fffd00584e8, stop = 4, ssize = 32, stmt = 0x7fffd008b808, ptop = 1, psize = 32, prps = 0x7fffd007a6e8, errors = 0, typefixed = 0, flowfixed = 0, profiler = 0x0, history = 0x0, keephistory = 0, marker = 0x0, maxarg = 8,
replica = 0x0, recycle = 0, recid = 0, octid = -2604246222170760229, trap = 0}
(gdb) p q
$3 = (InstrPtr) 0x7fffd0066c68
(gdb) p *q
$4 = {token = 40 '(', barrier = 0 '\000', typechk = 0 '\000', gc = 0 '\000', polymorphic = 0 '\000', varargs = 0 '\000', recycle = 0, jump = 0, fcn = 0, blk = 0x0, modname = 0xb48e58 "sql", fcnname = 0xf33568 "exportValue", argc = 4, retc = 1, maxarg = 8, argv = 0x7fffd0066ca4}
(gdb) p t
$5 = (sql_subtype *) 0x7fffd00798d8
(gdb) p *t
$6 = {type = 0x0, digits = 0, scale = 0, comp_type = 0x0}
(gdb) p t->type
$7 = (sql_type *) 0x0
(gdb) p *t->type
Cannot access memory at address 0x0
## Comment 14843
Date: 2010-08-30 09:23:20 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15001
Date: 2010-10-06 15:49:19 +0200
From: @sjoerdmullender
Changeset [0b75646be89a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0b75646be89a) 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=0b75646be89a](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0b75646be89a)
Changeset description:
Added test for bug #2586.
## Comment 15066
Date: 2010-10-19 09:13:37 +0200
From: @njnes
Changeset [333e14ad51c7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=333e14ad51c7) 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=333e14ad51c7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=333e14ad51c7)
Changeset description:
fixes bugs in limit (don't push topn under project, is handled in rel_bin
allready) Bug #2622 and Bug #2676
fix crash in Bug #2672 , ie complex between is now handled correctly
fix bug #2586, test for return types when using functions.
(and check for empty results on procedure calls)
## Comment 15261
Date: 2010-12-03 21:38:22 +0100
From: @njnes
fixed. ie closing.
## Comment 15648
Date: 2011-03-28 17:31:40 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
| times.sql: procedure times() crashes the server | https://api.github.com/repos/MonetDB/MonetDB/issues/2586/comments | 0 | 2020-11-30T11:04:39Z | 2024-06-27T11:48:09Z | https://github.com/MonetDB/MonetDB/issues/2586 | 753,380,386 | 2,586 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 13:02:14 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.1 (Jun2010) [obsolete]
Last updated: 2010-08-20 14:04:05 +0200
## Comment 14241
Date: 2010-07-07 13:02:14 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
test MonetDB5/src/modules/mal/Tests/remote10.mal fails on all platforms with
"!MALException:remote.register:function already exists at the remote site: octopus.qry"
cf., e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora12/src_modules_mal/remote10.out.00.html
Reproducible: Always
### Steps to Reproduce:
by nightly testing
or
run test MonetDB5/src/modules/mal/Tests/remote10.mal
### Actual Results:
test fails and test output differs from stable one
### Expected Results:
test should work fine, i.e., its output should match the approved stable output
## Comment 14280
Date: 2010-07-09 11:40:33 +0200
From: @grobian
url doesn't work.
The test was reenabled and changed by martin in changeset [a59ae8ba7b3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a59ae8ba7b3f) (Testing single partition fetching. Addition of remote function registration request.)
The test cannot possibly work this way, since we connect to ourself, and hence the function (which is put in the octopus module scope) always already exists (it's the original which we try to register again on ourself).
## Comment 14281
Date: 2010-07-09 11:43:09 +0200
From: @grobian
Changeset [cbf0ebe0f2d6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=cbf0ebe0f2d6) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cbf0ebe0f2d6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cbf0ebe0f2d6)
Changeset description:
Change remote10 test such that it uses 'user' scope, and hence doesn't conflict per definition, solves bug #2585
## Comment 14286
Date: 2010-07-09 12:38:42 +0200
From: @drstmane
For the records (applies likewise to other bug reports about failing tests):
URL temp. doesn't work as compilation (and hence testing) on that platform failed tonight; will be back tomorrow; till then use alternative URL to other platform (e.g., Fedora10 instead of Fedora12)
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora10/src_modules_mal/remote10.out.00.html
or top-level entry point to MonetDB5 testing results:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/index_short.html
| test MonetDB5/src/modules/mal/Tests/remote10.mal fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2585/comments | 0 | 2020-11-30T11:04:36Z | 2024-06-27T11:48:08Z | https://github.com/MonetDB/MonetDB/issues/2585 | 753,380,359 | 2,585 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 12:58:51 +0200
From: @drstmane
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.5 (Jun2010-SP2) [obsolete]
Last updated: 2010-11-15 09:38:57 +0100
## Comment 14240
Date: 2010-07-07 12:58:51 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
With test MonetDB5/src/mal/Tests/pithole.mal the exception
"!MALException:mal.interpreter:Running out of stack space."
fails to show on Windows; cf., e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_mal/pithole.out.00.html
It is not clear to me, yet, whether the exception is not raised at all or whether it merely does not reach its output destination.
In fact, it is not clear to me whether the exception needs to be raised at all in this case on Windows, i.e., whether the condition to raise the exception is fulfilled.
Reproducible: Always
### Steps to Reproduce:
by nightly testing
or
run test MonetDB5/src/mal/Tests/pithole.mal on Windows
### Actual Results:
Test output on Windows differs from given stable output and (hence) from output on all other tested platforms
### Expected Results:
In case the condition for raising this exception is (also) fulfilled on Windows, (1) the exception needs to be raised (also) on Windows, and (2) this must be reflected in the outout.
In case the condition for raising this exception is NOT fulfilled on Windows, (a) either the test needs to be changed to trigger the exception also on Windows, or (b) Windows-specific stable output without the exceptions needs to be approved.
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Int.64.32.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Int.64.64.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Mic.32.32.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Mic.64.32.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/MonetDB5/.mTests103/Mic.64.64.d.1-Windows6.0/src_mal/pithole.out.00.html
## Comment 14468
Date: 2010-07-18 09:43:57 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.32.32.d.1-Windows5.1/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.32.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.64.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Mic.32.32.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Mic.64.32.d.1-Windows6.0/src_mal/pithole.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Mic.64.64.d.1-Windows6.0/src_mal/pithole.out.00.html
## Comment 14852
Date: 2010-08-30 09:24:16 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15007
Date: 2010-10-07 14:04:00 +0200
From: @sjoerdmullender
This seems to be working.
| test MonetDB5/src/mal/Tests/pithole.mal fails to show exception on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2584/comments | 0 | 2020-11-30T11:04:33Z | 2024-06-27T11:48:07Z | https://github.com/MonetDB/MonetDB/issues/2584 | 753,380,323 | 2,584 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-07 00:19:03 +0200
From: Mark Bucciarelli <<mkbucc>>
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: mkbucc, @njnes, @drstmane
Last updated: 2010-08-20 14:03:53 +0200
## Comment 14231
Date: 2010-07-07 00:19:03 +0200
From: Mark Bucciarelli <<mkbucc>>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6
Build Identifier:
CREATE TABLE "test"."tbl1" (
"id" int NOT NULL,
"id1" int NOT NULL,
"id2" int NOT NULL,
"name" varchar(300) NOT NULL,
CONSTRAINT "test_id_pkey" PRIMARY KEY ("id"),
CONSTRAINT "test_id1_name_unique" UNIQUE ("id1", "name")
);
SELECT
(1) AS "a"
FROM
"test"."tbl1"
WHERE
"tbl1"."name" = 'some text' AND
"tbl1"."id1" = 1 AND NOT
("tbl1"."id2" = 295)
;
DROP TABLE "test"."tbl1";
Reproducible: Always
### Steps to Reproduce:
1. create a database called test
2. save SQL pasted above to file.
3. run sql with mclient; e.g., mclient -l sql -d test -u test t.sql
### Actual Results:
$ mclient -u test -l sql -d test t.sql
password:
MAPI = test@localhost:50000
ACTION= read_line
QUERY = CREATE TABLE "test"."tbl1" (
"id" int NOT NULL,
"id1" int NOT NULL,
"id2" int NOT NULL,
"name" varchar(300) NOT NULL,
CONSTRAINT "test_id_pkey" PRIMARY KEY ("id"),
CONSTRAINT "test_id1_name_unique" UNIQUE ("id1", "name")
);
SELECT
(1) AS "a"
FROM
"test"."tbl1"
WHERE
"tbl1"."name" = 'some text' AND
"tbl1"."id1" = 1 AND NOT
("tbl1"."id2" = 295)
;
DROP TABLE "test"."tbl1";
ERROR = !Connection terminated
### Expected Results:
$ mclient -u test -l sql -d test t.sql
password:
% . table_name
% a name
% tinyint type
% 1 length
$
If you remove the constraint "test_id1_name_unique", you get the expected results.
## Comment 14232
Date: 2010-07-07 00:43:35 +0200
From: @drstmane
[After prefixing the given SQL sample with
`CREATE SCHEMA test;`]
the problem is reproducible with the latest code bases from the Feb2010, Jun2010 & default branches.
Here's a first gdb log (with Jun2010):
$ gdb --args mserver5 --dbname=err
GNU gdb (GDB) Fedora (7.0.1-48.fc12)
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /.../Jun2010/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/bin/mserver5...done.
(gdb) r
Starting program: /.../Jun2010/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/bin/mserver5 --dbname=err
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffea65b710 (LWP 20192)]
MonetDB server v5.20.2, based on kernel v1.38.2
Serving database 'err', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 7.751 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /.../Jun2010/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/etc/monetdb5.conf)
[New Thread 0x7fffdf89c710 (LWP 21178)]
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.38.3 loaded
[New Thread 0x7fffdf69b710 (LWP 21185)]
MonetDB/GIS module v0.18.1 loaded
>[New Thread 0x7fffdf49a710 (LWP 23823)]
mserver5: /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3163: find_index: Assertion `list_length(exps) == list_length(es)' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffdf49a710 (LWP 23823)]
0x000000347b8326c5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-6.fc12.x86_64 cyrus-sasl-lib-2.1.23-9.fc12.x86_64 geos-3.2.1-1.fc12.x86_64 glibc-2.11.2-1.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-7.fc12.x86_64 libcurl-7.19.7-10.fc12.x86_64 libgcc-4.4.3-4.fc12.x86_64 libidn-1.9-5.x86_64 libselinux-2.0.90-5.fc12.x86_64 libssh2-1.2.4-1.fc12.x86_64 libstdc++-4.4.3-4.fc12.x86_64 libuuid-2.16.2-9.fc12.x86_64 libxml2-2.7.6-2.fc12.x86_64 libxslt-1.1.26-1.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64 nspr-4.8.4-2.fc12.x86_64 nss-3.12.6-7.fc12.x86_64 nss-softokn-freebl-3.12.6-2.fc12.1.x86_64 nss-util-3.12.6-1.fc12.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0a-1.fc12.x86_64 pcre-7.8-3.fc12.x86_64 raptor-1.4.18-5.fc12.x86_64 readline-6.0-3.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) bt
0 0x000000347b8326c5 in raise () from /lib64/libc.so.6
1 0x000000347b833ea5 in abort () from /lib64/libc.so.6
2 0x000000347b82b7b5 in __assert_fail () from /lib64/libc.so.6
3 0x00007fffe0348d1d in find_index (r=0x7fffd0141258, EXPS=0x7fffdf499ab0) at /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3163
4 0x00007fffe0348de8 in rel_select_use_index (changes=0x7fffdf499b2c, sql=0x7fffd0105758, rel=0x7fffd0141258) at /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3186
5 0x00007fffe0349cf7 in rewrite (sql=0x7fffd0105758, rel=0x7fffd0141258, rewriter=0x7fffe0348d9e <rel_select_use_index>) at /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3503
6 0x00007fffe0349c3a in rewrite (sql=0x7fffd0105758, rel=0x7fffd0142108, rewriter=0x7fffe0348d9e <rel_select_use_index>) at /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3488
7 0x00007fffe034a0ab in rel_optimizer (sql=0x7fffd0105758, rel=0x7fffd0142108) at /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3599
8 0x00007fffe02864af in sql_symbol2stmt (c=0x7fffd0105758, sym=0x7fffd0108578) at /.../Jun2010/source/sql/src/backends/monet5/sql.mx:1350
9 0x00007fffe02d27a2 in SQLparser (c=0x605b38) at /.../Jun2010/source/sql/src/backends/monet5/sql_scenario.mx:1203
10 0x00007ffff7d22c92 in runPhase (c=0x605b38, phase=1) at /.../Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:604
11 0x00007ffff7d22dca in runScenarioBody (c=0x605b38) at /.../Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:646
12 0x00007ffff7d23051 in runScenario (c=0x605b38) at /.../Jun2010/source/MonetDB5/src/mal/mal_scenario.mx:682
13 0x00007ffff7cd6f0d in MSserveClient (dummy=0x605b38) at /.../Jun2010/source/MonetDB5/src/mal/mal_session.mx:473
14 0x000000347c406a3a in start_thread () from /lib64/libpthread.so.0
15 0x000000347b8de77d in clone () from /lib64/libc.so.6
16 0x0000000000000000 in ?? ()
(gdb) up
1 0x000000347b833ea5 in abort () from /lib64/libc.so.6
(gdb)
2 0x000000347b82b7b5 in __assert_fail () from /lib64/libc.so.6
(gdb)
3 0x00007fffe0348d1d in find_index (r=0x7fffd0141258, EXPS=0x7fffdf499ab0) at /.../Jun2010/source/sql/src/server/rel_optimizer.mx:3163
3163 assert(list_length(exps) == list_length(es));
(gdb) li
3158 list_append(es, exp_dup(e) );
3159 break;
3160 }
3161 }
3162 }
3163 assert(list_length(exps) == list_length(es));
3164 /* fix the destroy function */
3165 cols->destroy = NULL;
3166 list_destroy(cols);
3167 list_destroy(exps);
(gdb) p exps
$1 = (list *) 0x7fffd01412a8
(gdb) p *exps
$2 = {sa = 0x0, destroy = 0x7fffe033c991 <exp_destroy>, h = 0x7fffd014a428, t = 0x7fffd01412e8, cnt = 3}
(gdb) p es
$3 = (list *) 0x7fffd0140bb8
(gdb) p *es
$4 = {sa = 0x0, destroy = 0x7fffe033c991 <exp_destroy>, h = 0x7fffd0142418, t = 0x7fffd0142448, cnt = 2}
(gdb) p list_length(exps)
$5 = 3
(gdb) p list_length(es)
$6 = 2
(gdb)
## Comment 14235
Date: 2010-07-07 09:17:15 +0200
From: @njnes
fixed by removing the incorrect assert. Test added to BugTracker-2010
## Comment 14236
Date: 2010-07-07 09:20:46 +0200
From: @njnes
Changeset [a0d12c135b17](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a0d12c135b17) 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=a0d12c135b17](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a0d12c135b17)
Changeset description:
Fixed bug #2583
The keys can match a smaller set out of the expression list. Thats fine,
ie the assert was incorrect.
| SQL crashes database reliably. | https://api.github.com/repos/MonetDB/MonetDB/issues/2583/comments | 0 | 2020-11-30T11:04:30Z | 2024-06-27T11:48:06Z | https://github.com/MonetDB/MonetDB/issues/2583 | 753,380,280 | 2,583 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-06 17:17:48 +0200
From: @njnes
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
Last updated: 2010-08-20 14:03:58 +0200
## Comment 14228
Date: 2010-07-06 17:17:48 +0200
From: @njnes
sql>create table skycrash(id serial, boom boolean);
sql>create view skyview as select 1 as unknown, id from skycrash;
operation successful
sql>select * from skyview where unknown in (1, 2, 3);
TypeException:user.s0_1[14]:'algebra.leftjoin' undefined in: _21:any := algebra.leftjoin(_6:bte, _20:bat[:bte,:oid])
TypeException:user.s0_1[15]:'algebra.project' undefined in: _22:any := algebra.project(_21:any)
TypeException:user.s0_1[17]:'algebra.markT' undefined in: _25:any := algebra.markT(_22:any, _23:oid)
TypeException:user.s0_1[18]:'bat.reverse' undefined in: _26:any := bat.reverse(_25:any)
TypeException:user.s0_1[28]:'algebra.leftjoin' undefined in: _42:any := algebra.leftjoin(_26:any, _41:bat[:oid,:int])
TypeException:user.s0_1[30]:'algebra.project' undefined in: _45:any := algebra.project(_42:any, _43:bte)
SQLException:SQLengine:Program contains errors
sql>
## Comment 14237
Date: 2010-07-07 09:26:23 +0200
From: @njnes
added test in_query_with_constants_fails.Bug-2582.sql
The optimization for in expressions shouldn't kick in for constants, ie constant in constant_set. We now protect against this case.
| incorrect plan on in-query on view with constant | https://api.github.com/repos/MonetDB/MonetDB/issues/2582/comments | 0 | 2020-11-30T11:04:27Z | 2024-06-27T11:48:05Z | https://github.com/MonetDB/MonetDB/issues/2582 | 753,380,237 | 2,582 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T10:59:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/2581/comments | 0 | 2020-11-30T11:04:24Z | 2020-11-30T11:04:26Z | https://github.com/MonetDB/MonetDB/issues/2581 | 753,380,210 | 2,581 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-05 15:12:53 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @njnes
Last updated: 2010-08-20 14:04:06 +0200
## Comment 14217
Date: 2010-07-05 15:12:53 +0200
From: @yzchang
The problem happens in both Jun2010 (updated yesterday evening) and current(updated this morning) on a CWI desktop machine.
sql>create table a (x int, y int);
operation successful
Timer 1.843 msec 9 rows
sql>insert into a values (1,1),(1,2), (1,3),(2,1),(2,2),(2,3),(1,2),(2,1),(2,3);
9 affected rows
Timer 9.620 msec 9 rows
sql>select * from (select 1 as id , count(*) as cnt from (select distinct x,y from a) as b) as b2 join (select 1 as id , count(*) as cnt2 from a) as a2 on b2.id = a2.id;
TypeException:user.s1_1[6]:'bat.mirror' undefined in: _11:any := bat.mirror(_5:bte)
TypeException:user.s1_1[8]:'algebra.join' undefined in: _13:any := algebra.join(_11:any, _12:bat[:oid,:oid])
TypeException:user.s1_1[9]:'algebra.markH' undefined in: _14:any := algebra.markH(_13:any, _15:oid)
TypeException:user.s1_1[10]:'algebra.markT' undefined in: _16:any := algebra.markT(_13:any, _15:oid)
TypeException:user.s1_1[11]:'bat.reverse' undefined in: _17:any := bat.reverse(_16:any)
TypeException:user.s1_1[12]:'algebra.join' undefined in: _18:any := algebra.join(_17:any, _5:bte)
TypeException:user.s1_1[13]:'algebra.join' undefined in: _19:any := algebra.join(_14:any, _10:bat[:oid,:bte])
TypeException:user.s1_1[17]:'algebra.join' undefined in: _25:any := algebra.join(_24:bat[:void,:oid], _14:any)
TypeException:user.s1_1[18]:'bat.reverse' undefined in: _26:any := bat.reverse(_25:any)
TypeException:user.s1_1[19]:'bat.reverse' undefined in: _27:any := bat.reverse(_26:any)
TypeException:user.s1_1[21]:'algebra.markT' undefined in: _29:any := algebra.markT(_27:any, _28:oid)
TypeException:user.s1_1[22]:'bat.reverse' undefined in: _30:any := bat.reverse(_29:any)
TypeException:user.s1_1[25]:'algebra.leftjoin' undefined in: _33:any := algebra.leftjoin(_30:any, _32:bat[:oid,:bte])
TypeException:user.s1_1[53]:'algebra.leftjoin' undefined in: _73:any := algebra.leftjoin(_30:any, _71:bat[:oid,:wrd])
TypeException:user.s1_1[54]:'bat.mirror' undefined in: _74:any := bat.mirror(_5:bte)
TypeException:user.s1_1[56]:'algebra.join' undefined in: _76:any := algebra.join(_74:any, _75:bat[:oid,:oid])
TypeException:user.s1_1[57]:'algebra.markH' undefined in: _77:any := algebra.markH(_76:any, _78:oid)
TypeException:user.s1_1[58]:'algebra.markT' undefined in: _79:any := algebra.markT(_76:any, _78:oid)
TypeException:user.s1_1[59]:'bat.reverse' undefined in: _80:any := bat.reverse(_79:any)
TypeException:user.s1_1[60]:'algebra.join' undefined in: _81:any := algebra.join(_80:any, _5:bte)
TypeException:user.s1_1[61]:'algebra.join' undefined in: _82:any := algebra.join(_77:any, _10:bat[:oid,:bte])
TypeException:user.s1_1[65]:'algebra.join' undefined in: _88:any := algebra.join(_87:bat[:void,:oid], _77:any)
TypeException:user.s1_1[66]:'bat.reverse' undefined in: _89:any := bat.reverse(_88:any)
TypeException:user.s1_1[68]:'algebra.markT' undefined in: _91:any := algebra.markT(_89:any, _90:oid)
TypeException:user.s1_1[69]:'bat.reverse' undefined in: _92:any := bat.reverse(_91:any)
TypeException:user.s1_1[70]:'algebra.leftjoin' undefined in: _93:any := algebra.leftjoin(_92:any, _10:bat[:oid,:bte])
TypeException:user.s1_1[83]:'algebra.leftjoin' undefined in: _115:any := algebra.leftjoin(_92:any, _113:bat[:oid,:wrd])
SQLException:SQLengine:Program contains errors
Timer 2.007 msec 1 rows
sql>select * from (select 1 as id , count(*) as cnt from (select distinct x,y from a) as b) as b2, (select 1 as id , count(*) as cnt2 from a) as a2 where b2.id = a2.id;
TypeException:user.s0_1[6]:'bat.mirror' undefined in: _11:any := bat.mirror(_5:bte)
TypeException:user.s0_1[8]:'algebra.join' undefined in: _13:any := algebra.join(_11:any, _12:bat[:oid,:oid])
TypeException:user.s0_1[9]:'algebra.markH' undefined in: _14:any := algebra.markH(_13:any, _15:oid)
TypeException:user.s0_1[10]:'algebra.markT' undefined in: _16:any := algebra.markT(_13:any, _15:oid)
TypeException:user.s0_1[11]:'bat.reverse' undefined in: _17:any := bat.reverse(_16:any)
TypeException:user.s0_1[12]:'algebra.join' undefined in: _18:any := algebra.join(_17:any, _5:bte)
TypeException:user.s0_1[13]:'algebra.join' undefined in: _19:any := algebra.join(_14:any, _10:bat[:oid,:bte])
TypeException:user.s0_1[17]:'algebra.join' undefined in: _25:any := algebra.join(_24:bat[:void,:oid], _14:any)
TypeException:user.s0_1[18]:'bat.reverse' undefined in: _26:any := bat.reverse(_25:any)
TypeException:user.s0_1[19]:'bat.reverse' undefined in: _27:any := bat.reverse(_26:any)
TypeException:user.s0_1[21]:'algebra.markT' undefined in: _29:any := algebra.markT(_27:any, _28:oid)
TypeException:user.s0_1[22]:'bat.reverse' undefined in: _30:any := bat.reverse(_29:any)
TypeException:user.s0_1[25]:'algebra.leftjoin' undefined in: _33:any := algebra.leftjoin(_30:any, _32:bat[:oid,:bte])
TypeException:user.s0_1[53]:'algebra.leftjoin' undefined in: _73:any := algebra.leftjoin(_30:any, _71:bat[:oid,:wrd])
TypeException:user.s0_1[54]:'bat.mirror' undefined in: _74:any := bat.mirror(_5:bte)
TypeException:user.s0_1[56]:'algebra.join' undefined in: _76:any := algebra.join(_74:any, _75:bat[:oid,:oid])
TypeException:user.s0_1[57]:'algebra.markH' undefined in: _77:any := algebra.markH(_76:any, _78:oid)
TypeException:user.s0_1[58]:'algebra.markT' undefined in: _79:any := algebra.markT(_76:any, _78:oid)
TypeException:user.s0_1[59]:'bat.reverse' undefined in: _80:any := bat.reverse(_79:any)
TypeException:user.s0_1[60]:'algebra.join' undefined in: _81:any := algebra.join(_80:any, _5:bte)
TypeException:user.s0_1[61]:'algebra.join' undefined in: _82:any := algebra.join(_77:any, _10:bat[:oid,:bte])
TypeException:user.s0_1[65]:'algebra.join' undefined in: _88:any := algebra.join(_87:bat[:void,:oid], _77:any)
TypeException:user.s0_1[66]:'bat.reverse' undefined in: _89:any := bat.reverse(_88:any)
TypeException:user.s0_1[68]:'algebra.markT' undefined in: _91:any := algebra.markT(_89:any, _90:oid)
TypeException:user.s0_1[69]:'bat.reverse' undefined in: _92:any := bat.reverse(_91:any)
TypeException:user.s0_1[70]:'algebra.leftjoin' undefined in: _93:any := algebra.leftjoin(_92:any, _10:bat[:oid,:bte])
TypeException:user.s0_1[83]:'algebra.leftjoin' undefined in: _115:any := algebra.leftjoin(_92:any, _113:bat[:oid,:wrd])
SQLException:SQLengine:Program contains errors
Timer 1.759 msec 9 rows
It seems that the problem is caused by the join condition, since:
sql>select * from (select 1 as id , count(*) as cnt from (select distinct x,y from a) as b) as b2, (select 1 as id , count(*) as cnt2 from a) as a2;
+------+------+------+------+
| id | cnt | id | cnt2 |
+======+======+======+======+
| 1 | 6 | 1 | 9 |
+------+------+------+------+
1 tuple
Timer 8.443 msec 1 rows
Jennie
## Comment 14230
Date: 2010-07-06 17:58:38 +0200
From: @drstmane
Changeset [75fb1faa9477](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=75fb1faa9477) 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=75fb1faa9477](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=75fb1faa9477)
Changeset description:
merged with Jennie's new tests from Jun2010:
"
Added tests for bugs 2579 and 2580
bug #2579 is nog fixed yet.
bug #2580 is fixed by Niels' yesterday's check-in.
"
| SQL: exec query with join condition results in "SQLException:SQLengine:Program contains errors" | https://api.github.com/repos/MonetDB/MonetDB/issues/2580/comments | 0 | 2020-11-30T11:04:21Z | 2024-06-27T11:48:04Z | https://github.com/MonetDB/MonetDB/issues/2580 | 753,380,171 | 2,580 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-05 11:08:47 +0200
From: @yzchang
To: SQL devs <<bugs-sql>>
Version: 11.11.7 (Jul2012-SP1)
CC: @romulogoncalves, @njnes, simon.brodt, @drstmane
Last updated: 2013-01-22 09:29:09 +0100
## Comment 14215
Date: 2010-07-05 11:08:47 +0200
From: @yzchang
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
In the following query, the simple/small doubles are incorrectly cast to integers:
sql>select 1.0/2.0;
+----------------------+
| sql_div_single_value |
+======================+
| 0 |
+----------------------+
1 tuple
Timer 0.431 msec 1 rows
I can only get the expected result using a cast:
sql>select cast (1 as double)/2;
+------------------------+
| sql_div_single_value |
+========================+
| 0.5 |
+------------------------+
1 tuple
Timer 0.324 msec 1 rows
Reproducible: Always
## Comment 14216
Date: 2010-07-05 11:16:38 +0200
From: @drstmane
there is IMHO no cast from double to int;
rather, both 1.0 & 2.0 are parsed as decimal and "optimized" to 0 digits, and the div keeps the 0 digits; cf.,
sql>\fraw
sql>select 1.0/2.0;
% . table_name
% sql_div_single_value name
% decimal type
% 3 length
[ 0 ]
sql>select 1.0/2.1;
% . table_name
% sql_div_single_value name
% decimal type
% 7 length
[ 0.476 ]
sql>select 1.1/2.1;
% . table_name
% sql_div_single_value name
% decimal type
% 7 length
[ 0.523 ]
sql>select 1.1/2.0;
% . table_name
% sql_div_single_value name
% decimal type
% 4 length
[ 0.5 ]
I cannot tell what SQL semantics require in such cases (if at all)
## Comment 14229
Date: 2010-07-06 17:58:38 +0200
From: @drstmane
Changeset [75fb1faa9477](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=75fb1faa9477) 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=75fb1faa9477](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=75fb1faa9477)
Changeset description:
merged with Jennie's new tests from Jun2010:
"
Added tests for bugs 2579 and 2580
bug #2579 is nog fixed yet.
bug #2580 is fixed by Niels' yesterday's check-in.
"
## Comment 14842
Date: 2010-08-30 09:23:20 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 14944
Date: 2010-09-28 11:46:29 +0200
From: @sjoerdmullender
Looking at the code that is produced (plan, explain, debug), I noticed that the values 1.0 and 2.0 lost the ".0" very early on (i.e., they didn't occur in the code at all). Looking at the parser and scanner, I noticed that the parser strips trailing zeroes from numbers with decimal points, so the information that we were dealing with a decimal is lost there.
If I change the code in the parser to not strip those zeroes, the result of the query becomes
sql>select 1.0/2.0;
+----------------------+
| sql_div_single_value |
+======================+
| 0.500 |
+----------------------+
1 tuple (1.073ms)
The patch is simply to replace the call strip_extra_zeros(sa_strdup(SA, $1)) with sa_strdup(SA, $1) in the section dealing with INTNUM.
Unfortunately, this change causes a bunch of other tests to fail.
## Comment 15684
Date: 2011-03-28 17:36:31 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15988
Date: 2011-07-27 17:29:55 +0200
From: @njnes
Changeset [89e3602630f4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=89e3602630f4) 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=89e3602630f4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=89e3602630f4)
Changeset description:
don't strip zero's from literals anymore. Fixes bug #2579 (ie 1.0/2.0 now results in 0.500)
some more fixes to make sure we can handle q14 on larger scales.
## Comment 16048
Date: 2011-07-29 11:03:54 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16239
Date: 2011-09-16 15:04:33 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17411
Date: 2012-07-04 15:48:37 +0200
From: Simon Brodt <<simon.brodt>>
Problem still exists for:
sql>SELECT '3.1'/'5.1';
+----------------------+
| sql_div_single_value |
+======================+
| 0 |
+----------------------+
1 tuple (0.804ms)
The following returns the correct result:
sql>SELECT '3.1'/5.1;
+----------------------+
| sql_div_single_value |
+======================+
| 0.607 |
+----------------------+
1 tuple (0.755ms)
sql>SELECT 3.1/5.1;
+----------------------+
| sql_div_single_value |
+======================+
| 0.607 |
+----------------------+
1 tuple (0.667ms)
sql>SELECT 3.1/'5.1';
+----------------------+
| sql_div_single_value |
+======================+
| 0.607 |
+----------------------+
1 tuple (0.741ms)
## Comment 17678
Date: 2012-08-24 14:55:56 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18030
Date: 2012-11-27 11:27:38 +0100
From: @romulogoncalves
A test was added to the Bug_tracker_2012 named incorrect_cast_from_double_to_int.Bug-2579
The correct out and err output as well.
## Comment 18172
Date: 2012-11-28 10:54:45 +0100
From: @njnes
SELECT '3.1'/'5.1'; division of 2 strings. The compiler cannot guess the proper type here.
## Comment 18211
Date: 2012-11-28 14:44:15 +0100
From: @njnes
Changeset [f5f1bf4f326e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f5f1bf4f326e) 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=f5f1bf4f326e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f5f1bf4f326e)
Changeset description:
approved output. Dividing 2 strings is simply not supported. Compiler
just takes a division operator (and by bad luck) its the byte/byte version.
Bug #2579
## Comment 18366
Date: 2013-01-22 09:29:09 +0100
From: @sjoerdmullender
Oct2012-SP3 has been released.
| SQL: incorrect cast from double to int | https://api.github.com/repos/MonetDB/MonetDB/issues/2579/comments | 0 | 2020-11-30T11:04:17Z | 2024-06-27T11:48:03Z | https://github.com/MonetDB/MonetDB/issues/2579 | 753,380,113 | 2,579 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-05 03:01:49 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2011-09-08 14:46:54 +0200
## Comment 14214
Date: 2010-07-05 03:01:49 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
After a transaction (including commit) that replaced a big table (drop, create, insert) in the database. I ended up with; The actual trigger for this was a grant command, which 'seemed' to be be executed in the transaction, but did not result in access to the resource. I executed it again after the transaction, but this aborted the server.
>mserver5: ../../../src/gdk/gdk_bbp.mx:2006: decref: Assertion `0' failed.
Reproducible: Didn't try
## Comment 16199
Date: 2011-09-08 14:46:54 +0200
From: @sjoerdmullender
Please provide a test case.
| gdk/gdk_bbp.mx:2006: decref: Assertion `0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/2578/comments | 0 | 2020-11-30T11:04:14Z | 2024-06-27T11:48:02Z | https://github.com/MonetDB/MonetDB/issues/2578 | 753,380,079 | 2,578 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-05 00:25:41 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @drstmane
Last updated: 2010-08-30 09:18:32 +0200
## Comment 14213
Date: 2010-07-05 00:25:41 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
Executing the following query results in a list of 'null' values.
select kvk from kvk where kvk not in (select kvk from kvk_nieuw union select kvk from kvk_extra union select kvk from kvk_extra_nieuw);
While this query returns the expected behavior.
select kvk from kvk except (select kvk from kvk_nieuw union select kvk from kvk_extra union select kvk from kvk_extra_nieuw);
Reproducible: Always
sql>\d kvk
CREATE TABLE "sys"."kvk" (
"id" int NOT NULL DEFAULT next value for "sys"."seq_5288",
"kvk" bigint,
"bedrijfsnaam" varchar(256),
"adres" varchar(64),
"postcode" char(6),
"plaats" varchar(32),
"type" varchar(14),
"kvks" int,
"sub" int,
"bedrijfsnaam_size" smallint,
"adres_size" smallint,
CONSTRAINT "kvk_id_pkey" PRIMARY KEY ("id")
);
sql>\d kvk_nieuw
CREATE TABLE "sys"."kvk_nieuw" (
"kvk" bigint,
"bedrijfsnaam" varchar(256),
"kvks" int,
"sub" int,
"adres" varchar(64),
"postcode" varchar(8),
"plaats" varchar(32),
"type" varchar(14)
);
sql>\d kvk_extra
CREATE TABLE "sys"."kvk_extra" (
"kvk" bigint,
"bedrijfsnaam" varchar(256),
"straat" varchar(256),
"nummer" int,
"toevoeging" varchar(16),
"postcode" char(6),
"plaats" varchar(32),
"website" varchar(128),
"type" varchar(14),
"status" varchar(64),
"kvks" int,
"sub" int
);
sql>\d kvk_extra_nieuw
CREATE TABLE "sys"."kvk_extra_nieuw" (
"kvk" bigint,
"bedrijfsnaam" varchar(256),
"straat" varchar(256),
"nummer" int,
"toevoeging" varchar(16),
"postcode" varchar(10),
"plaats" varchar(32),
"website" varchar(128),
"type" varchar(14),
"status" varchar(64),
"kvks" int,
"sub" int
);
MonetDB server v5.21.0 (64-bit), based on kernel v1.39.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-testing
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: root@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
Backup of the database is available in private.
## Comment 14295
Date: 2010-07-09 13:10:06 +0200
From: @grobian
Changeset [66faaf067601](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=66faaf067601) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=66faaf067601](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=66faaf067601)
Changeset description:
Add (sort of reverse-engineered) test for bug #2577
## Comment 14298
Date: 2010-07-09 13:18:54 +0200
From: @skinkie
First query now results in Segmentation Fault.
select kvk from kvk where kvk not in (select kvk from kvk_nieuw union select
kvk from kvk_extra union select kvk from kvk_extra_nieuw);
0x00007fffe43eb143 in rel_logical_exp (sql=0x147b068, rel=0x0, sc=0x167c278, f=1) at ../../../src/server/rel_select.mx:2655
warning: Source file is more recent than executable.
2655 r = rel_value_exp(sql, &rel, sval, f, ek);
(gdb) bt
0 0x00007fffe43eb143 in rel_logical_exp (sql=0x147b068, rel=0x0, sc=0x167c278, f=1) at ../../../src/server/rel_select.mx:2655
1 0x00007fffe43f1c8c in rel_select_exp (sql=0x147b068, rel=0xab7ba8, outer=0x0, sn=0x167c378, ek=...) at ../../../src/server/rel_select.mx:4410
2 0x00007fffe43f3233 in rel_query (sql=0x147b068, rel=0x0, sq=0x167c378, toplevel=1, ek=...) at ../../../src/server/rel_select.mx:4730
3 0x00007fffe43f46b2 in rel_subquery (sql=0x147b068, rel=0x0, sq=0x167c378, ek=...) at ../../../src/server/rel_select.mx:5073
4 0x00007fffe43f472c in rel_selects (sql=0x147b068, s=0x167c378) at ../../../src/server/rel_select.mx:5084
5 0x00007fffe43e2ade in rel_semantic (sql=0x147b068, s=0x167c378) at ../../../src/server/rel_semantic.mx:336
6 0x00007fffe43484c3 in sql_symbol2stmt (c=0x147b068, sym=0x167c378) at ../../../../src/backends/monet5/sql.mx:1362
7 0x00007fffe43945f6 in SQLparser (c=0x605878) at ../../../../src/backends/monet5/sql_scenario.mx:1275
8 0x00007ffff7b04fb2 in runPhase (c=0x605878, phase=1) at ../../../src/mal/mal_scenario.mx:604
9 0x00007ffff7b050ea in runScenarioBody (c=0x605878) at ../../../src/mal/mal_scenario.mx:646
10 0x00007ffff7b05371 in runScenario (c=0x605878) at ../../../src/mal/mal_scenario.mx:682
11 0x00007ffff7ab92af in MSserveClient (dummy=0x605878) at ../../../src/mal/mal_session.mx:473
12 0x00007ffff57a9547 in start_thread () from /lib/libpthread.so.0
13 0x00007ffff48db28d in clone () from /lib/libc.so.6
(gdb) q
## Comment 14299
Date: 2010-07-09 13:19:46 +0200
From: @skinkie
Ok reason for segmentation fault: one of the tables in the in(...) expression doesn't exist anymore.
## Comment 14301
Date: 2010-07-09 13:20:48 +0200
From: @grobian
file another bug for that.
## Comment 14302
Date: 2010-07-09 13:22:21 +0200
From: @skinkie
Original bug can still be reproduced using the proper table names.
## Comment 14305
Date: 2010-07-09 13:25:51 +0200
From: @grobian
If you'd had taken the time to actually look at what I checked in, you'd have seen that it confirms your bug.
## Comment 14307
Date: 2010-07-09 13:29:00 +0200
From: @skinkie
(In reply to comment 6)
> If you'd had taken the time to actually look at what I checked in, you'd have
> seen that it confirms your bug.
Actually I looked over your patch;
+select kvk from kvk where kvk not in (
+% .L53 table_name
+% kvk name
+% bigint type
+% 1 length
+[ 1 ]
+select kvk from kvk except (
+% sys.kvk table_name
+% kvk name
+% bigint type
+% 1 length
+[ 1 ]
I don't see the 'null' output that I show?
## Comment 14310
Date: 2010-07-09 13:41:36 +0200
From: @grobian
it's a test, if I'd approved the NULL, the test wouldn't fail, like it should until the bug is fixed ...
## Comment 14316
Date: 2010-07-09 14:08:09 +0200
From: @skinkie
(In reply to comment 8)
> it's a test, if I'd approved the NULL, the test wouldn't fail, like it should
> until the bug is fixed ...
I read it as:
Fabian didn't have an issue because he had the correct output.
But I see now that you manually 'made' it correct ;)
## Comment 14564
Date: 2010-07-30 14:43:02 +0200
From: @njnes
Changeset [998b436673fa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=998b436673fa) 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=998b436673fa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=998b436673fa)
Changeset description:
We now put an project after each (NOT) 'IN'. Solves Bug #2577.
## Comment 14600
Date: 2010-08-02 16:13:54 +0200
From: @drstmane
Test works fine, now, with nightly testing:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/not-in-union-except-union.Bug-2577.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/not-in-union-except-union.Bug-2577.err.00.html
## Comment 14826
Date: 2010-08-30 09:18:32 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| not in (... union ...) differs from: except (... union ...) | https://api.github.com/repos/MonetDB/MonetDB/issues/2577/comments | 0 | 2020-11-30T11:04:11Z | 2024-06-27T11:48:01Z | https://github.com/MonetDB/MonetDB/issues/2577 | 753,380,027 | 2,577 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-04 03:21:24 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
CC: @njnes, @drstmane
Last updated: 2011-08-05 14:59:50 +0200
## Comment 14211
Date: 2010-07-04 03:21:24 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
1. copy into (serveral times, resulting in errors)
>mserver5: ../../../src/gdk/gdk_heap.mx:514: HEAPsave_intern: Assertion `0' failed.
Reproducible: Sometimes
### Actual Results:
MonetDB server v5.21.0 (64-bit), based on kernel v1.39.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-testing
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: root@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
## Comment 14212
Date: 2010-07-04 03:24:16 +0200
From: @skinkie
sql>delete from kvk_nieuw;
2059000 affected rows
sql>copy 1030500 records into kvk_nieuw from '/home/skinkie/zomer/utf8.txt' delimiters '\t', '\n' null as '';
1030500 affected rows
sql>copy 1030800 records into kvk_nieuw from '/home/skinkie/zomer/utf8.txt' delimiters '\t', '\n' null as '';
SQLException:importTable:missing separator ' ' line 1030801 field 6
failed to import table
sql>copy 1030760 records into kvk_nieuw from '/home/skinkie/zomer/utf8.txt' delimiters '\t', '\n' null as '';
SQLException:importTable:missing separator ' ' line 1030761 field 6
failed to import table
sql>copy 1030600 records into kvk_nieuw from '/home/skinkie/zomer/utf8.txt' delimiters '\t', '\n' null as '';
1030600 affected rows
sql>copy 1030700 records into kvk_nieuw from '/home/skinkie/zomer/utf8.txt' delimiters '\t', '\n' null as '';
*bug sets in*
## Comment 14234
Date: 2010-07-07 09:14:19 +0200
From: @njnes
assert is removed. Only in the case of strings these (slower) mmaps are needed.
## Comment 14779
Date: 2010-08-25 19:47:55 +0200
From: @skinkie
The problem is back...
## Comment 14780
Date: 2010-08-25 21:07:01 +0200
From: @drstmane
indeed, the assert is still in the code
(cf.,
http://dev.monetdb.org/hg/MonetDB/file/tip/MonetDB/src/gdk/gdk_heap.mxl514
)
where it was added by Niels in this changeset:
http://dev.monetdb.org/hg/MonetDB/rev/42775467d209
given that the assert is not properly indented (like more assert added with above changeset), it might be left-over debugging code that accidentally sneaked in --- but Niels should double check this ...
## Comment 15896
Date: 2011-07-05 17:13:27 +0200
From: @sjoerdmullender
Is this still an issue?
The assert was removed in rev. [4315a44b501d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4315a44b501d)
## Comment 16077
Date: 2011-08-05 14:59:50 +0200
From: @sjoerdmullender
I'm assuming the mentioned fix did the trick.
| copy into resulted in HEAPsave_intern: Assertion `0' failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/2576/comments | 0 | 2020-11-30T11:04:07Z | 2024-06-27T11:47:59Z | https://github.com/MonetDB/MonetDB/issues/2576 | 753,379,991 | 2,576 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-04 02:48:40 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 2.38.5 (Jun2010-SP2) [obsolete]
CC: @mlkersten, @njnes, @drstmane
Last updated: 2010-11-15 09:39:09 +0100
## Comment 14210
Date: 2010-07-04 02:48:40 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
Using copy into to insert a table into MonetDB isn't very user friendly if the source material contains errors. Ideally MonetDB should show all errors that it finds and not only the first it encounters. A bigger problem is in the SQLException:importTable:missing separator error. The line offset given there doesn't represent the line where the error is found.
I can guess threading could give these issues. Data samples are available in private.
Reproducible: Always
MonetDB server v5.21.0 (64-bit), based on kernel v1.39.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-testing
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: root@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
## Comment 14285
Date: 2010-07-09 12:35:34 +0200
From: @grobian
Please give an exact example of an error you see, and what you would like to see.
## Comment 14288
Date: 2010-07-09 12:49:20 +0200
From: @skinkie
sql>copy 6096600 records into kvk_test from '/home/skinkie/zomer/utf8-nocomma.txt' delimiters '\t', '\n' null as '';
SQLException:importTable:missing separator ' ' line 344961 field 7
missing separator ' ' line 344961 field 7
failed to import table
Please observe that currently the error message is duplicated, never had that before. Next to that line 344961 does not contain an error at all. The message is bogus, and there are errors in other places of the files.
## Comment 14619
Date: 2010-08-06 10:41:43 +0200
From: @mlkersten
After an error the complete statement should be rolled back, because one can not assume that correct data has been entered. Likewise, continue reading the file to the next field/record separator only marginally improves error reporting.
## Comment 14621
Date: 2010-08-06 11:08:28 +0200
From: @skinkie
(In reply to comment 3)
> After an error the complete statement should be rolled back, because one can
> not assume that correct data has been entered. Likewise, continue reading the
> file to the next field/record separator only marginally improves error
> reporting.
I do not dispute that, but that might make position of the file where the error is 'detected' too late. (Or improper management what line, of what block) is currently being read).
## Comment 14677
Date: 2010-08-13 14:10:49 +0200
From: @njnes
waiting for an example or is this similar to bug #2615
## Comment 14781
Date: 2010-08-29 14:57:05 +0200
From: @skinkie
So getting back to the original subject. Given the current infrastructure it should be possible to give some more feedback to the user than this:
sql>copy 57567517 records into fulltext from '/home/skinkie/automatic/indexer/test2' using delimiters '\t', '\n', '';
SQLException:importTable:value 'failed to import table
Now I guess it breaks on a 'special character' wrongly truncated UTF-8 for example, but still with the above isn't much to do. (You still have to investigate what line breaks, manually that doesn't really cut it.)
## Comment 14855
Date: 2010-08-30 11:01:19 +0200
From: @drstmane
(In reply to comment 6)
> sql>copy 57567517 records into fulltext from
> '/home/skinkie/automatic/indexer/test2' using delimiters '\t', '\n', '';
> SQLException:importTable:value 'failed to import table
Lacking a closing "'", this snippet of the error message looks truncated to me.
Could you please provide us with sufficient information & input to reproduce the problem ourselves, i.e., the table definition and the data (.csv file), or at least the fraction of the data that triggers above error?
## Comment 14856
Date: 2010-08-30 12:21:24 +0200
From: @skinkie
Created attachment 32
utf8 fragment
Any utf8 fragment would actually do.
CREATE TABLE "sys"."fulltext" (
"documentid" BIGINT NOT NULL,
"seq" SMALLINT NOT NULL,
"trigram" CHAR(3) NOT NULL
);
copy 2 records into fulltext from '/tmp/utf8-truncation' using delimiters '\t', '\n', '';
> Attached file: [utf8-truncation](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2575_utf8-truncation_32) (application/octet-stream, 37 bytes)
> Description: utf8 fragment
## Comment 14857
Date: 2010-08-30 14:27:41 +0200
From: @sjoerdmullender
This is a new problem, so should really be reported in a new tracker item.
The problem here is that the snprintf call that is used to format the error message doesn't like the incomplete UTF-8 sequence any more than the parser does. This means that snprintf just aborts formatting, and therefore the error message is incomplete.
So Stefan M, the copy/paste was actually complete with the unbalanced quote: that's where snprintf aobrted.
## Comment 14858
Date: 2010-08-30 14:41:32 +0200
From: @sjoerdmullender
Changeset [50ff7afd4fe4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=50ff7afd4fe4) 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=50ff7afd4fe4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=50ff7afd4fe4)
Changeset description:
Fix for bug #2575, comment 6.
If snprintf fails (e.g. because of a bad UTF-8 sequence),
report the error message without the value.
## Comment 14861
Date: 2010-08-30 14:45:20 +0200
From: @skinkie
*** Bug #2662 has been marked as a duplicate of this bug. ***
## Comment 14863
Date: 2010-08-30 14:54:14 +0200
From: @sjoerdmullender
Changeset [67b86dfaf583](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=67b86dfaf583) 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=67b86dfaf583](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=67b86dfaf583)
Changeset description:
Added test for bug #2575 (comment 6).
| copy into missing separator doesn't represent true error line | https://api.github.com/repos/MonetDB/MonetDB/issues/2575/comments | 0 | 2020-11-30T11:04:04Z | 2024-06-27T11:47:58Z | https://github.com/MonetDB/MonetDB/issues/2575 | 753,379,947 | 2,575 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-02 12:04:45 +0200
From: @skinkie
To: clients devs <<bugs-clients>>
Version: -- development
Last updated: 2010-08-30 09:18:00 +0200
## Comment 14186
Date: 2010-07-02 12:04:45 +0200
From: @skinkie
The dump produced from msqldump doesn't include GRANTs on the tables. This makes the dump not directly usable, until the GRANTs have been applied manually.
## Comment 14218
Date: 2010-07-05 17:35:40 +0200
From: @sjoerdmullender
Changeset [4c2084c2a824](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4c2084c2a824) 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=4c2084c2a824](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=4c2084c2a824)
Changeset description:
Implemented dumping of GRANTs to columns/tables.
This fixes bug #2574.
## Comment 14219
Date: 2010-07-05 17:35:41 +0200
From: @sjoerdmullender
Changeset [3453a035be69](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3453a035be69) 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=3453a035be69](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3453a035be69)
Changeset description:
Merge from Jun2010 branch.
Implemented dumping of GRANTs to columns/tables.
This fixes bug #2574.
## Comment 14220
Date: 2010-07-05 18:05:32 +0200
From: @sjoerdmullender
Changeset [c2bc481efdea](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c2bc481efdea) 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=c2bc481efdea](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c2bc481efdea)
Changeset description:
Implemented dumping of GRANT statements.
This fixes bug #2574.
## Comment 14793
Date: 2010-08-30 09:18:00 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| msqldump does not export GRANT information upon export | https://api.github.com/repos/MonetDB/MonetDB/issues/2574/comments | 0 | 2020-11-30T11:04:01Z | 2024-06-27T11:47:57Z | https://github.com/MonetDB/MonetDB/issues/2574 | 753,379,896 | 2,574 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-02 09:51:51 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @njnes
Last updated: 2010-08-20 14:03:58 +0200
## Comment 14178
Date: 2010-07-02 09:51:51 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9
Build Identifier:
When starting a Jun2010 server on a Feb2010-created DB, the server automatically upgrades the DB catalog:
"Upgrading catalog from Feb2010"
While the Jun2010 server keeps running, everything seems to work fine.
However, once the Jun2010 server is stopped and restarted, the DB catalog seems to be corrupted; at least a "select * from tables;" query results in
"SELECT: no such table 'tables'"
Queries on actual data seems to work fine, though ...
Reproducible: Always
### Steps to Reproduce:
1. create DB with Feb2010
2. stop Feb2010 server
3. start Jun2010 server on same DB
-> "Upgrading catalog from Feb2010"
=> "select * from tables;" works as expected
4. stop and restart Jun2010 server on same DB
=> "select * from tables;" results in
"SELECT: no such table 'tables'"
### Actual Results:
"select * from tables;"
results in
"SELECT: no such table 'tables'"
### Expected Results:
"select * from tables;"
should work as expected
data queries seems to work fine in all cases.
## Comment 14185
Date: 2010-07-02 11:48:09 +0200
From: @drstmane
Should we consider warning users about this problem, e.g., by a reply to the release announce email and a "post-it" on the release notes page of the web site?
## Comment 14196
Date: 2010-07-02 14:36:00 +0200
From: @njnes
Changeset [839af9c3b69b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=839af9c3b69b) 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=839af9c3b69b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=839af9c3b69b)
Changeset description:
fix schema id for old database format.
Fixes bug #2573
## Comment 14198
Date: 2010-07-02 14:46:51 +0200
From: @sjoerdmullender
This fix doesn't seem to fix an already corrupted database:
create db with Feb2010
upgrade to Jun2010
run server
apply fix
run server again
## Comment 14199
Date: 2010-07-02 14:54:56 +0200
From: @njnes
True, but we don't have a way to detect a corrupt converted db. If the user detects it, it can be fixed by hand with a small sql update.
What is needed is to update the schema_id of the newly created views (tables and columns). These can be found using select * from _tables;
## Comment 14200
Date: 2010-07-02 15:03:49 +0200
From: @sjoerdmullender
Can you then provide the exact SQL query you have to perform?
And why can't you detect it? I can by doing e.g. select * from tables (note lack of _).
## Comment 14203
Date: 2010-07-02 15:16:28 +0200
From: @sjoerdmullender
OK, to recover your database, do this:
Start mserver5 and connect to it with mclient.
Then perform the two queries:
update _tables set schema_id = (select id from schemas where name = 'sys') where name = 'tables';
update _tables set schema_id = (select id from schemas where name = 'sys') where name = 'columns';
Then stop the server and restart it.
Done.
## Comment 14204
Date: 2010-07-02 15:24:47 +0200
From: @njnes
sql>UPDATE _TABLES set schema_id=(select id from schemas where name = 'sys') where name in ( 'tables');
1 affected row
sql>UPDATE _TABLES set schema_id=(select id from schemas where name = 'sys') where name in ( 'columns');
1 affected row
## Comment 14205
Date: 2010-07-02 18:48:01 +0200
From: @drstmane
In case other tables, functions, types, or sequences have been created on a Feb2010 -> Jun2010 upgraded database using the (buggy) Jun2010 release, also these need to be fixed.
I.e., instead of doing only the two update statements suggested by Niels,
we actually need to do the following four update statements, preferably automatically on server start:
update sys._tables set schema_id=(select id from sys.schemas where name='sys') where schema_id not in (select id from sys.schemas);
update sys.functions set schema_id=(select id from sys.schemas where name='sys') where schema_id not in (select id from sys.schemas);
update sys.types set schema_id=(select id from sys.schemas where name='sys') where schema_id not in (select id from sys.schemas);
update sys.sequences set schema_id=(select id from sys.schemas where name='sys') where schema_id not in (select id from sys.schemas);
Unfortunately, these queries do not work in all cases do to another bug:
with
select * from sys._tables where schema_id <> 0 and schema_id not in (select id from sys.schemas);
+------+------+-----------+---------------------------------------+------+--------+---------------+----------+
| id | name | schema_id | query | type | system | commit_action | readonly |
+======+======+===========+=======================================+======+========+===============+==========+
| 4219 | z | 2000 | null | 0 | false | 0 | false |
| 4222 | zz | 2000 | null | 0 | false | 0 | false |
| 4225 | xxx | 2000 | null | 0 | false | 0 | false |
+------+------+-----------+---------------------------------------+------+--------+---------------+----------+
I get
update sys._tables set schema_id=(select id from sys.schemas where name='sys') where schema_id not in (select id from sys.schemas);
SQLException:zero_or_one:cardinality violation (3>1)
I'll file a separate bug report for the latter bug once I find the time ...
## Comment 14206
Date: 2010-07-02 22:05:35 +0200
From: @sjoerdmullender
(In reply to comment 8)
> update sys.functions set schema_id=(select id from sys.schemas where
> name='sys') where schema_id not in (select id from sys.schemas);
> update sys.types set schema_id=(select id from sys.schemas where name='sys')
> where schema_id not in (select id from sys.schemas);
Actually, these queries also needs to avoid changing entries where schema_id=0:
update sys.functions set schema_id=(select id from sys.schemas where
name='sys') where schema_id not in (select id from sys.schemas) and schema_id <> 0;
update sys.types set schema_id=(select id from sys.schemas where name='sys')
where schema_id not in (select id from sys.schemas) and schema_id <> 0;
It is safe to add the schema_id<>0 condition to all queries.
## Comment 14364
Date: 2010-07-12 12:48:52 +0200
From: @drstmane
Created attachment 13
test scripts (SQL) mentioned in comment below
First the good news:
The following thorough test for upgrading from Feb2010(-SP2) to a (not yet released) Jun2010-SP1 candidate appears to work fine, now (please find the mentioned *.sql in the attached Bug2573.tgz):
- start Feb2010(-SP2) server
- run attached Feb2010.1.sql that creates schemas, tables, sequences, types
and functions in various schemas
- stop Feb2010(-SP2) server
- restart Feb2010(-SP2) server
- run attached Feb2010.2.sql that checks the previously created schemas,
tables, sequences, types and functions as well as the catalog as such.
- stop Feb2010(-SP2) server
- start Jun2010-SP1 server on the same data base
=> "Upgrading catalog from Feb2010"
- run attached Jun2010.0.sql that checks the Feb2010-created schemas,
tables, sequences, types and functions as well as the catalog as such.
- stop Jun2010-SP1 server
- restart Jun2010-SP1 server
- run attached Jun2010.1.sql that creates more schemas, tables, sequences,
types and functions in various schemas
- stop Jun2010-SP1 server
- restart Jun2010-SP1 server
- run attached Jun2010.2.sql that checks both the Feb2010-created and
Jun2010-SP1-created schemas, tables, sequences, types and functions as
well as the catalog as such.
All this appears to work fine.
Now the not that good news:
I also tried the above upgrade not only directly from Feb2010(-SP2) to
Jun2010-SP1, but also to the retracted Jun2010, first, as "intermedite
step".
First of all, with tables and functions that use self-defined types (as
Feb2010.1.sql) does, already starting the Jun2010 server on the Feb2010
database results in a segfault (details available on request).
Likewise, trying to run a Jun2010-SP1 server on that database after the
Jun2010 server failed to upgrade it results in the same segfault.
It is unlikely that these bug will be fixed; they will become "obsolete" with the release of Jun2010-SP1 and the advice to upgrade directly from Feb2010(-SP2) to Jun2010-SP1.
However, with when avoiding the use of self-defined types in tables &
functions (see attached {Feb,Jun}2010.1-.sql variants), the following
"indirect" upgrade paths, i.e., in case the Feb2010(-SP2) database was
initially upgraded with the retracted Jun2010 release:
- start Feb2010(-SP2) server
- run attached Feb2010.1.sql that creates schemas, tables, sequences, types
and functions in varius schemas
- stop Feb2010(-SP2) server
- restart Feb2010(-SP2) server
- run attached Feb2010.2.sql that checks the previously created schemas,
tables, sequences, types and functions as well as the catalog as such.
- stop Feb2010(-SP2) server
- start Jun2010 server on the same data base
=> "Upgrading catalog from Feb2010"
- stop Jun2010 server
- start Jun2010-SP1 server on the same data base
- fix catalog using the follwoing 4 SQL statements:
update _tables set schema_id = ( select id from schemas where name = 'sys' )
where schema_id not in (select id from schemas) and schema_id <> 0;
update functions set schema_id = ( select id from schemas where name = 'sys' )
where schema_id not in (select id from schemas) and schema_id <> 0;
update types set schema_id = ( select id from schemas where name = 'sys' )
where schema_id not in (select id from schemas) and schema_id <> 0;
update sequences set schema_id = ( select id from schemas where name = 'sys' )
where schema_id not in (select id from schemas) and schema_id <> 0;
- stop Jun2010-SP1 server
- restart Jun2010-SP1 server
Everything's fine and keeps on working as expected.
> Attached file: [Bug2573.tgz](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2573_Bug2573.tgz_13) (application/x-gzip, 1001 bytes)
> Description: test scripts (SQL) mentioned in comment below
## Comment 14365
Date: 2010-07-12 12:49:15 +0200
From: @drstmane
Since it is (for now --- we're working on it) not (easily) possible to include an "upgrade" test into our nightly testing system, I close this bug without further tests.
| DB catalog corrupted after upgrade from Feb2010 to Jun2010 | https://api.github.com/repos/MonetDB/MonetDB/issues/2573/comments | 0 | 2020-11-30T11:03:57Z | 2024-06-27T11:47:56Z | https://github.com/MonetDB/MonetDB/issues/2573 | 753,379,841 | 2,573 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-02 00:12:45 +0200
From: Mitja Kleider <<mitja>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
Duplicates: #2570
Last updated: 2010-07-02 08:37:47 +0200
## Comment 14173
Date: 2010-07-02 00:12:45 +0200
From: Mitja Kleider <<mitja>>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.6) Gecko/20100628 Ubuntu/10.04 (lucid) Firefox/3.6.6
Build Identifier:
When compiling the latest hg version with options
--enable-optimize --disable-debug --disable-assert
compiling stops because of a warning, the patch below fixes it.
Reproducible: Always
### Steps to Reproduce:
1. set the compile options --enable-optimize --disable-debug --disable-assert
2. compile
### Actual Results:
cc1: warnings being treated as errors
../../../src/mal/mal_interpreter.mx: In function 'DFLOWscheduler':
../../../src/mal/mal_interpreter.mx:1281: error: 'f' may be used uninitialized in this function
### Expected Results:
successful compilation
diff -r [c847cd226a6e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c847cd226a6e) MonetDB5/src/mal/mal_interpreter.mx
--- a/MonetDB5/src/mal/mal_interpreter.mx Thu Jul 01 20:13:45 2010 +0200
+++ b/MonetDB5/src/mal/mal_interpreter.mx Fri Jul 02 00:07:25 2010 +0200
@@ -1278,7 +1278,7 @@
int pc = 0, i, j, oa =0, ia;
int limit = flow->stop - flow->start;
str ret = MAL_SUCCEED;
- FlowStep fs = (FlowStep)alloca(sizeof(FlowStepRec) * limit), f;
+ FlowStep fs = (FlowStep)alloca(sizeof(FlowStepRec) * limit), f = NULL;
InstrPtr p;
if ( limit == 0)
## Comment 14174
Date: 2010-07-02 08:37:47 +0200
From: @drstmane
This has already been reported in
2570 "MonetDB5 fails to compile"
http://bugs.monetdb.org/show_bug.cgi?id=2570
The proposed patch would indeed "silence" the compiler.
However, then the code might run into dereferencing a NULL pointer,
and consequently cause a segfault --- probably not what we want.
A proper fix is required that does fix compilation and also prevent segfaults.
*** This bug has been marked as a duplicate of bug #2570 ***
| uninitialized variable warning breaks compiling | https://api.github.com/repos/MonetDB/MonetDB/issues/2572/comments | 0 | 2020-11-30T11:03:54Z | 2024-06-28T13:20:33Z | https://github.com/MonetDB/MonetDB/issues/2572 | 753,379,802 | 2,572 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-01 17:33:53 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
Last updated: 2010-08-20 11:25:24 +0200
## Comment 14170
Date: 2010-07-01 17:33:53 +0200
From: @sjoerdmullender
The Jun2010 branch of sql fails to compile when using an optimized build.
The error is:
sql/src/backends/monet5/merovingian/merovingian.c: In function ‘main’:
sql/src/backends/monet5/merovingian/merovingian.c:430: error: ‘d’ may be used uninitialized in this function
There is a goto in MERO_EXIT which jumps to the shutdown label. This macro may be called before `d' is initialized. In the shutdown section `d' is dereferenced without any checks.
## Comment 14171
Date: 2010-07-01 18:17:59 +0200
From: @grobian
Changeset [f5d253fa8790](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f5d253fa8790) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f5d253fa8790](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f5d253fa8790)
Changeset description:
Fix issues found by compilers when compiling in strict mode (Bug #2571)
- make sure d isn't unitialised (and dereferenced)
- make sure we don't try to remove and free a NULL pidfilename
| merovingian fails to build | https://api.github.com/repos/MonetDB/MonetDB/issues/2571/comments | 0 | 2020-11-30T11:03:51Z | 2024-06-27T11:47:54Z | https://github.com/MonetDB/MonetDB/issues/2571 | 753,379,763 | 2,571 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-01 17:29:41 +0200
From: @sjoerdmullender
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
CC: mitja, @mlkersten, @drstmane
Last updated: 2010-07-02 10:09:54 +0200
## Comment 14169
Date: 2010-07-01 17:29:41 +0200
From: @sjoerdmullender
The default branch of MonetDB5 fails to compile when using an optimized build.
The error is:
MonetDB5/src/mal/mal_interpreter.mx: In function ‘DFLOWscheduler’:
MonetDB5/src/mal/mal_interpreter.mx:1281: error: ‘f’ may be used uninitialized in this function
I don't know how to fix this, since there is a goto into the middle of a loop. At the start of the loop (which may be skipped) is the initialization of `f', and in the bottom part, after the jump label, `f' is used.
## Comment 14175
Date: 2010-07-02 08:37:47 +0200
From: @drstmane
*** Bug #2572 has been marked as a duplicate of this bug. ***
## Comment 14179
Date: 2010-07-02 10:04:19 +0200
From: @drstmane
changeset: 36512:8eec5abe209c
user: mk@cwi.nl
date: Fri Jul 02 09:31:30 2010 +0200
files: MonetDB5/src/mal/mal_interpreter.mx
description:
Fixed uninitialized variable
Also taking care of initial jump.
## Comment 14180
Date: 2010-07-02 10:05:32 +0200
From: @grobian
will only show up at next release (Jun2010-SP1)
## Comment 14181
Date: 2010-07-02 10:09:11 +0200
From: @drstmane
Just for the records:
This report and its fix are not related to the Jun2010 branch / releases at all as the problem occurred and was fixed only in the "default" development branch ...
Hence, it will only show up in the next feature release (possibly Sep2010) and of course instantly for those how compile MonetDB5 from HG sources ...
## Comment 14182
Date: 2010-07-02 10:09:54 +0200
From: @grobian
bah, please ignore my previous comment.
| MonetDB5 fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/2570/comments | 0 | 2020-11-30T11:03:48Z | 2024-06-27T11:47:53Z | https://github.com/MonetDB/MonetDB/issues/2570 | 753,379,720 | 2,570 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-01 14:56:55 +0200
From: Mitja Kleider <<mitja>>
To: SQL devs <<bugs-sql>>
Version: 2.38.5 (Jun2010-SP2) [obsolete]
CC: @drstmane, @skinkie
Last updated: 2010-11-15 09:38:58 +0100
## Comment 14163
Date: 2010-07-01 14:56:55 +0200
From: Mitja Kleider <<mitja>>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build Identifier:
ERROR = !sql_stmt symbol(4ed7b38)->token = INSERT
This error message occurs when running the query below:
Reproducible: Always
### Steps to Reproduce:
create table tmp_a (node integer, k varchar(255), v varchar(1024));
create table tmp_b (node integer, k varchar(255), v varchar(1024));
insert into tmp_a values (1,'a','a');
insert into tmp_b values (1,'a','a');
insert into tmp_b values (2,'b','a');
insert into tmp_a select node,k,v from tmp_b except select node,k,v from tmp_a;
### Actual Results:
sql_stmt symbol(351a8f8)->token = INSERT
### Expected Results:
tuple(s) inserted
This was fine:
sql>select node,k,v from tmp_a except select node,k,v from tmp_b;
0 tuples
sql>select node,k,v from tmp_b except select node,k,v from tmp_a;
+------+------+------+
| node | k | v |
+======+======+======+
| 2 | b | a |
+------+------+------+
1 tuple
## Comment 14172
Date: 2010-07-01 18:28:57 +0200
From: Mitja Kleider <<mitja>>
As a sidenote:
SELECT node,k,v FROM new_node_tags EXCEPT SELECT node,k,v FROM node_tags;
is crashing mserver5, not in the testcase mentioned above, but under real conditions with 6*10^6 entries in node_tags and 5000 entries in new_node_tags.
I just do not know yet how to make it reproducible for anyone.
## Comment 14279
Date: 2010-07-09 11:23:44 +0200
From: @grobian
Changeset [af78dffbccdc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=af78dffbccdc) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=af78dffbccdc](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=af78dffbccdc)
Changeset description:
Add test for bug #2569
## Comment 14358
Date: 2010-07-10 10:33:42 +0200
From: @drstmane
a similar error occurs with this test
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.32.32.d.1-Fedora12/src_test_BugTracker-2010/crashonschema.Bug-2547.err.00.html
ERROR = !sql_stmt symbol(b31073f8)->token = CREATE_SCHEMA
## Comment 14469
Date: 2010-07-18 09:45:44 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/insert-into-except.Bug-2569.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-Fedora12/src_test_BugTracker-2010/crashonschema.Bug-2547.err.00.html
## Comment 14565
Date: 2010-07-30 14:43:04 +0200
From: @njnes
Changeset [d92e4d6dc20d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d92e4d6dc20d) 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=d92e4d6dc20d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d92e4d6dc20d)
Changeset description:
Fixed bug #2569 (except/union/intersect right after insert/delete/update. We now correctly fallback to the more general subquery case (not only simple selects (SQL_SELECT)).
## Comment 14599
Date: 2010-08-02 16:12:02 +0200
From: @drstmane
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/insert-into-except.Bug-2569.err.00.html
now works fine.
However,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/crashonschema.Bug-2547.err.00.html
still results in
QUERY = create schema intro3
ERROR = !sql_stmt symbol(7fe348007a88)->token = CREATE_SCHEMA
## Comment 14838
Date: 2010-08-30 09:23:19 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 14914
Date: 2010-09-20 09:58:59 +0200
From: @sjoerdmullender
This bug was fixed. The crash in the crashonschema test is obviously a different bug and warrants its own bug report.
| INSERT INTO ... EXCEPT ... fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2569/comments | 0 | 2020-11-30T11:03:44Z | 2024-06-27T11:47:52Z | https://github.com/MonetDB/MonetDB/issues/2569 | 753,379,664 | 2,569 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-01 14:08:54 +0200
From: Milena Ivanova <<M.Ivanova>>
To: clients devs <<bugs-clients>>
Version: -- development
Duplicates: #2567
Last updated: 2010-07-01 14:22:05 +0200
## Comment 14159
Date: 2010-07-01 14:08:54 +0200
From: Milena Ivanova <<M.Ivanova>>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
uri's with unix sockets are not handled by RMTconnect (mapi_mapiuri)
MALException:remote.connect:unable to connect to 'mapi:monetdb:///export/scratch1/milena/monet.DBG/var/MonetDB5/dbfarm/head/.mapi.sockhead': URI must contain a port number after the hostname
Reproducible: Always
## Comment 14160
Date: 2010-07-01 14:22:05 +0200
From: @grobian
*** This bug has been marked as a duplicate of bug #2567 ***
| mapi_mapiuri doesn't accept uri's with unix sockets | https://api.github.com/repos/MonetDB/MonetDB/issues/2568/comments | 0 | 2020-11-30T11:03:40Z | 2024-06-28T13:20:32Z | https://github.com/MonetDB/MonetDB/issues/2568 | 753,379,623 | 2,568 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-07-01 13:59:56 +0200
From: @grobian
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.1 (Jun2010) [obsolete]
CC: M.Ivanova
Last updated: 2010-08-20 14:03:58 +0200
## Comment 14157
Date: 2010-07-01 13:59:56 +0200
From: @grobian
mal>i := sabaoth.getLocalConnectionURI();
mal>io.print(i);
[ "mapi:monetdb:///ufs/fabian/scratch/monetdb/Jun2010/program-x86_64/var/MonetDB5/dbfarm/phantom2/.mapi.sockphantom2" ]
mal>y:= remote.connect(i, "monetdb", "monetdb");
!MALException:remote.connect:unable to connect to 'mapi:monetdb:///ufs/fabian/scratch/monetdb/Jun2010/program-x86_64/var/MonetDB5/dbfarm/phantom2/.mapi.sockphantom2': URI contains invalid port
There are two bugs here:
1) sabaoth.getLocalURI() returns an invalid url for UNIX domain sockets (dbname is attached to the socket url)
2) mapi_mapiuri doesn't cope with urls for UNIX domain sockets
## Comment 14158
Date: 2010-07-01 14:01:35 +0200
From: @grobian
Changeset [2d856b72dba7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2d856b72dba7) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2d856b72dba7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2d856b72dba7)
Changeset description:
Fix implementation of mapi_mapiuri to deal with UNIX socket urls properly. This fixes one part of Bug #2567.
## Comment 14161
Date: 2010-07-01 14:22:05 +0200
From: @grobian
*** Bug #2568 has been marked as a duplicate of this bug. ***
## Comment 14162
Date: 2010-07-01 14:31:00 +0200
From: @grobian
Changeset [2a62d1933339](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2a62d1933339) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2a62d1933339](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2a62d1933339)
Changeset description:
Return a correct URI for local connection from Sabaoth when the connection is a UNIX domain socket. Partial fix for bug #2567.
| remote.connect fails using UNIX domain socket url from sabaoth.getLocalConnectionURI. | https://api.github.com/repos/MonetDB/MonetDB/issues/2567/comments | 0 | 2020-11-30T11:03:37Z | 2024-06-27T11:47:50Z | https://github.com/MonetDB/MonetDB/issues/2567 | 753,379,584 | 2,567 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-29 17:18:44 +0200
From: @sjoerdmullender
To: buildtools devs <<bugs-buildtools>>
Version: 1.38.1 (Jun2010) [obsolete]
Last updated: 2010-07-01 15:54:36 +0200
## Comment 14149
Date: 2010-06-29 17:18:44 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.10) Gecko/20100622 Fedora/3.5.10-1.fc12 Firefox/3.5.10
Build Identifier:
The monetdb-install.sh script still has a --cvs option to get the sources from Sourceforge. However, Sourceforge no longer has the latest sources. The option should be replaced by a --hg option that gets the sources from dev.monetdb.org.
Reproducible: Always
### Steps to Reproduce:
1. monetdb-install.sh --cvs
2.
3.
### Actual Results:
Old sources.
### Expected Results:
New sources.
The component is not correct, but there is no better one.
## Comment 14164
Date: 2010-07-01 15:54:36 +0200
From: @grobian
Dropped CVS support from the script. It was decided not to add Mercurial support instead, because cloning the entire repo each and every time makes no sense from multiple points of view.
| monetdb-install.sh not yet ported to Mercurial | https://api.github.com/repos/MonetDB/MonetDB/issues/2566/comments | 0 | 2020-11-30T11:03:34Z | 2024-06-28T13:21:56Z | https://github.com/MonetDB/MonetDB/issues/2566 | 753,379,546 | 2,566 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-29 12:35:37 +0200
From: @grobian
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.1 (Jun2010) [obsolete]
Last updated: 2010-08-20 14:03:54 +0200
## Comment 14147
Date: 2010-06-29 12:35:37 +0200
From: @grobian
% /var/tmp/MonetDB-Jun2010-install/bin/mserver5 --version
MonetDB server v5.20.1 (32-bit), based on kernel v1.38.1 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 0.0GiB available memory, 8 available cpu cores
Configured for prefix: /var/tmp/MonetDB-Jun2010-install
Libraries:
libpcre: 8.00 2009-10-19 (compiled with 8.00)
openssl: OpenSSL 0.9.8n 24 Mar 2010 (compiled with OpenSSL 0.9.8n 24 Mar 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: fabian@build-x86-macosx (i386-apple-darwin9.8.0)
Compilation: gcc -O2
Linking : /Volumes/scratch/gentoo/usr/bin/i686-apple-darwin9-ld
Due to the failure to detect memory, any attempt to start fails due to insufficient memory errors.
## Comment 14148
Date: 2010-06-29 14:41:18 +0200
From: @grobian
% /var/tmp/MonetDB-Jun2010-install64/bin/mserver5 --version
MonetDB server v5.20.1 (64-bit), based on kernel v1.38.1 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 0.0GiB available memory, 8 available cpu cores
Configured for prefix: /var/tmp/MonetDB-Jun2010-install64
Libraries:
libpcre: 8.00 2009-10-19 (compiled with 8.00)
openssl: OpenSSL 0.9.8n 24 Mar 2010 (compiled with OpenSSL 0.9.8n 24 Mar 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: fabian@build-x86-macosx (x86_64-apple-darwin9.8.0)
Compilation: gcc -O2
Linking : /Volumes/scratch/gentoo/x86_64/usr/bin/x86_64-apple-darwin9-ld
Problem is bit-agnostic, and seems to have multiple heads.
- physical memory size is not detected
instead an obsolete and completely wrong code path is being used, hence physical max memory is never available on Mac OS X (at least <10.6)
- datasize check is questionable
datasize on OSX defaults to 6MB, seems not to be enforced
datasize is ignored by Linux OS
datasize is aggressively enforced by Solaris OS
- with a forced artificial amount of 4GiB, starting still fails on OSX
GDKvmalloc(196608) fails, try to free up space [memory in use=24,virtual memory in use=0]
GDKvmalloc(196608) result [mem=24,vm=0]
!FATAL: GDKvmalloc: failed for 196608 bytes
## Comment 14150
Date: 2010-06-29 19:55:21 +0200
From: @grobian
Problem is reproducable on other Mac 10.5 systems.
Real problem is the termination of mserver5 (gdk) with GDKvmalloc errors.
## Comment 14151
Date: 2010-06-30 10:32:13 +0200
From: @grobian
Feb2010 release worked:
% /var/tmp/MoneDB-Feb2010-install/bin/mserver5
MonetDB server v5.18.5, based on kernel v1.36.5
Serving database 'demo', using 8 threads
Compiled for i386-apple-darwin9.8.0/32bit with 32bit OIDs dynamically linked
Found 6.000 MiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /var/tmp/MonetDB-Feb2010-install/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>io.print("hello");
[ "hello" ]
>
(Note, the 6MiB is due to a datasize limitation set by default on any Mac)
## Comment 14152
Date: 2010-06-30 10:36:54 +0200
From: @grobian
without the datasize limitation, the Feb2010 release also detects memory correctly on the mac:
% /var/tmp/MonetDB-Feb2010-install/bin/mserver5 --version
MonetDB server v5.18.5 (32-bit), based on kernel v1.36.5 (32-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 4.0GiB available memory, 8 available cpu cores
Configured for prefix: /var/tmp/MonetDB-Feb2010-install
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8n 24 Mar 2010 (compiled with OpenSSL 0.9.8n 24 Mar 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: fabian@build-x86-macosx (i386-apple-darwin9.8.0)
Compilation: gcc -O2
Linking : /Volumes/scratch/gentoo/usr/bin/i686-apple-darwin9-ld
## Comment 14153
Date: 2010-06-30 13:01:36 +0200
From: @grobian
cause found:
changeset [57878a477b7c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=57878a477b7c)
MAP_ANONYMOUS instead of MAP_ANON
Seems MAP_ANONYMOUS exists, but causes failures on OSX. Backing out the changeset makes mserver start again regardless settings of datasize.
## Comment 14156
Date: 2010-06-30 14:22:58 +0200
From: @sjoerdmullender
Changeset [6af87f2fd50f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6af87f2fd50f) 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=6af87f2fd50f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6af87f2fd50f)
Changeset description:
Define MAP_ANONYMOUS as MAP_ANON in case it doesn't exist.
This hopefully fixes bug #2565.
| mserver5 fails to start due to fatal GDKvmalloc errors | https://api.github.com/repos/MonetDB/MonetDB/issues/2565/comments | 0 | 2020-11-30T11:03:31Z | 2024-06-27T11:47:48Z | https://github.com/MonetDB/MonetDB/issues/2565 | 753,379,509 | 2,565 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-27 10:11:13 +0200
From: @drstmane
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
Last updated: 2015-03-23 08:45:58 +0100
## Comment 14141
Date: 2010-06-27 10:11:13 +0200
From: @drstmane
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9
Build Identifier:
The SQL optimizer tries to re-order group-by columns such that, e.g., an ordered column is used first. However, this seems to work only, is the group-by columns also appear in the projection, i.e., in the select clause, as ,e.g., in
select count(*) as c,"objID","NeighborObjID" from neighbors group by "objID","NeighborObjID";
In case the group-by columsn are omitted from the projection, as ,e.g., in
select count(*) as c from neighbors group by "objID","NeighborObjID";
this re-ordering fails, as score_gbe() in sql/src/server/rel_optimizer.mx fails to locate the column in the projection list, and hence fails to locate the columns BAT and thus cannot find out whether it is sorted or not.
In fact, even if the group-by columns appear in the projection of the (sub-)query with the group-by but not in the enclosing (super-)query, score_gbe() fails to find the BATs; e.g.,
select count(c), sum(c), min(c), max(c) from (select count(*) as c,"objID","NeighborObjID" from neighbors group by "objID","NeighborObjID") as t;
A possible solution could IMHO be to have function score_gbe() (or related code) use the columns of the tables in the from clause to find the BATs that store the group-by columns.
Reproducible: Always
### Steps to Reproduce:
Start server, connect with SQL client and then:
1.
Create table:
CREATE TABLE "sys"."neighbors" (
"objID" bigint NOT NULL,
"NeighborObjID" bigint NOT NULL,
);
2.
Insert data such that column "objID" is sorted, but column "NeighborObjID" is not:
insert into neighbors values (1,2);
insert into neighbors values (2,1);
insert into neighbors values (3,3);
3.
Disable mitosis for easier inspection of MAL plan:
set optimizer='nov2009_pipe';
4.
Check MAL plan:
explain select count(*) as c from neighbors group by "objID","NeighborObjID";
### Actual Results:
MAL plan first groups (group.new()) on non-ordered "NeighborObjId" and then (group.done()) on ordered "objID".
### Expected Results:
MAL plan first groups (group.new()) on ordered "objId" and then (group.done()) on non-ordered "NeighborObjID".
This is potentially a major performance bug.
## Comment 14142
Date: 2010-06-27 11:01:49 +0200
From: @drstmane
Would the following be a suitable patch to fall back to plain column name of the underlying table in case there is no alias found in the projection list?
diff -r 7297d3bfa229 sql/src/server/rel_optimizer.mx
--- a/sql/src/server/rel_optimizer.mx Sat Jun 26 15:53:41 2010 +0200
+++ b/sql/src/server/rel_optimizer.mx Sun Jun 27 11:00:24 2010 +0200
@@ -112,8 +112,10 @@
case op_groupby:
if (!rel->exps)
break;
alias = exps_bind_column(rel->exps, name, NULL);
+ if (!alias)
+ return name_find_column( rel->l, rname, name);
break;
case op_insert:
case op_update:
case op_delete:
## Comment 14143
Date: 2010-06-27 11:29:32 +0200
From: @drstmane
Alternatively, we could first check for plain columns and only then fall back to aliases:
diff -r 7297d3bfa229 sql/src/server/rel_optimizer.mx
--- a/sql/src/server/rel_optimizer.mx Sat Jun 26 15:53:41 2010 +0200
+++ b/sql/src/server/rel_optimizer.mx Sun Jun 27 11:28:37 2010 +0200
@@ -112,6 +112,9 @@
case op_groupby:
if (!rel->exps)
break;
+ c = name_find_column( rel->l, rname, name);
+ if (c)
+ return c;
alias = exps_bind_column(rel->exps, name, NULL);
break;
case op_insert:
## Comment 14144
Date: 2010-06-27 13:32:57 +0200
From: @drstmane
Both patch appear to solve the reported problem, while not changing the testing status, i.e., tests that failed before still fail, tests that worked fine before still work fine (both with Feb2010 & Jun2010).
However, I'll wait for Niels' comments before checking in either patch, as I'm not familiar enough with the respective code to judge the semantic consequences of either patch.
## Comment 14154
Date: 2010-06-30 13:25:48 +0200
From: @drstmane
I decided to checkin my first patch, i.e., in case a group by column is not found as alias in teh projection list, we fall back to checking the columns of the input table:
changeset: 36472:44c969f6d7fd
branch: Jun2010
user: Stefan Manegold <Stefan.Manegold@cwi.nl>
date: Wed Jun 30 12:43:27 2010 +0200
files: sql/src/server/rel_optimizer.mx
description:
fixing bug #2564:
in case group by column is not found as alias in projection list,
fall back to check plain input columns
in order to find the underlying BAT and check its sortedness
## Comment 14155
Date: 2010-06-30 13:26:19 +0200
From: @drstmane
TODO:
A test needs to be added before closing this bug report.
## Comment 14284
Date: 2010-07-09 12:34:20 +0200
From: @grobian
Would a PLAN or EXPLAIN query be suitable for testing this?
## Comment 14361
Date: 2010-07-10 19:38:47 +0200
From: @drstmane
Changeset [7f15fd046eb2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7f15fd046eb2) 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=7f15fd046eb2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7f15fd046eb2)
Changeset description:
added test for bug #2564
## Comment 17028
Date: 2012-02-29 01:23:26 +0100
From: @drstmane
Changeset [1a611d986944](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1a611d986944) 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=1a611d986944](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1a611d986944)
Changeset description:
group-by_ordered_column.Bug-2564: propagated changesets [4a59b28b5528](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4a59b28b5528) & [8ee024048e42](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8ee024048e42) to 32bit output
## Comment 17034
Date: 2012-03-01 09:24:31 +0100
From: @drstmane
Changeset [f713c9890bc5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f713c9890bc5) 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=f713c9890bc5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f713c9890bc5)
Changeset description:
group-by_ordered_column.Bug-2564: fixed 32-bit output
## Comment 18647
Date: 2013-03-25 10:36:13 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [5a5636ffd264](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5a5636ffd264) 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=5a5636ffd264](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5a5636ffd264)
Changeset description:
group-by_ordered_column.Bug-2564: re-aligned 32-bit output:
propagated changesets [b3ad7b2f063f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b3ad7b2f063f) [5b102f303d89](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5b102f303d89) [4d2f0aaa57f1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4d2f0aaa57f1) [2e1ec897300f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2e1ec897300f)
to 32-bit output
## Comment 19029
Date: 2013-08-19 07:19:32 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [2170ee8bb0f0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2170ee8bb0f0) 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=2170ee8bb0f0](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=2170ee8bb0f0)
Changeset description:
group-by_ordered_column.Bug-2564: propagated changeset [7dbbc71e5a3f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7dbbc71e5a3f) to 32-bit output
## Comment 19121
Date: 2013-09-04 09:45:32 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [ba7000fa9013](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ba7000fa9013) 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=ba7000fa9013](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ba7000fa9013)
Changeset description:
group-by_ordered_column.Bug-2564: propagated changeset [22fcf0f73d51](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=22fcf0f73d51) to 32-bit output
## Comment 20738
Date: 2015-03-23 08:45:58 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [b85936ed9060](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b85936ed9060) 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=b85936ed9060](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b85936ed9060)
Changeset description:
group-by_ordered_column.Bug-2564: propagated 7 recent changesets to 32-bit output:
7ed1f3fd23d6 [6409eff6000d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6409eff6000d) [4a6c4bf6f77d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4a6c4bf6f77d) [487cb3d637ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=487cb3d637ff) [0a99b61c5a13](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0a99b61c5a13) [98036860e94b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=98036860e94b) [22120f327102](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=22120f327102)
| group-by column ordering fails if group-by columns are not in projection | https://api.github.com/repos/MonetDB/MonetDB/issues/2564/comments | 0 | 2020-11-30T11:03:27Z | 2024-06-27T11:47:47Z | https://github.com/MonetDB/MonetDB/issues/2564 | 753,379,464 | 2,564 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-22 21:00:39 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @njnes
Last updated: 2010-08-20 14:04:07 +0200
## Comment 14139
Date: 2010-06-22 21:00:39 +0200
From: @skinkie
Query: select *;
Results in:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe3dd6710 (LWP 16546)]
0x00007fffe46a37fb in rel_projections (sql=0x1482048, rel=0x0, tname=0x0, settname=1, intern=0) at ../../../src/server/rel_select.mx:394
394 if (is_subquery(rel) && is_project(rel->op))
(gdb) bt
0 0x00007fffe46a37fb in rel_projections (sql=0x1482048, rel=0x0, tname=0x0, settname=1, intern=0) at ../../../src/server/rel_select.mx:394
1 0x00007fffe46a32f4 in rel_table_projections (sql=0x1482048, rel=0xef2538, tname=0x0) at ../../../src/server/rel_select.mx:259
2 0x00007fffe46b104c in rel_table_exp (sql=0x1482048, rel=0xef2538, column_e=0x1527b68) at ../../../src/server/rel_select.mx:4202
3 0x00007fffe46b122f in rel_simple_select (sql=0x1482048, rel=0xef2538, where=0x0, selection=0x1527b88, distinct=0) at ../../../src/server/rel_select.mx:4248
4 0x00007fffe46b2ecf in rel_query (sql=0x1482048, rel=0x0, sq=0x1527cb8, toplevel=1, ek=...) at ../../../src/server/rel_select.mx:4708
5 0x00007fffe46b4377 in rel_subquery (sql=0x1482048, rel=0x0, sq=0x1527cb8, ek=...) at ../../../src/server/rel_select.mx:5054
6 0x00007fffe46b43f1 in rel_selects (sql=0x1482048, s=0x1527cb8) at ../../../src/server/rel_select.mx:5065
7 0x00007fffe46a29f2 in rel_semantic (sql=0x1482048, s=0x1527cb8) at ../../../src/server/rel_semantic.mx:336
8 0x00007fffe46084b3 in sql_symbol2stmt (c=0x1482048, sym=0x1527cb8) at ../../../../src/backends/monet5/sql.mx:1362
9 0x00007fffe46545e6 in SQLparser (c=0x605878) at ../../../../src/backends/monet5/sql_scenario.mx:1275
10 0x00007ffff7b04aa6 in runPhase (c=0x605878, phase=1) at ../../../src/mal/mal_scenario.mx:604
11 0x00007ffff7b04bde in runScenarioBody (c=0x605878) at ../../../src/mal/mal_scenario.mx:646
12 0x00007ffff7b04e65 in runScenario (c=0x605878) at ../../../src/mal/mal_scenario.mx:682
13 0x00007ffff7ab92af in MSserveClient (dummy=0x605878) at ../../../src/mal/mal_session.mx:473
14 0x00007ffff57a9547 in start_thread () from /lib/libpthread.so.0
15 0x00007ffff48db28d in clone () from /lib/libc.so.6
Happens in older versions as well as current development.
## Comment 14184
Date: 2010-07-02 11:30:27 +0200
From: @skinkie
Not fixed in development; nor did you mentioned a revision of the fix, so probably not committed.
## Comment 14189
Date: 2010-07-02 13:19:04 +0200
From: @njnes
Changeset [602b15e3d588](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=602b15e3d588) 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=602b15e3d588](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=602b15e3d588)
Changeset description:
fixed bug #2563
added check against empty projection
## Comment 14192
Date: 2010-07-02 13:25:49 +0200
From: @grobian
Fixed in Jun2010 branch
## Comment 14193
Date: 2010-07-02 13:27:48 +0200
From: @skinkie
Confirmed. I do suggest a different error message. Currently:
Column expression Table '(null)' unknown.
Since select 1; select 'a'; are both allowed I wonder if the error should reflect the operators meaning.
| SELECT *; crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/2563/comments | 0 | 2020-11-30T11:03:24Z | 2024-06-27T11:47:46Z | https://github.com/MonetDB/MonetDB/issues/2563 | 753,379,418 | 2,563 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-21 11:09:44 +0200
From: @grobian
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
Last updated: 2010-06-24 11:20:15 +0200
## Comment 14129
Date: 2010-06-21 11:09:44 +0200
From: @grobian
Package cfitsio was not found in the pkg-config search path.
Perhaps you should add the directory containing `cfitsio.pc'
to the PKG_CONFIG_PATH environment variable
No package 'cfitsio' found
Package cfitsio was not found in the pkg-config search path.
Perhaps you should add the directory containing `cfitsio.pc'
to the PKG_CONFIG_PATH environment variable
No package 'cfitsio' found
This is a mere reminder that we probably call pkg-config not totally correctly here, as it is not good to confront the user with alarming "not found" messages while they aren't in any way harmful.
## Comment 14138
Date: 2010-06-22 16:35:31 +0200
From: @grobian
Changeset [30b07534802e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=30b07534802e) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30b07534802e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=30b07534802e)
Changeset description:
Fix warning emitted by pkg-config by first checking if the cfitsio package is installed at all.
This closes bug #2562.
I cannot login to bugzilla right now, hence I cannot close the bug.
| pkg-config errors during configure | https://api.github.com/repos/MonetDB/MonetDB/issues/2562/comments | 0 | 2020-11-30T11:03:21Z | 2024-06-27T11:47:45Z | https://github.com/MonetDB/MonetDB/issues/2562 | 753,379,374 | 2,562 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-18 03:16:40 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @njnes
Last updated: 2010-11-15 09:39:03 +0100
## Comment 14119
Date: 2010-06-18 03:16:40 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
CREATE TABLE "sys"."kvk" (
"id" serial,
"kvk" bigint,
"bedrijfsnaam" varchar(256),
"adres" varchar(64),
"postcode" char(6),
"plaats" varchar(32),
"type" varchar(14),
"kvks" int,
"sub" int,
"bedrijfsnaam_size" smallint,
"adres_size" smallint
);
CREATE TABLE "sys"."anbi" (
"naam" varchar(128),
"vestigingsplaats" varchar(64),
"beschikking" date,
"einddatum" date,
"intrekking" date
);
select bedrijfsnaam, plaats, kvks from kvk,anbi where bedrijfsnaam in (anbi.naam);
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /opt/monetdb-testing/bin/mserver5 --set mapi_port=510000
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffee5b4710 (LWP 21028)]
MonetDB server v5.21.0, based on kernel v1.39.0
Serving database 'demo', using 2 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 3.865 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /opt/monetdb-testing/etc/monetdb5.conf)
[New Thread 0x7fffe41d8710 (LWP 21029)]
Listening for connection requests on mapi:monetdb://127.0.0.1:510000/
MonetDB/SQL module v2.39.0 loaded
[New Thread 0x7fffe3fd7710 (LWP 21030)]
>[New Thread 0x7fffe3dd6710 (LWP 21032)]
[New Thread 0x7fffe3bd5710 (LWP 21033)]
[New Thread 0x7fffe39d4710 (LWP 21034)]
mserver5: ../../../src/server/rel_select.mx:742: rel_lastexp: Assertion `list_length(rel->exps)' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffe3dd6710 (LWP 21032)]
0x00007ffff4839445 in raise () from /lib/libc.so.6
(gdb) bt
0 0x00007ffff4839445 in raise () from /lib/libc.so.6
1 0x00007ffff483a941 in abort () from /lib/libc.so.6
2 0x00007ffff48326a0 in __assert_fail () from /lib/libc.so.6
3 0x00007fffe46a478f in rel_lastexp (sql=0x13c2cf8, rel=0xb5db18) at ../../../src/server/rel_select.mx:742
4 0x00007fffe46ab514 in rel_logical_exp (sql=0x13c2cf8, rel=0xb5db18, sc=0x1490018, f=1) at ../../../src/server/rel_select.mx:2726
5 0x00007fffe46b1b09 in rel_select_exp (sql=0x13c2cf8, rel=0xb5db18, outer=0x0, sn=0x1490118, ek=...) at ../../../src/server/rel_select.mx:4406
6 0x00007fffe46b2ef8 in rel_query (sql=0x13c2cf8, rel=0x0, sq=0x1490118, toplevel=1, ek=...) at ../../../src/server/rel_select.mx:4711
7 0x00007fffe46b4377 in rel_subquery (sql=0x13c2cf8, rel=0x0, sq=0x1490118, ek=...) at ../../../src/server/rel_select.mx:5054
8 0x00007fffe46b43f1 in rel_selects (sql=0x13c2cf8, s=0x1490118) at ../../../src/server/rel_select.mx:5065
9 0x00007fffe46a29f2 in rel_semantic (sql=0x13c2cf8, s=0x1490118) at ../../../src/server/rel_semantic.mx:336
10 0x00007fffe46084b3 in sql_symbol2stmt (c=0x13c2cf8, sym=0x1490118) at ../../../../src/backends/monet5/sql.mx:1362
11 0x00007fffe46545e6 in SQLparser (c=0x605878) at ../../../../src/backends/monet5/sql_scenario.mx:1275
12 0x00007ffff7b04aa6 in runPhase (c=0x605878, phase=1) at ../../../src/mal/mal_scenario.mx:604
13 0x00007ffff7b04bde in runScenarioBody (c=0x605878) at ../../../src/mal/mal_scenario.mx:646
14 0x00007ffff7b04e65 in runScenario (c=0x605878) at ../../../src/mal/mal_scenario.mx:682
15 0x00007ffff7ab92af in MSserveClient (dummy=0x605878) at ../../../src/mal/mal_session.mx:473
16 0x00007ffff57a9547 in start_thread () from /lib/libpthread.so.0
17 0x00007ffff48db28d in clone () from /lib/libc.so.6
Query: "select bedrijfsnaam, plaats, kvks from kvk where bedrijfsnaam in (select naam from anbi);" seems to work.
Reproducible: Always
MonetDB server v5.21.0 (64-bit), based on kernel v1.39.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-testing
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: skinkie@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
## Comment 14131
Date: 2010-06-21 19:13:21 +0200
From: @njnes
added test to in_column_exp.Bug-2561.sql
fixed crash (added missing projection)
## Comment 14133
Date: 2010-06-21 19:16:18 +0200
From: @grobian
was fixed on default, hence will only show up on next feature release (after Jun2010)
| rel_lastexp: Assertion `list_length(rel->exps)' failed | https://api.github.com/repos/MonetDB/MonetDB/issues/2561/comments | 0 | 2020-11-30T11:03:18Z | 2024-06-27T11:47:44Z | https://github.com/MonetDB/MonetDB/issues/2561 | 753,379,346 | 2,561 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-18 02:40:52 +0200
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2010-08-20 14:04:02 +0200
## Comment 14118
Date: 2010-06-18 02:40:52 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
I have upgraded from:
MonetDB server v5.19.0, based on kernel v1.37.0
to
MonetDB server v5.21.0, based on kernel v1.39.0
First I shutdown the database cleanly. After that I restarted the database. Which for all running database resulted in the following error:
MonetDB server v5.21.0, based on kernel v1.39.0
Serving database 'demo', using 2 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 3.865 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /opt/monetdb-head/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50002/
MonetDB/SQL module v2.39.0 loaded
mserver5: ../../../../src/storage/bat/bat_table.mx:94: delta_full_bat_: Assertion `b->T->type == i->T->type' failed.
Aborted
Switching back to the previous compiled version worked for me. And serves files again. Now I do wonder, given the error above; and my up-to-date msqldump's I could fillup a new database, but that might potentially inhibit the same behavior as above.
Since I can't find any reference to the error message, or written comments about a significant change of the deltabats in the Changelogs that make them incompatible with previous versions I'm not going to try my luck on that.
Reproducible: Always
MonetDB server v5.19.0 (64-bit), based on kernel v1.37.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-head
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.00)
openssl: OpenSSL 0.9.8n 24 Mar 2010 (compiled with OpenSSL 0.9.8n 24 Mar 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: root@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
MonetDB server v5.21.0 (64-bit), based on kernel v1.37.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 3.9GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb-head
Libraries:
libpcre: 8.02 2010-03-19 (compiled with 8.02)
openssl: OpenSSL 0.9.8o 01 Jun 2010 (compiled with OpenSSL 0.9.8o 01 Jun 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: skinkie@openkvk (x86_64-unknown-linux-gnu)
Compilation: gcc -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
(version was run after moving around the newer version, the kernel version is thus wrong)
## Comment 14121
Date: 2010-06-18 17:37:49 +0200
From: @sjoerdmullender
Was the upgraded version before or after the push of changeset [4dd1701e7f19](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4dd1701e7f19) on June 7?
That changeset contains code to convert a SQL catalog from the format compatible with the Feb2010 release to one compatible with the upcoming Jun2010 release.
If your database was created with a version of the Jun2010 branch from before the change to the catalog, and your version of the default branch is from before the addition of the conversion code, then that may well be the problem.
## Comment 14122
Date: 2010-06-18 17:45:52 +0200
From: @skinkie
(In reply to comment 1)
> Was the upgraded version before or after the push of changeset [4dd1701e7f19](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=4dd1701e7f19) on
> June 7?
It was the last version in CVS, thus before the switch to HG.
> That changeset contains code to convert a SQL catalog from the format
> compatible with the Feb2010 release to one compatible with the upcoming Jun2010
> release.
> If your database was created with a version of the Jun2010 branch from before
> the change to the catalog, and your version of the default branch is from
> before the addition of the conversion code, then that may well be the problem.
I guess it is possible to detect what version the user is running on disk. Wouldn't a check between the on disk version be better, in addition to a potential 'upgrade' between versions?
## Comment 14130
Date: 2010-06-21 11:40:40 +0200
From: @grobian
Seems like this happened to me on current too. The same database worked 10 minutes ago, only difference is in mapreduce optimiser, which isn't even invoked at this stage.
MonetDB server v5.21.0, based on kernel v1.39.0
Serving database 'qn1', using 4 threads
Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 7.751 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
[New Thread 0x7fffde8df710 (LWP 10565)]
Listening for UNIX domain connection requests on mapi:monetdb:///ufs/fabian/scratch/monetdb/current/program-x86_64/var/MonetDB5/dbfarm/qn1/.mapi.sock
MonetDB/SQL module v2.39.0 loaded
mserver5: /ufs/fabian/scratch/monetdb/current/sql/src/storage/bat/bat_table.mx:94: delta_full_bat_: Assertion `b->T->type == i->T->type' failed.
Program received signal SIGABRT, Aborted.
0x00000037d98326c5 in raise () from /lib64/libc.so.6
(gdb) bt
0 0x00000037d98326c5 in raise () from /lib64/libc.so.6
1 0x00000037d9833ea5 in abort () from /lib64/libc.so.6
2 0x00000037d982b7b5 in __assert_fail () from /lib64/libc.so.6
3 0x00007fffdedfa0a1 in delta_full_bat_ (c=0x1255b78, bat=0x1255c48, temp=0,
d=0x623c98, s=0x0)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/bat/bat_table.mx:94
4 0x00007fffdedfa2ac in delta_full_bat (c=0x1255b78, bat=0x1255c48, temp=0,
d=0x623c98, s=0x0)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/bat/bat_table.mx:120
5 0x00007fffdedfa31a in full_column (c=0x1255b78, d=0x623c98, s=0x0)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/bat/bat_table.mx:126
6 0x00007fffdedfa87e in column_find_value (tr=0x124ef88, c=0x1255b78,
rid=131)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/bat/bat_table.mx:180
7 0x00007fffdede9211 in load_column (tr=0x124ef88, t=0x12cd028, rid=131)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/store.mx:527
8 0x00007fffdede996b in load_table (tr=0x124ef88, s=0x124f008, rid=131)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/store.mx:605
9 0x00007fffdedeb1c6 in load_schema (tr=0x124ef88, id=2153, rid=19)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/store.mx:884
10 0x00007fffdedeb60a in load_trans (tr=0x124ef88, id=2153)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/store.mx:936
11 0x00007fffdededde1 in store_init (debug=0, store=store_bat,
---Type <return> to continue, or q <return> to quit---
logdir=0x7fffdee340d8 "sql_logs", dbname=0x63a558 "qn1", stk=0)
at /ufs/fabian/scratch/monetdb/current/sql/src/storage/store.mx:1467
12 0x00007fffded9fea7 in mvc_init (dbname=0x63a558 "qn1", debug=0,
store=store_bat, stk=0)
at /ufs/fabian/scratch/monetdb/current/sql/src/server/sql_mvc.mx:289
13 0x00007fffded58d4a in SQLinit ()
at /ufs/fabian/scratch/monetdb/current/sql/src/backends/monet5/sql_scenario.mx:277
14 0x00007fffded589a9 in SQLprelude ()
at /ufs/fabian/scratch/monetdb/current/sql/src/backends/monet5/sql_scenario.mx:201
15 0x00007ffff7ce5a22 in runMALsequence (cntxt=0x605560, mb=0x635548,
startpc=1, stoppc=0, stk=0x7fffffff3020, env=0x0, pcicaller=0x0)
at /ufs/fabian/scratch/monetdb/current/five/src/mal/mal_interpreter.mx:1912
16 0x00007ffff7cd9e61 in runMAL (cntxt=0x605560, mb=0x635548, startpc=1,
mbcaller=0x0, env=0x0, pcicaller=0x0)
at /ufs/fabian/scratch/monetdb/current/five/src/mal/mal_interpreter.mx:349
17 0x00007ffff7cd8c59 in MALengine (c=0x605560)
at /ufs/fabian/scratch/monetdb/current/five/src/mal/mal_session.mx:667
18 0x00007ffff7cd7355 in malBootstrap ()
at /ufs/fabian/scratch/monetdb/current/five/src/mal/mal_session.mx:95
19 0x00007ffff7cc683e in mal_init ()
at /ufs/fabian/scratch/monetdb/current/five/src/mal/mal.mx:377
---Type <return> to continue, or q <return> to quit---
20 0x000000000040339b in main (argc=16, av=0x7fffffffd728)
at /ufs/fabian/scratch/monetdb/current/five/src/tools/mserver5.mx:624
(gdb)
(gdb)
## Comment 14132
Date: 2010-06-21 19:15:53 +0200
From: @njnes
indeed the head changed, ie making the db incompatible. This may always happen on the head. (reason for this was a fix of the type of the storage column)
| After shutdown and upgrade delta_full_bat_ assertion failed | https://api.github.com/repos/MonetDB/MonetDB/issues/2560/comments | 0 | 2020-11-30T11:03:15Z | 2024-06-28T13:21:56Z | https://github.com/MonetDB/MonetDB/issues/2560 | 753,379,295 | 2,560 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-18 02:14:08 +0200
From: @skinkie
To: buildtools devs <<bugs-buildtools>>
Version: -- development
CC: mitja, @drstmane
Last updated: 2010-07-07 09:04:29 +0200
## Comment 14117
Date: 2010-06-18 02:14:08 +0200
From: @skinkie
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.55 Safari/533.4
Build Identifier:
Thus the detection of the version of libtool fails. I was so kind to resolve the issue and to create a patch:
diff -r [2ec4097dee10](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=2ec4097dee10) buildtools/conf/Mbootstrap.in
--- a/buildtools/conf/Mbootstrap.in Thu Jun 17 22:38:36 2010 +0200
+++ b/buildtools/conf/Mbootstrap.in Fri Jun 18 02:00:29 2010 +0200
@@ -111,7 +111,7 @@
echo "Please get it at eg. http://www.gnu.org/software/libtool/." >&2
exit 1
fi
-LT_VERSION=`$LIBTOOL --version 2>/dev/null | sed -n '/^ltmain\.sh/{s/([^)]*)//g;s/ltmain.sh//g;s/ //g;p;q;}'`
+LT_VERSION=`$LIBTOOL --version 2>/dev/null | sed -n '/^\(ltmain\.sh\|libtool\)/{s/([^)]*)//g;s/\(ltmain.sh\|libtool\)//g;s/ //g;p;q;}'`
_LT_VERSION=`echo $LT_VERSION | awk 'BEGIN { FS = "."; } { printf "%d", ($1 * 1000 + $2) * 1000 + $3;}'`
_REQ_LT_VERSION=`echo $REQ_LT_VERSION | awk 'BEGIN { FS = "."; } { printf "%d", ($1 * 1000 + $2) * 1000 + $3;}'`
Reproducible: Always
## Comment 14187
Date: 2010-07-02 12:20:45 +0200
From: @grobian
I assume you encounter this when you bootstrap yourself?
## Comment 14188
Date: 2010-07-02 13:09:17 +0200
From: @skinkie
Your assumption is well founded considering I selected version development.
## Comment 14194
Date: 2010-07-02 14:18:30 +0200
From: @drstmane
Stefan
could you please provide the virgin output of the following commands on your system:
type -a glibtool
type -a glibtoolize
type -a libtool
libtool --version
?
That might allow us to verify your patch.
Thanks.
Stefan
## Comment 14195
Date: 2010-07-02 14:21:18 +0200
From: @skinkie
skinkie@openkvk ~ $ type -a glibtool
-bash: type: glibtool: not found
skinkie@openkvk ~ $ type -a glibtoolize
-bash: type: glibtoolize: not found
skinkie@openkvk ~ $ type -a libtool
libtool is /usr/bin/libtool
skinkie@openkvk ~ $ libtool --version
libtool (GNU libtool) 2.2.10
Written by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
Copyright (C) 2010 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
## Comment 14197
Date: 2010-07-02 14:40:40 +0200
From: @grobian
I guess the patch is fine. I don't use Mbootstrap (but an eautoreconf-alike function), so libtool-2.2.10 behaves fine for me.
## Comment 14201
Date: 2010-07-02 15:11:48 +0200
From: @skinkie
(In reply to comment 5)
> I guess the patch is fine. I don't use Mbootstrap (but an eautoreconf-alike
> function), so libtool-2.2.10 behaves fine for me.
If you have a different way of compiling. Mitja will be interested.
## Comment 14202
Date: 2010-07-02 15:15:01 +0200
From: @grobian
I just bootstrap the sources using standard autoconf commands, not using the patching and sedding tricks performed by Mbootstrap.
in short:
* Running autogen ...
* Running aclocal -I . -I /ufs/fabian/scratch/monetdb/current/program-x86_64/sh
are/MonetDB (1.11.1) ...
* Running libtoolize --copy --force --automake (2.2.10) ...
* Running aclocal -I . -I /ufs/fabian/scratch/monetdb/current/program-x86_64/sh
are/MonetDB (1.11.1) ...
* Running autoconf (2.65) ...
* Running autoheader (2.65) ...
* Running automake --add-missing --copy (1.11.1) ...
## Comment 14221
Date: 2010-07-06 07:30:01 +0200
From: @drstmane
Changeset [a7a0e0845e56](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a7a0e0845e56) 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=a7a0e0845e56](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a7a0e0845e56)
Changeset description:
fixing bug #2559 "libtool-2.2.10 is not called ltmain.sh anymore"
Apparently, (at least) as of libtool 2.2.10, libtool calls itself
no longer "ltmain.sh" but "libtool" in its own `--version` output;
hence, we need to adapt our version analysis in Mbootstrap.in .
Thanks go to Stefan de Konink for reporting the problem and
providing a patch.
## Comment 14222
Date: 2010-07-06 07:31:24 +0200
From: @drstmane
Changeset [b1df4a254d3e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b1df4a254d3e) 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=b1df4a254d3e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b1df4a254d3e)
Changeset description:
merge with Feb2010:
fixing bug #2559 "libtool-2.2.10 is not called ltmain.sh anymore"
Apparently, (at least) as of libtool 2.2.10, libtool calls itself
no longer "ltmain.sh" but "libtool" in its own `--version` output;
hence, we need to adapt our version analysis in Mbootstrap.in .
Thanks go to Stefan de Konink for reporting the problem and
providing a patch.
## Comment 14223
Date: 2010-07-06 08:53:36 +0200
From: @drstmane
Fixed in HG (Feb2010, Jun2010 & default).
Will be tested nightly on our MacOS X (Darwin) machine with Gentoo prefix.
## Comment 14233
Date: 2010-07-07 09:04:29 +0200
From: @drstmane
FYI:
changeset: 36593:145bd8a5adaf
branch: Feb2010
parent: 36573:1e2808a8e416
user: Stefan Manegold <Stefan.Manegold@cwi.nl>
date: Wed Jul 07 00:13:38 2010 +0200
files: buildtools/conf/Mbootstrap.in
description:
cope with (old) sed (e.g. on Solaris) that do not support "\(...\|...\)"
diff -r [1e2808a8e416](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1e2808a8e416) -r [145bd8a5adaf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=145bd8a5adaf) buildtools/conf/Mbootstrap.in
--- a/buildtools/conf/Mbootstrap.in Tue Jul 06 15:32:06 2010 +0200
+++ b/buildtools/conf/Mbootstrap.in Wed Jul 07 00:13:38 2010 +0200
@@ -111,7 +111,7 @@
echo "Please get it at eg. http://www.gnu.org/software/libtool/." >&2
exit 1
fi
-LT_VERSION=`$LIBTOOL --version 2>/dev/null | sed -n '/^\(ltmain\.sh\|libtool\)/{s/([^)]*)//g;s/\(ltmain\.sh\|libtool\)//g;s/ //g;p;q;}'`
+LT_VERSION=`$LIBTOOL --version 2>/dev/null | sed -n -e '/^ltmain\.sh/{s/([^)]*)//g;s/ltmain\.sh//g;s/ //g;p;q;}' -e '/^libtool/{s/([^)]*)//g;s/libtool//g;s/ //g;p;q;}'`
_LT_VERSION=`echo $LT_VERSION | awk 'BEGIN { FS = "."; } { printf "%d", ($1 * 1000 + $2) * 1000 + $3;}'`
_REQ_LT_VERSION=`echo $REQ_LT_VERSION | awk 'BEGIN { FS = "."; } { printf "%d", ($1 * 1000 + $2) * 1000 + $3;}'`
| libtool-2.2.10 is not called ltmain.sh anymore | https://api.github.com/repos/MonetDB/MonetDB/issues/2559/comments | 0 | 2020-11-30T11:03:12Z | 2024-06-27T11:47:42Z | https://github.com/MonetDB/MonetDB/issues/2559 | 753,379,256 | 2,559 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-17 12:19:19 +0200
From: @skinkie
To: clients devs <<bugs-clients>>
Version: -- development
CC: mitja, @drstmane
Last updated: 2010-08-30 09:18:01 +0200
## Comment 14114
Date: 2010-06-17 12:19:19 +0200
From: @skinkie
In favor to more simple types, the SQLROW* types have been replaced. Since there is no proper compilation check it fails. Since most users probably want to have their clients directory compiled under the newer unixODBC version instead care for a proper configuration check the following can be used to get the code compiled again:
diff -r [e7bbd5d0cd46](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e7bbd5d0cd46) clients/src/odbc/driver/ODBCStmt.h
--- a/clients/src/odbc/driver/ODBCStmt.h Wed Jun 16 17:02:29 2010 +0200
+++ b/clients/src/odbc/driver/ODBCStmt.h Thu Jun 17 12:12:31 2010 +0200
@@ -42,6 +42,9 @@
ifndef _H_ODBCSTMT
define _H_ODBCSTMT
+define SQLROWOFFSET SQLLEN
+define SQLROWSETSIZE SQLULEN
+
include "ODBCGlobal.h"
include "ODBCError.h"
include "ODBCDbc.h"
## Comment 14278
Date: 2010-07-09 11:16:22 +0200
From: @grobian
Please provide us a compilation failure/build log, as well as which version of unixODBC you have installed.
## Comment 14289
Date: 2010-07-09 12:51:39 +0200
From: @skinkie
The version of unixODBC is in the subject. The first compile error:
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../../src/odbc/driver -I../../.. -I../../../../src/odbc/driver -I../.. -I../../../../src/odbc/driver/../.. -I/opt/monetdb-testing/include/MonetDB -I/opt/monetdb-testing/include/MonetDB/common -I/opt/monetdb-testing/include/MonetDB/gdk -DLIBMONETODBC -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -c ../../../../src/odbc/driver/ODBCConvert.c -fPIC -DPIC -o .libs/libMonetODBC_la-ODBCConvert.o
In file included from ../../../../src/odbc/driver/ODBCConvert.c:21:
../../../../src/odbc/driver/ODBCStmt.h:83: error: expected specifier-qualifier-list before â
../../../../src/odbc/driver/ODBCConvert.c: In function â:
../../../../src/odbc/driver/ODBCConvert.c:978: error: â has no member named â
../../../../src/odbc/driver/ODBCConvert.c:979: error: â has no member named â
../../../../src/odbc/driver/ODBCConvert.c: In function â:
../../../../src/odbc/driver/ODBCConvert.c:2347: error: â has no member named â
../../../../src/odbc/driver/ODBCConvert.c:2348: error: â has no member named â
../../../../src/odbc/driver/ODBCConvert.c:2349: error: â has no member named â
../../../../src/odbc/driver/ODBCConvert.c:2350: error: â has no member named â
../../../../src/odbc/driver/ODBCConvert.c:2352: error: â has no member named â
make[7]: *** [libMonetODBC_la-ODBCConvert.lo] Fout 1
make[7]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc/driver' wordt verlaten
make[6]: *** [all] Fout 2
make[6]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc/driver' wordt verlaten
make[5]: *** [all-recursive] Fout 1
make[5]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc' wordt verlaten
make[4]: *** [all] Fout 2
make[4]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc' wordt verlaten
make[3]: *** [all-recursive] Fout 1
make[3]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux/src' wordt verlaten
make[2]: *** [all] Fout 2
make[2]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux/src' wordt verlaten
make[1]: *** [all-recursive] Fout 1
make[1]: Map '/home/skinkie/sources/monetdb-hg/clients/Linux' wordt verlaten
make: *** [all] Fout 2
## Comment 14291
Date: 2010-07-09 12:53:37 +0200
From: @grobian
Seems your paste got corrupted, the most important bits are missing. Please try again.
## Comment 14293
Date: 2010-07-09 12:57:16 +0200
From: @skinkie
make[7]: Entering directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc/driver'
/bin/sh ../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../../src/odbc/driver -I../../.. -I../../../../src/odbc/driver -I../.. -I../../../../src/odbc/driver/../.. -I/opt/monetdb-testing/include/MonetDB -I/opt/monetdb-testing/include/MonetDB/common -I/opt/monetdb-testing/include/MonetDB/gdk -DLIBMONETODBC -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -c -o libMonetODBC_la-ODBCConvert.lo `test -f 'ODBCConvert.c' || echo '../../../../src/odbc/driver/'`ODBCConvert.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../../src/odbc/driver -I../../.. -I../../../../src/odbc/driver -I../.. -I../../../../src/odbc/driver/../.. -I/opt/monetdb-testing/include/MonetDB -I/opt/monetdb-testing/include/MonetDB/common -I/opt/monetdb-testing/include/MonetDB/gdk -DLIBMONETODBC -Wall -Wextra -fno-strict-aliasing -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -c ../../../../src/odbc/driver/ODBCConvert.c -fPIC -DPIC -o .libs/libMonetODBC_la-ODBCConvert.o
In file included from ../../../../src/odbc/driver/ODBCConvert.c:21:
../../../../src/odbc/driver/ODBCStmt.h:83: error: expected specifier-qualifier-list before 'SQLROWOFFSET'
../../../../src/odbc/driver/ODBCConvert.c: In function 'ODBCFetch':
../../../../src/odbc/driver/ODBCConvert.c:978: error: 'ODBCStmt' has no member named 'ImplRowDescr'
../../../../src/odbc/driver/ODBCConvert.c:979: error: 'ODBCStmt' has no member named 'ApplRowDescr'
../../../../src/odbc/driver/ODBCConvert.c: In function 'ODBCStore':
../../../../src/odbc/driver/ODBCConvert.c:2347: error: 'ODBCStmt' has no member named 'ImplParamDescr'
../../../../src/odbc/driver/ODBCConvert.c:2348: error: 'ODBCStmt' has no member named 'ApplParamDescr'
../../../../src/odbc/driver/ODBCConvert.c:2349: error: 'ODBCStmt' has no member named 'ImplParamDescr'
../../../../src/odbc/driver/ODBCConvert.c:2350: error: 'ODBCStmt' has no member named 'ApplParamDescr'
../../../../src/odbc/driver/ODBCConvert.c:2352: error: 'ODBCStmt' has no member named 'ApplParamDescr'
make[7]: *** [libMonetODBC_la-ODBCConvert.lo] Error 1
make[7]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc/driver'
make[6]: *** [all] Error 2
make[6]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc/driver'
make[5]: *** [all-recursive] Error 1
make[5]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc'
make[4]: *** [all] Error 2
make[4]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src/odbc'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/skinkie/sources/monetdb-hg/clients/Linux'
make: *** [all] Error 2
## Comment 14475
Date: 2010-07-18 19:08:04 +0200
From: @drstmane
*** Bug #2625 has been marked as a duplicate of this bug. ***
## Comment 14476
Date: 2010-07-18 19:08:55 +0200
From: @drstmane
For a more detailed analysis see bug #2625 "ODBC driver fails to compile on
64-bit MacOS X with Gentoo Prefix and unixODBC 2.3".
## Comment 14482
Date: 2010-07-19 16:42:31 +0200
From: @sjoerdmullender
Changeset [1fcc26eb1124](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1fcc26eb1124) 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=1fcc26eb1124](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1fcc26eb1124)
Changeset description:
Get rid of SQLROWSETSIZE and SQLROWOFFSET.
This should fix bug #2558.
## Comment 14489
Date: 2010-07-20 08:07:07 +0200
From: @drstmane
Works fine, now, with the unixODBC 2.3 of the GentoPrefix on our MacOS X (Darwin 9.8.0) machine.
## Comment 14796
Date: 2010-08-30 09:18:01 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| unixODBC-2.3.0 removed SQLROWOFFSET and SQLROWSETSIZE | https://api.github.com/repos/MonetDB/MonetDB/issues/2558/comments | 0 | 2020-11-30T11:03:08Z | 2024-06-27T11:47:41Z | https://github.com/MonetDB/MonetDB/issues/2558 | 753,379,199 | 2,558 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-16 11:33:45 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 2.38.3 (Jun2010-SP1) [obsolete]
CC: @njnes, @drstmane
Last updated: 2010-08-30 09:18:04 +0200
## Comment 14113
Date: 2010-06-16 11:33:45 +0200
From: @grobian
sql/src/jdbc/tests/Test_JdbcClient fails with a foreign key constraint violation on 64-bits platforms. It succeeds on 32-bits platforms.
Error on line 11: SQLException:assert:INSERT INTO: FOREIGN KEY constraint 'foreign.foreign_subject_predicate_object_fkey' violated
Error on line 12: current transaction is aborted (please ROLLBACK)
## Comment 14244
Date: 2010-07-07 14:29:43 +0200
From: @drstmane
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_jdbc_tests/Test_JdbcClient.err.00.html
The test actually also fails on 32-bit Windows when compiled with Intel's icc:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/Int.32.32.d.1-Windows5.1/src_jdbc_tests/Test_JdbcClient.err.00.html
And test sql/src/test/BugDay_2005-10-06_2.8/Tests/MapiClient-dump.SF-905851.SQL.py shows the same behavior:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugDay_2005-10-06_2.8/MapiClient-dump.SF-905851.err.00.html
## Comment 14372
Date: 2010-07-12 19:05:02 +0200
From: @drstmane
(At least) on my 64-bit Fedora 12 desktop, both tests sql/src/jdbc/tests/Test_JdbcClient and sql/src/test/BugDay_2005-10-06_2.8/Tests/MapiClient-dump.SF-905851 work fine with the mitosis optimizer disabled, i.e., the problem is caused by the combination of mitosis and mergetable optimizers (most probably by the latter).
Niels, Sjoerd and me already found that, but have not yet been able to locate the actual bug inside mergetable, let fix it ...).
## Comment 14425
Date: 2010-07-15 19:22:49 +0200
From: @drstmane
Changeset [735b133ade47](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=735b133ade47) 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=735b133ade47](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=735b133ade47)
Changeset description:
make mitosis work (again) as it is supposed to work
This checkin is basically a selective back-port of the
mitosis & octopus related parts of the following two
multi-purpose changesets:
http://dev.monetdb.org/hg/MonetDB/rev/2a358751a4b6
(i.e.,
opt_support: provide a function to see if later in the pipeline there is a specific optimizer mentioned
opt_octopus: use the legibility test
) and
http://dev.monetdb.org/hg/MonetDB/rev/692eff15bea0
(i.e.,
mitosis should be more aware of octopus
)
Before this checkin, the mitosis logic to calculate the
number and size of the to be created partitions was in
fact disabled, overruled by OPTlegAdviceInternal(),
which alwasy only return the number of threads (GDKnr_threads),
even in case octopus was not activated or used at all.
Consequently, also the logic that made mitosis bail-out
without action if only 1 partition was to be created
(e.g., with small datasets on single-core machines
or when single-threaded execution is requested),
was in fact disabled.
With this checkin, OPTlegAdviceInternal() return a
value (supposely the number of legs to be used ---
currently still hard-wired to GDKnr_threads), only
if octopus is indeed available activated and used.
Otherwise, mitosis falls back to its own logic
of determening the number of partition to create
depending on the number of available threads,
the available memory and the data size.
Also, the mitosis (again) bails-out if it were
to create only a single partition.
On multi-core systems and without restricting the
number of threads to one, this checkin does not
change the behavior of any of the currently available
MonetDB5 or sql tests.
On single core systems or in case the number of threads
is restricted to only one, testing behavor changes in
that the following tests no work fine instead of failing:
sql/src/jdbc/tests/Tests/Test_JdbcClient.SQL.sh
sql/src/test/BugDay_2005-10-06_2.8/Tests/MapiClient-dump.SF-905851.SQL.py
(bug #2557 "SQLException:assert:INSERT INTO: FOREIGN KEY constraint violated on 64-bits")
sql/src/test/BugTracker/Tests/range_predicate.SF-1711242.sql
sql/src/test/BugTracker/Tests/variable_stack_crash.SF-1711251.sql
sql/src/test/BugTracker/Tests/variable_stack_crash.SF-1711251-2.sql
sql/src/test/bugs/Tests/innerjoin_between-bug-sf-960672.sql
(bug #2613 "SQL creates wrong MAL code a.o. with GDK_nr_threads=1")
Most probably, these test do work fine, now, as with a single
partition mitosis, and hence mergetable, do not trigger any more.
The first two tests (bug #2557) still fail in the multi-threaded case.
The latter four tests (bug #2613) did only fail in the single-threaded case,
and when compiled with Intels icc on a dual-core 64-bit Fedora 12 machine;
nightly testing will reveal the effect of this checkin for that case.
## Comment 14443
Date: 2010-07-16 18:56:31 +0200
From: @drstmane
potentially related bugs are
- bug #2613 "SQL creates wrong MAL code a.o. with GDK_nr_threads=1"
- bug #2596 "some TPCH tests fail with assertion in opt_mergetable on Windows"
## Comment 14470
Date: 2010-07-18 09:47:26 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_jdbc_tests/Test_JdbcClient.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugDay_2005-10-06_2.8/MapiClient-dump.SF-905851.err.00.html
## Comment 14573
Date: 2010-07-30 20:10:10 +0200
From: @njnes
Changeset [ef573cb4e212](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ef573cb4e212) 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=ef573cb4e212](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ef573cb4e212)
Changeset description:
Fixed bug #2557.
Mergetable didn't handle semijoin(x, mat) properly.
This gave (with multi key foreign key checks) too many parts.
## Comment 14802
Date: 2010-08-30 09:18:04 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| SQLException:assert:INSERT INTO: FOREIGN KEY constraint violated on 64-bits | https://api.github.com/repos/MonetDB/MonetDB/issues/2557/comments | 0 | 2020-11-30T11:03:05Z | 2024-06-27T11:47:40Z | https://github.com/MonetDB/MonetDB/issues/2557 | 753,379,154 | 2,557 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-14 12:43:41 +0200
From: maguila
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.1 (Jun2010) [obsolete]
Last updated: 2010-11-15 09:39:05 +0100
## Comment 14098
Date: 2010-06-14 12:43:41 +0200
From: maguila
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.1 (KHTML, like Gecko) Chrome/6.0.435.0 Safari/534.1
Build Identifier:
I'm trying to limit the memory that monetdb can use during its
executions. I'm using mal language and I've found this operation in
order to do it.
command mem_maxsize(v:lng) :void
address set_mem_maxsize
comment "Set the maximum usable amount of physical swapspace in KB.";
When I use this operation the connection is terminated.
I let here some examples: (I'm working with a machine with 32 GB)
mal>status.mem_maxsize(4294967296:lng);
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = status.mem_maxsize(4294967296:lng);
ERROR = !Connection terminated
mal>status.mem_maxsize(1073741824:lng);
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = status.mem_maxsize(1073741824:lng);
ERROR = !Connection terminated
mal>status.mem_maxsize(1048576:lng);
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = status.mem_maxsize(1048576:lng);
ERROR = !Connection terminated
Reproducible: Always
### Steps to Reproduce:
1.start mclient
2.and write --> status.mem_maxsize(1048576:lng);
### Actual Results:
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = status.mem_maxsize(1048576:lng);
ERROR = !Connection terminated
## Comment 14100
Date: 2010-06-14 14:52:30 +0200
From: @grobian
Changeset [191e5f0c892f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=191e5f0c892f) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=191e5f0c892f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=191e5f0c892f)
Changeset description:
Clean-up status module, fixes segfault from bug #2556 as side-effect.
## Comment 14101
Date: 2010-06-14 15:21:46 +0200
From: @grobian
The change that fixes this issue is too big to be considered a fix for the upcoming Jun2010 release. The issue as reported has been around for a long time, and will remain unfixed in the Jun2010 release. We decided to apply the fix for the next feature release after the Jun2010 release.
It is unlikely that this function does what you expect it to do, hence the low priority in fixing it. Simply don't use this function.
| mem_maxsize(v:lng) crash, trying to limit memory | https://api.github.com/repos/MonetDB/MonetDB/issues/2556/comments | 0 | 2020-11-30T11:03:02Z | 2024-06-27T11:47:39Z | https://github.com/MonetDB/MonetDB/issues/2556 | 753,379,103 | 2,556 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-13 02:06:13 +0200
From: hobury <<info>>
To: GDK devs <<bugs-common>>
Version: 1.36.5 (Feb2010-SP2) [obsolete]
CC: @drstmane
Last updated: 2010-08-20 14:03:49 +0200
## Comment 14090
Date: 2010-06-13 02:06:13 +0200
From: hobury <<info>>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100106 Firefox/3.5.7
Build Identifier:
Tried to install MonetDB-Feb2010-SuperBall-SP2.
The first error appears at:
gdk_system.c:141: error: storage size of 'rl' isn't known
Reproducible: Always
### Steps to Reproduce:
These are the steps to reproduce:
wget http://monetdb.cwi.nl/downloads/sources/Feb2010-SP2/MonetDB-Feb2010-SuperBall-SP2.tar.bz2
bunzip2 MonetDB-Feb2010-SuperBall-SP2.tar.bz2
tar -xf MonetDB-Feb2010-SuperBall-SP2.tar
cd MonetDB-Feb2010-SuperBall-SP2
./monetdb-install.sh --prefix=/usr/local --enable-sql --enable-xquery
This was attempted twice and after ensuring that sufficient disk space was available.
### Actual Results:
The errors appear as follows:
gdk_system.c: In function 'MT_init':
gdk_system.c:141: error: storage size of 'rl' isn't known
gdk_system.c:147: warning: implicit declaration of function 'getrlimit'
gdk_system.c:147: error: 'RLIMIT_DATA' undeclared (first use in this function)
gdk_system.c:147: error: (Each undeclared identifier is reported only once
gdk_system.c:147: error: for each function it appears in.)
gdk_system.c:148: error: 'RLIM_INFINITY' undeclared (first use in this function)
gmake[5]: *** [libbat_la-gdk_system.lo] Error 1
gmake[5]: Leaving directory `/var/tmp/MonetDB-1276382852/MonetDB/MonetDB/src/gdk'
gmake[4]: *** [all] Error 2
gmake[4]: Leaving directory `/var/tmp/MonetDB-1276382852/MonetDB/MonetDB/src/gdk'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/var/tmp/MonetDB-1276382852/MonetDB/MonetDB/src'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/var/tmp/MonetDB-1276382852/MonetDB/MonetDB/src'
gmake[1]: *** [all-recursive] Error 1
gmake[1]: Leaving directory `/var/tmp/MonetDB-1276382852/MonetDB/MonetDB'
gmake: *** [all] Error 2
making MonetDB failed
### Expected Results:
Normal termination of installation script.
uname -a
FreeBSD pcbsd-5885 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 10: Thu Jan 7 14:50:53 EST 2010 root@build8x64.pcbsd.org:/usr/obj/usr/pcbsd-build80/fbsd-source/8.0-src/sys/PCBSD amd64
## Comment 14091
Date: 2010-06-13 10:35:18 +0200
From: @grobian
Changeset [d3455d727e7f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d3455d727e7f) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d3455d727e7f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d3455d727e7f)
Changeset description:
include sys/time.h for FreeBSD for bug #2555, reorder includes such that the documentation matches
## Comment 14092
Date: 2010-06-13 10:41:48 +0200
From: @grobian
can you please attach your build logfile?
## Comment 14093
Date: 2010-06-13 16:07:05 +0200
From: hobury <<info>>
Created attachment 7
Log file
Redid the procedure on a clean install:
uname -a
FreeBSD pcbsd-7236 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 10: Thu Jan 7 14:50:53 EST 2010 root@build8x64.pcbsd.org:/usr/obj/usr/pcbsd-build80/fbsd-source/8.0-src/sys/PCBSD amd64v
> Attached file: [log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2555_log_7) (text/plain, 33343 bytes)
> Description: Log file
## Comment 14094
Date: 2010-06-13 16:13:22 +0200
From: @grobian
Changeset [360847a980da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=360847a980da) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=360847a980da](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=360847a980da)
Changeset description:
FreeBSD has both sysconf and getrlimit, though to use the latter, it needs sys/resource.h include. This should fix bug #2555
## Comment 14095
Date: 2010-06-13 16:19:54 +0200
From: @grobian
Changeset [6b333af0bc16](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6b333af0bc16) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6b333af0bc16](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6b333af0bc16)
Changeset description:
include sys/time.h for FreeBSD for bug #2555, reorder includes such that the documentation matches
(transplanted from d3455d727e7f05e5582cf85529658cbeb1a4e5d9)
## Comment 14096
Date: 2010-06-13 16:19:55 +0200
From: @grobian
Changeset [75848849b8db](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=75848849b8db) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=75848849b8db](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=75848849b8db)
Changeset description:
FreeBSD has both sysconf and getrlimit, though to use the latter, it needs sys/resource.h include. This should fix bug #2555
(transplanted from 360847a980da29d039dd7ebe036f6fb38f7d68b8)
## Comment 14097
Date: 2010-06-13 16:25:27 +0200
From: @grobian
A fix to your problem has been checked into the Jun2010 branch (the upcoming next release which is due to be released soon), since there will be no Feb2010 releases any more.
Tomorrow around noon (CEST) you can download a Jun2010 supertarball preview from here that should include the fix:
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/.DailyBuilds./0_latest/SourceSuperBall/
## Comment 14106
Date: 2010-06-14 20:08:10 +0200
From: hobury <<info>>
Created attachment 9
Log file freebsd 7.3 amd64
> Attached file: [log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2555_log_9) (text/plain, 98780 bytes)
> Description: Log file freebsd 7.3 amd64
## Comment 14107
Date: 2010-06-14 20:09:34 +0200
From: hobury <<info>>
Comment on attachment 9
Log file freebsd 7.3 amd64
The nightly build was also tested on a freebsd 7.3 machine (while no freebsd 8.0 machine is available for now):
uname -a
FreeBSD beijing.hobury.com 7.3-RELEASE FreeBSD 7.3-RELEASE 0: Sun Mar 21 05:25:24 UTC 2010 root@driscoll.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
Error messages are possibly related.
## Comment 14108
Date: 2010-06-14 20:17:33 +0200
From: @grobian
the freebsd7.3 problem appears to be a libtool problem that I can't really make any sense of.
## Comment 14109
Date: 2010-06-15 06:57:14 +0200
From: hobury <<info>>
(In reply to comment 10)
> the freebsd7.3 problem appears to be a libtool problem that I can't really make
> any sense of.
So do you suggest that the installed libtool should be upgraded? Have there been other reports of FreeBSD 7.3 not being able to install MonetDB (and not logged in bugzilla)?
## Comment 14110
Date: 2010-06-15 07:22:16 +0200
From: @drstmane
What is the result of
perl -MConfig -e '$x=$Config{installvendorarch}; $x =~ s|$Config{vendorprefix}/||; print $x;'
on your FreeBSD 7.3 system?
## Comment 14111
Date: 2010-06-15 07:30:40 +0200
From: @drstmane
I'm not aware of any other reports regarding this problem on FreeBSD.
However, the error
/bin/sh ../../../libtool --mode=install /usr/bin/install -c MapiLib.la '/usr/local/'
libtool: install: error: cannot install `MapiLib.la' to a directory not ending in /usr/local/
indeed seems to indicate a libtool problem --- whether libtool inherent or triggered by the MonetDB code base is not clear to me.
The problem could also be perl and/or swig related (see my previous posting).
Unless you need the perl DBI interface, you might also want to try to compile MonetDB without swig support by setting
EXTRA_ECONF='--with-swig=no'
in your shell environment before calling monetdb-install.sh
## Comment 14112
Date: 2010-06-15 22:28:19 +0200
From: hobury <<info>>
> What is the result of
>
> perl -MConfig -e '$x=$Config{installvendorarch}; $x =~
> s|$Config{vendorprefix}/||; print $x;'
>
> on your FreeBSD 7.3 system?
There is no result at all, and the command returns to the prompt.
## Comment 14123
Date: 2010-06-19 09:29:45 +0200
From: hobury <<info>>
Created attachment 10
Log file - 19-jun-2010 FreeBSD 8.0
(In reply to comment 7)
> Tomorrow around noon (CEST) you can download a Jun2010 supertarball preview
> from here that should include the fix:
> http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/.DailyBuilds./0_latest/SourceSuperBall/
Installation on FreeBSD 8.0 still failed, log file attached.
> Attached file: [log](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2555_log_10) (application/octet-stream, 99349 bytes)
> Description: Log file - 19-jun-2010 FreeBSD 8.0
## Comment 14124
Date: 2010-06-19 10:36:47 +0200
From: @drstmane
Your FreeBSD 8.0 seems to experience the same problem as on your FreeBSD 7.3:
/bin/sh ../../../libtool --mode=install /usr/bin/install -c MapiLib.la '/usr/local/'
libtool: install: error: cannot install `MapiLib.la' to a directory not ending in /usr/local/
The error as such looks self contradicting to me.
It might be triggered (not necessarily caused) by the fact that your perl installation does not reveals its installation suffix the way we usually test for it (see my earlier request and your answer). I honestly have no idea why your perl does that or why your libtool then chokes.
(
BTW, which versio of Perl are you using?
)
Did/could you try my suggestion of skipping the compilation of the Perl/DBI interface by setting
EXTRA_ECONF='--with-swig=no'
in your shell environment before calling monetdb-install.sh ?
## Comment 14125
Date: 2010-06-19 10:50:36 +0200
From: @drstmane
Could you please also test what the following commands say on your FreeBSD systems:
perl -V
perl -V:installvendorarch -V:installvendorlib -V:vendorprefix
Thanks!
## Comment 14126
Date: 2010-06-20 14:25:45 +0200
From: hobury <<info>>
Created attachment 11
Perl version FreeBSD 8.0
(In reply to comment 17)
> Could you please also test what the following commands say on your FreeBSD
> systems:
>
> perl -V
>
> perl -V:installvendorarch -V:installvendorlib -V:vendorprefix
>
> Thanks!
Please see attachment for the result of the commands above. I had tried the EXTRA_ECONF='--with-swig=no' setting, but it leads to a command not found. How exactly should it be run or entered?
> Attached file: [perl-version.txt](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2555_perl-version.txt_11) (text/plain, 3106 bytes)
> Description: Perl version FreeBSD 8.0
## Comment 14127
Date: 2010-06-20 14:44:14 +0200
From: @drstmane
The syntactic details for setting environment variables depend on your shell.
In bash, you can use, e.g.,
export EXTRA_ECONF='--with-swig=no'
./monetdb-install.sh ...
## Comment 14128
Date: 2010-06-20 23:13:42 +0200
From: hobury <<info>>
(In reply to comment 19)
> export EXTRA_ECONF='--with-swig=no'
> ./monetdb-install.sh ...
The only difference in the log file is that line 10 now reads:
./configure --prefix='/usr/local' --disable-optimize --disable-debug --disable-assert --disable-strict --with-swig=no
| gdk_system/MT_init fails to compile on FreeBSD 8.0 | https://api.github.com/repos/MonetDB/MonetDB/issues/2555/comments | 0 | 2020-11-30T11:02:58Z | 2024-06-27T11:47:38Z | https://github.com/MonetDB/MonetDB/issues/2555 | 753,379,042 | 2,555 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-02 10:16:16 +0200
From: @grobian
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.20.1 (Jun2010) [obsolete]
Last updated: 2010-08-20 14:03:52 +0200
## Comment 14071
Date: 2010-06-02 10:16:16 +0200
From: @grobian
The message
FIXME: remove this notice for the installed monetdb5.conf
-----------------------------------------------------------
Please keep the comments below aligned with the defaults in
MonetDB/src/common/monet_options.mx
-----------------------------------------------------------
does not belong to a released conffile, as it is of no use for any user and needlessly pretends to cause panic for no good reason.
It should be removed before we release. Perhaps it should only exist in the default (development/Current) branch, as that's the only place where reasonably defaults can be changed/added.
## Comment 14072
Date: 2010-06-02 11:38:44 +0200
From: @sjoerdmullender
I added code to my build script to remove the comments prior to a release build.
The next release candidate build will show whether it works.
The code will remove the comments from the .in file and commit the change.
| monetdb5.conf: remove "keep aligned" message before actual release | https://api.github.com/repos/MonetDB/MonetDB/issues/2554/comments | 0 | 2020-11-30T11:02:55Z | 2024-06-27T11:47:37Z | https://github.com/MonetDB/MonetDB/issues/2554 | 753,379,002 | 2,554 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-01 21:18:38 +0200
From: Mitja Kleider <<mitja>>
To: MonetDB5 devs <<bugs-monetdb5>>
Version: 5.22.1 (Oct2010) [obsolete]
CC: @drstmane
Last updated: 2010-11-15 09:39:02 +0100
## Comment 14065
Date: 2010-06-01 21:18:38 +0200
From: Mitja Kleider <<mitja>>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build Identifier:
The SQL queries below both fail with this error message:
MALException:!ERROR: BBPdecref: tmp_1066 does not have pointer fixes.
sql>select count(node), node, k, v from node_tags group by node, k, v
having count(node) > 1;
sql>ALTER TABLE node_tags ADD CONSTRAINT pk_node_tags UNIQUE (node, k,
v);
I am using the latest mercurial version on Gentoo:
$ hg identify
[ec76161adec3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ec76161adec3) tip
Reproducible: Always
### Steps to Reproduce:
1. Import Germany.osm from 2010-06-01 in this schema http://wiki.openstreetmap.org/wiki/MonetDB/Schema
2. Execute any of the two queries mentioned above.
3. MALException
If you need more details, I am happy to provide them.
### Actual Results:
MALException:!ERROR: BBPdecref: tmp_1066 does not have pointer fixes.
### Expected Results:
Successful query execution.
$ mserver5 --version
MonetDB server v5.21.0 (64-bit), based on kernel v1.39.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 6.8GiB available memory, 2 available cpu cores
Configured for prefix: /opt/monetdb
Libraries:
libpcre: 7.9 2009-04-11 (compiled with 7.9)
openssl: OpenSSL 0.9.8n 24 Mar 2010 (compiled with OpenSSL 0.9.8n 24 Mar 2010)
libxml2: 2.7.7 (compiled with 2.7.7)
Compiled by: mitja@localhost (x86_64-unknown-linux-gnu)
Compilation: gcc -O2 -Wall -Wextra -fno-strict-aliasing -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : /usr/x86_64-pc-linux-gnu/bin/ld -IPA -m elf_x86_64
## Comment 14066
Date: 2010-06-01 21:40:05 +0200
From: @drstmane
Mitja,
thanks for the detailed report.
Just one question: where can I download Germany.osm from?
Stefan
## Comment 14067
Date: 2010-06-01 22:33:40 +0200
From: Mitja Kleider <<mitja>>
(In reply to comment 1)
> Just one question: where can I download Germany.osm from?
ftp://ftp5.gwdg.de/pub/misc/openstreetmap/download.geofabrik.de/germany.osm.bz2
I just uploaded the code for importing to http://gitorious.org/osm-poi-tools/monetdb/trees/master
## Comment 14068
Date: 2010-06-01 23:43:04 +0200
From: @drstmane
Both queries run without error with the latest code base from both the Feb2010 Stable release branch and the Jun2010 release candidate branch.
The second query is actually included in the generated import.sql , which I modified to wrap the last two transactions (adding sequences and constraints) in
SET optimizer='nov2009_pipe';
...
SET optimizer='default_pipe';
accoding to the instructions at http://wiki.openstreetmap.org/wiki/MonetDB/Schema (& http://article.gmane.org/gmane.comp.db.monetdb.devel/2398 ;-)).
The first query yields an empty result in both cases.
Inside import.sql, the second query (ALTER TABLE ...) also runs without error with the latest code base from the default branch.
The first query, however, triggers the reported error with the latest code branch from the default branch.
When configured and built with assertions enabled, mserver5 reports
>mserver5: .../MonetDB/src/gdk/gdk_bbp.mx:2013: decref: Assertion `b == ((void *)0) || b->T->heap.parentid == 0 || BBP[(((int)(b->T->heap.parentid))>0?((int)(b->T->heap.parentid)):-((int)(b->T->heap.parentid)))].refs > 0' failed.
More investigation to follow tomorrow ...
Stefan
## Comment 14069
Date: 2010-06-01 23:56:37 +0200
From: Mitja Kleider <<mitja>>
> The second query is actually included in the generated import.sql, which I
> modified to wrap the last two transactions (adding sequences and constraints)
> in
>
> SET optimizer='nov2009_pipe';
> ...
> SET optimizer='default_pipe';
I can confirm, the query
ALTER TABLE node_tags ADD CONSTRAINT pk_node_tags UNIQUE (node, k, v);
is successful with nov2009_pipe, but fails with the reported error message in my case when using default_pipe.
## Comment 14070
Date: 2010-06-02 07:17:21 +0200
From: @drstmane
There seems to be a reference counting problem, i.e., the parent of a view has only logical but no physical references (see details below);
possibly caused by some view creation (still) incrementing (only) the logical, but not the physical reference count;
possibly related to Sjoerd's recent view reference counting changes.
mserver5: /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB/src/gdk/gdk_bbp.mx:2013: decref: Assertion `b == ((void *)0) || b->T->heap.parentid == 0 || BBP[(((int)(b->T->heap.parentid))>0?((int)(b->T->heap.parentid)):-((int)(b->T->heap.parentid)))].refs > 0' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0x7fffdd077710 (LWP 16562)]
0x00000036ce8326d5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-6.fc12.x86_64 cyrus-sasl-lib-2.1.23-9.fc12.x86_64 geos-3.2.1-1.fc12.x86_64 glibc-2.11.1-6.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-7.fc12.x86_64 libcurl-7.19.7-9.fc12.x86_64 libgcc-4.4.3-4.fc12.x86_64 libidn-1.9-5.x86_64 libselinux-2.0.90-5.fc12.x86_64 libssh2-1.2.4-1.fc12.x86_64 libstdc++-4.4.3-4.fc12.x86_64 libuuid-2.16.2-9.fc12.x86_64 libxml2-2.7.6-2.fc12.x86_64 libxslt-1.1.26-1.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64 nspr-4.8.4-2.fc12.x86_64 nss-3.12.6-4.fc12.x86_64 nss-softokn-3.12.4-19.fc12.x86_64 nss-softokn-freebl-3.12.4-19.fc12.x86_64 nss-util-3.12.6-1.fc12.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0-4.fc12.x86_64 pcre-7.8-3.fc12.x86_64 raptor-1.4.18-5.fc12.x86_64 readline-6.0-3.fc12.x86_64 sqlite-3.6.20-1.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) bt
0 0x00000036ce8326d5 in raise () from /lib64/libc.so.6
1 0x00000036ce833eb5 in abort () from /lib64/libc.so.6
2 0x00000036ce82b7c5 in __assert_fail () from /lib64/libc.so.6
3 0x00007ffff71495c0 in decref (i=891, logical=0, releaseShare=0, lock=1) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB/src/gdk/gdk_bbp.mx:2013
4 0x00007ffff714a25a in BBPreleaseref (i=891) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB/src/gdk/gdk_bbp.mx:2140
5 0x00007fffe9d1a115 in ALGjoinestimate (result=0x7fffdf756b88, lid=0x7fffdf756a68, rid=0x7fffdf756998, estimate=0x7fffdd074878) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB5/src/modules/kernel/algebra.mx:3080
6 0x00007fffe9d1a198 in ALGjoin (result=0x7fffdf756b88, lid=0x7fffdf756a68, rid=0x7fffdf756998) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB5/src/modules/kernel/algebra.mx:3089
7 0x00007ffff7cf7fdb in DFLOWstep (t=0x7fffd00a1468, fs=0x7fffdf753d20) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB5/src/mal/mal_interpreter.mx:1916
8 0x00007ffff7cfcd61 in runDFLOWworker (t=0x7fffd00a1468) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB5/src/mal/mal_interpreter.mx:1134
9 0x00000036cf406a3a in start_thread () from /lib64/libpthread.so.0
10 0x00000036ce8de62d in clone () from /lib64/libc.so.6
11 0x0000000000000000 in ?? ()
(gdb) up
1 0x00000036ce833eb5 in abort () from /lib64/libc.so.6
(gdb)
2 0x00000036ce82b7c5 in __assert_fail () from /lib64/libc.so.6
(gdb)
3 0x00007ffff71495c0 in decref (i=891, logical=0, releaseShare=0, lock=1) at /ufs/manegold/_/scratch0/Monet/HG/default/source/MonetDB/src/gdk/gdk_bbp.mx:2013
2013 assert(b == NULL || b->T->heap.parentid == 0 || BBP_refs(b->T->heap.parentid) > 0);
(gdb) li
2008 if (BBP_refs(i) == 0) {
2009 GDKerror("BBPdecref: %s does not have pointer fixes.\n", BBPname(i));
2010 assert(0);
2011 } else {
2012 assert(b == NULL || b->H->heap.parentid == 0 || BBP_refs(b->H->heap.parentid) > 0);
2013 assert(b == NULL || b->T->heap.parentid == 0 || BBP_refs(b->T->heap.parentid) > 0);
2014 assert(b == NULL || b->H->vheap == NULL || b->H->vheap->parentid == 0 || BBP_refs(b->H->vheap->parentid) > 0);
2015 assert(b == NULL || b->T->vheap == NULL || b->T->vheap->parentid == 0 || BBP_refs(b->T->vheap->parentid) > 0);
2016 refs = --BBP_refs(i);
2017 if (b && refs == 0) {
(gdb) p BBP[891]
$1 = {b = {0x7fffc4000b38, 0x7fffc4000b60}, nme = {0x7fffb4000ab8 "tmp_1573", 0x7fffc4000908 "tmpr_1573"}, bak = {0x7fffb4000ab8 "tmp_1573", 0x0}, next = {0, 0}, cache = 0x7fffc4000b38, path = 0x7fffb40008c8 "15/1573", options = 0x0, refs = 1, lrefs = 1, lastused = 112100, status = 1}
(gdb) p b
$2 = (BAT *) 0x7fffc4000b38
(gdb) p *b
$3 = {batCacheid = 891, H = 0x7fffc4000b88, T = 0x7fffc4000c18, P = 0x7fffc4000ca8, U = 0x7fffc4000cc0}
(gdb) p *b->U
$4 = {deleted = 0, first = 0, inserted = 8607268, count = 8607268, capacity = 8650752}
(gdb) p *b->P
$5 = {tid = 140736901642001, stamp = 446, copiedtodisk = 0, dirty = 1, dirtyflushed = 0, descdirty = 1, lview = 0, set = 0, restricted = 1, persistence = 1, unused = 0, sharecnt = 0, map_head = 0 '\000', map_tail = 0 '\000', map_hheap = 0 '\000', map_theap = 0 '\000'}
(gdb) p *b->H
$6 = {id = 0x7ffff77d4789 "h", width = 0, type = 0 '\000', shift = 0 '\000', sorted = 65 'A', varsized = 1 '\001', key = 1 '\001', dense = 0 '\000', nonil = 1 '\001', nil = 0 '\000', unused = 0 '\000', align = 1004289, nosorted_rev = 0, nokey = {0, 0}, nosorted = 0, nodense = 0, seq = 0, heap = {
maxsize = 0, free = 0, size = 0, base = 0x0, filename = 0x0, storage = 1 '\001', copied = 0 '\000', hashash = 0 '\000', newstorage = 1 '\001', dirty = 0 '\000', parentid = 0}, vheap = 0x0, hash = 0x0, props = 0x0}
(gdb) p *b->T
$7 = {id = 0x7ffff77d478b "t", width = 4, type = 13 '\r', shift = 2 '\002', sorted = 0 '\000', varsized = 1 '\001', key = 0 '\000', dense = 0 '\000', nonil = 1 '\001', nil = 0 '\000', unused = 0 '\000', align = 1004282, nosorted_rev = 0, nokey = {10, 11}, nosorted = 4, nodense = 0, seq = 0, heap = {
maxsize = 34603008, free = 34429072, size = 34603008, base = 0x7fffd5f00000 "\020 ", filename = 0x7fffd008bd28 "10/1073.tail", storage = 1 '\001', copied = 0 '\000', hashash = 0 '\000', newstorage = 1 '\001', dirty = 0 '\000', parentid = -571}, vheap = 0x62f258, hash = 0x0, props = 0x0}
(gdb) p b->T->heap.parentid
$8 = -571
(gdb) p BBP[571]
$9 = {b = {0x62f088, 0x62f0b0}, nme = {0x62f2a8 "tmp_1073", 0x62f2d8 "tmpr_1073"}, bak = {0x0, 0x0}, next = {0, 0}, cache = 0x62f088, path = 0x62f308 "10/1073", options = 0x0, refs = 0, lrefs = 6, lastused = 112112, status = 33}
(gdb) p b->H->heap.parentid
$10 = 0
(gdb) p b->H->vheap
$11 = (Heap *) 0x0
(gdb) p b->T->vheap
$12 = (Heap *) 0x62f258
(gdb) p b->T->vheap->parentid
$13 = 0
(gdb)
## Comment 14073
Date: 2010-06-02 14:40:16 +0200
From: @drstmane
The problem seems to occur when a view is created over an [oid,str] BAT that has its own BUN tail heap (b->H->heap.parentid == 0, i.e., no view), but shares the var tail heap with an other BAT (b->T->vheap->parentid != 0, i.e., a view).
VIEWcreate() only handles shared BUN headp, but not yet shared var heaps.
Next to
define VIEWhparent(x) ((x)->P->lview?0:(x)->H->heap.parentid)
define VIEWtparent(x) ((x)->P->lview?0:(x)->T->heap.parentid)
also
define VIEWvhparent(x) (((x)->P->lview||!(x)->H->vheap)?0:(x)->H->vheap->parentid)
define VIEWvtparent(x) (((x)->P->lview||!(x)->T->vheap)?0:(x)->T->vheap->parentid)
are already defined in gdk.mx, but apparently not yet used "everywhere".
Among others, the following code in gdk_bbp.mx does not seem completely sound to me, yet:
static int
BBPaddtobin(BAT *b)
{
int bin = BATCACHE_BIN(b->htype, b->ttype);
bat bid = b->batCacheid, hp = VIEWhparent(b), tp = VIEWtparent(b), vhp = VIEWhparent(b), vtp = VIEWtparent(b);
^ ^ ^ ^
more to be done once time allows ...
## Comment 14088
Date: 2010-06-10 16:41:12 +0200
From: @sjoerdmullender
Changeset [e5a1c58910b1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e5a1c58910b1) 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=e5a1c58910b1](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e5a1c58910b1)
Changeset description:
Attempt to deal with views on varheaps.
If a BAT is a view on another BAT, that can mean several things.
- sharing BUN heap (only if no VAR heap)
- sharing BUN heap + VAR heap
- sharing VAR heap
When sharing the VAR heap, two situations were possible:
- the VAR heap structure is shared (and hence also the actual data)
- the VAR heap structure is private, but the base pointer points into
the parent's VAR heap data.
This checkin gets rid of the latter possibility. When the VAR heap is
shared, it is not completely shared.
A VAR heap structure is "owned" by one BAT, the parent. Only when the
parent BAT is destroyed can the heap structure and accompanying data
be freed. The owner of the VAR heap structure is indicated by the
parentid in the VAR heap structure. This value must now always be the
ID of the owner BAT (and hence is always greater than zero). If the
parentid value differs from a BAT's own ID, the var heap structure is
owned by another BAT and hence the BAT is a view on this other BAT.
Note that this checkin removes the possibility of a view's var heap
base pointer pointing somewhere halfway into the parent's var heap
data, but this situation doesn't make any sense since the BUN heap
contains offsets relative to the start of the VAR heap data, which
would be lost in this situation.
This fixes bug #2553.
## Comment 14145
Date: 2010-06-28 18:12:52 +0200
From: @sjoerdmullender
I can now run the test on the "default" branch without error.
| "group by" query fails: MALException: BBPdecref: tmp_1066 does not have pointer fixes. | https://api.github.com/repos/MonetDB/MonetDB/issues/2553/comments | 0 | 2020-11-30T11:02:52Z | 2024-06-27T11:47:36Z | https://github.com/MonetDB/MonetDB/issues/2553 | 753,378,958 | 2,553 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-06-01 20:21:50 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 2.36.5 (Feb2010-SP2) [obsolete]
CC: @njnes
Last updated: 2014-08-07 20:00:07 +0200
## Comment 14063
Date: 2010-06-01 20:21:50 +0200
From: @grobian
% $INSTALL_DIR/bin/mclient -d phantom3
Welcome to mclient, the MonetDB/SQL interactive terminal
Database: MonetDB v5.20.0, 'phantom3'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>\d
sql>create table rr (id int);
operation successful
sql>insert into rr values (1),(2),(3);
3 affected rows
sql>prepare select * from rr limit ?;
syntax error, unexpected '?', expecting sqlINT in: "prepare select * from rr limit ?"
sql>
I would expect the prepare to succeed and me being able to do exec0(1) to see one tuple returned.
## Comment 14064
Date: 2010-06-01 20:22:28 +0200
From: @grobian
this bug also applies to the current candidate (Jun2010 release)
## Comment 14176
Date: 2010-07-02 08:48:17 +0200
From: @njnes
Changeset [64acf9744dca](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=64acf9744dca) 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=64acf9744dca](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=64acf9744dca)
Changeset description:
added test for fixed bug #2552 PREPARE: limit statement not recognised
## Comment 19260
Date: 2013-10-09 11:51:15 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [46ab29b898c2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=46ab29b898c2) 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=46ab29b898c2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=46ab29b898c2)
Changeset description:
fixed bug #3382 (added test to Bug #2552, which are very related)
## Comment 19265
Date: 2013-10-09 21:02:02 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [8bc29626a40f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8bc29626a40f) 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=8bc29626a40f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8bc29626a40f)
Changeset description:
limit_in_prepare.Bug-2552: propagated changeset [46ab29b898c2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=46ab29b898c2) to 32-bit output
## Comment 19266
Date: 2013-10-09 21:08:48 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [01ef84ed226f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=01ef84ed226f) 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=01ef84ed226f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=01ef84ed226f)
Changeset description:
limit_in_prepare.Bug-2552: approve default branch output
## Comment 19362
Date: 2013-11-29 16:44:41 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [c29b57f8ff31](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c29b57f8ff31) 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=c29b57f8ff31](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c29b57f8ff31)
Changeset description:
limit_in_prepare.Bug-2552: prepagared changeset [d22c2f41c74c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d22c2f41c74c) to 32-bit output
## Comment 20015
Date: 2014-08-07 20:00:07 +0200
From: MonetDB Mercurial Repository <<hg>>
Changeset [5eec7ffbc4f3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=5eec7ffbc4f3) 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=5eec7ffbc4f3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=5eec7ffbc4f3)
Changeset description:
limit_in_prepare.Bug-2552: re-aligned 32-bit output with default output
| PREPARE: limit statement not recognised | https://api.github.com/repos/MonetDB/MonetDB/issues/2552/comments | 0 | 2020-11-30T11:02:48Z | 2024-06-27T11:47:35Z | https://github.com/MonetDB/MonetDB/issues/2552 | 753,378,911 | 2,552 |
[
"MonetDB",
"MonetDB"
] | # Deleted Bugzilla Bug
Date: 2020-11-30T10:59:56Z
This bug was created during the import from Bugzilla.
GitHub Issues Tracker allows to assign consecutive
ids only. So this dummy issue was created in place of
a deleted Bugzilla Bug.
Please ignore this report.
| Deleted Bugzilla Bug | https://api.github.com/repos/MonetDB/MonetDB/issues/2551/comments | 0 | 2020-11-30T11:02:45Z | 2020-11-30T11:02:47Z | https://github.com/MonetDB/MonetDB/issues/2551 | 753,378,864 | 2,551 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-27 17:13:36 +0200
From: @grobian
To: Merovingian devs <<bugs-merovingian>>
Version: 1.38.1 (Jun2010) [obsolete]
Last updated: 2010-06-01 12:25:48 +0200
## Comment 14057
Date: 2010-05-27 17:13:36 +0200
From: @grobian
Forwarded from Gijs Molenaar:
ik kan geen bugreport aanmaken, dan maar zo:
Permissies van sockets staan niet goed. Idee is dat je als in je monetdb group
zit en merovingian draait als monetdb, je het monetdb commando kan gebruiken. Is
niet zo.
## Comment 14059
Date: 2010-06-01 11:51:32 +0200
From: @grobian
Changeset [22ab36b7873b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=22ab36b7873b) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=22ab36b7873b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=22ab36b7873b)
Changeset description:
Fix bug #2550 (file access permissions), cleanup more, remove prestarting database feature
## Comment 14060
Date: 2010-06-01 12:25:48 +0200
From: @grobian
.merovingian_control = USR and GRP writable
.merovingian_pass = USR writable
.mapi_socket = USR, GRP, OTR writable
| Socket permissions do not allow others to connect (strict umask) | https://api.github.com/repos/MonetDB/MonetDB/issues/2550/comments | 0 | 2020-11-30T11:02:42Z | 2024-06-27T11:47:34Z | https://github.com/MonetDB/MonetDB/issues/2550 | 753,378,827 | 2,550 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-25 18:18:06 +0200
From: michael.seibold
To: SQL devs <<bugs-sql>>
Version: 2.36.3 (Feb2010-SP1) [obsolete]
CC: michael.seibold, @drstmane
Last updated: 2010-06-08 08:28:16 +0200
## Comment 14056
Date: 2010-05-25 18:18:06 +0200
From: michael.seibold
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3
Build Identifier:
When I do the following, the database "TestBug" crashes with a Segmentation Fault when preparing the prepared statement(see java program below) through JDBC interface (MonetDB-Feb2010-SuperBall-SP1):
Java Program TestBug:
---------------------
public class TestBug {
public static void main(String[] args) {
try {
Class.forName("nl.cwi.monetdb.jdbc.MonetDriver").newInstance();
Properties props = new Properties();
props.setProperty("user", "monetdb");
props.setProperty("password", "monetdb");
Connection connection = DriverManager.getConnection("jdbc:monetdb://localhost/TestBug", props);
connection.setAutoCommit(false);
connection.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE);
PreparedStatement ps = connection.prepareStatement("UPDATE TB.STOCK_ITEM SET S_QUANTITY = ?, S_YTD = S_YTD + ?, S_ORDER_CNT = S_ORDER_CNT + 1 WHERE S_W_ID = ? AND S_I_ID = ?");
} catch (SQLException e) {
e.printStackTrace();
} catch (InstantiationException e) {
e.printStackTrace();
} catch (IllegalAccessException e) {
e.printStackTrace();
} catch (ClassNotFoundException e) {
e.printStackTrace();
}
}
}
Reproducible: Always
### Steps to Reproduce:
./monetdb create TestBug
./monetdb status
./monetdb start TestBug
./monetdb status
./mclient -lsql -umonetdb -Pmonetdb -d TestBug -i < test_bug_create_schema.sql
test_bug_create_schema.sql:
----------------------------
CREATE SCHEMA TB;
CREATE TABLE TB.STOCK_ITEM ( S_W_ID INTEGER NOT NULL , S_I_ID INTEGER NOT NULL , S_QUANTITY INTEGER NOT NULL , S_DIST_01 CHAR(24) NOT NULL , S_DIST_02 CHAR(24) NOT NULL , S_DIST_03 CHAR(24) NOT NULL , S_DIST_04 CHAR(24) NOT NULL , S_DIST_05 CHAR(24) NOT NULL , S_DIST_06 CHAR(24) NOT NULL , S_DIST_07 CHAR(24) NOT NULL , S_DIST_08 CHAR(24) NOT NULL , S_DIST_09 CHAR(24) NOT NULL , S_DIST_10 CHAR(24) NOT NULL , S_YTD DECIMAL(8,0) NOT NULL , S_ORDER_CNT INTEGER NOT NULL , S_REMOTE_CNT INTEGER NOT NULL , S_DATA VARCHAR(50) NOT NULL);
Java Program TestBug:
---------------------
public class TestBug {
public static void main(String[] args) {
try {
Class.forName("nl.cwi.monetdb.jdbc.MonetDriver").newInstance();
Properties props = new Properties();
props.setProperty("user", "monetdb");
props.setProperty("password", "monetdb");
Connection connection = DriverManager.getConnection("jdbc:monetdb://localhost/TestBug", props);
connection.setAutoCommit(false);
connection.setTransactionIsolation(Connection.TRANSACTION_SERIALIZABLE);
PreparedStatement ps = connection.prepareStatement("UPDATE TB.STOCK_ITEM SET S_QUANTITY = ?, S_YTD = S_YTD + ?, S_ORDER_CNT = S_ORDER_CNT + 1 WHERE S_W_ID = ? AND S_I_ID = ?");
} catch (SQLException e) {
e.printStackTrace();
} catch (InstantiationException e) {
e.printStackTrace();
} catch (IllegalAccessException e) {
e.printStackTrace();
} catch (ClassNotFoundException e) {
e.printStackTrace();
}
}
}
### Actual Results:
Segmentation Fault
### Expected Results:
no Segmentation Fault
When I do the same thing using normal (not prepared) Statements through JDBC everything works fine, but horribly slow. Seems to be an issue with PreparedStatements of JDBC.
## Comment 14074
Date: 2010-06-02 15:29:15 +0200
From: @grobian
Hi Michael,
Have you tried by chance with Feb2010-SP2? In any case, could you please run your TestBug program with
Connection connection =
DriverManager.getConnection("jdbc:monetdb://localhost/TestBug?debug=true", props);
and attach the monet_xxxxxxxxxx.log file to this bug?
Thanks.
## Comment 14075
Date: 2010-06-02 15:32:43 +0200
From: @grobian
Sorry, I didn't really watch closely. The bug is simply reproducable by issuing the following statement from mclient.
PREPARE UPDATE TB.STOCK_ITEM SET S_QUANTITY = ?, S_YTD = S_YTD + ?, S_ORDER_CNT = S_ORDER_CNT + 1 WHERE S_W_ID = ? AND S_I_ID = ?;
It also crashes on the candidate here, so Michael, you don't need to do anything, we have enough pointers to debug the problem in detail here.
## Comment 14076
Date: 2010-06-02 15:37:11 +0200
From: @drstmane
... and here is a first gdb log (with Feb2010-SP2):
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe0d99710 (LWP 26061)]
0x00007fffe14670b0 in rel_binop_ (sql=0x7fffd4005438, l=0x7fffd4070038, r=0x7fffd4070108, s=0x7fffd4018298, fname=0x7fffd40af878 "sql_add", table_func=0) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_select.mx:3029
3029 int digits = t1->digits + t2->digits;
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-6.fc12.x86_64 cyrus-sasl-lib-2.1.23-9.fc12.x86_64 glibc-2.11.1-6.x86_64 keyutils-libs-1.2-6.fc12.x86_64 krb5-libs-1.7.1-9.fc12.x86_64 libcom_err-1.41.9-7.fc12.x86_64 libcurl-7.19.7-9.fc12.x86_64 libidn-1.9-5.x86_64 libselinux-2.0.90-5.fc12.x86_64 libssh2-1.2.4-1.fc12.x86_64 libuuid-2.16.2-9.fc12.x86_64 libxml2-2.7.6-2.fc12.x86_64 libxslt-1.1.26-1.fc12.x86_64 ncurses-libs-5.7-3.20090207.fc12.x86_64 nspr-4.8.4-2.fc12.x86_64 nss-3.12.6-4.fc12.x86_64 nss-softokn-3.12.4-19.fc12.x86_64 nss-softokn-freebl-3.12.4-19.fc12.x86_64 nss-util-3.12.6-1.fc12.x86_64 openldap-2.4.19-4.fc12.x86_64 openssl-1.0.0-4.fc12.x86_64 pcre-7.8-3.fc12.x86_64 raptor-1.4.18-5.fc12.x86_64 readline-6.0-3.fc12.x86_64 sqlite-3.6.20-1.fc12.x86_64 zlib-1.2.3-23.fc12.x86_64
(gdb) bt
0 0x00007fffe14670b0 in rel_binop_ (sql=0x7fffd4005438, l=0x7fffd4070038, r=0x7fffd4070108, s=0x7fffd4018298, fname=0x7fffd40af878 "sql_add", table_func=0) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_select.mx:3029
1 0x00007fffe146785b in rel_binop (sql=0x7fffd4005438, rel=0x7fffe0d98a18, se=0x7fffd40af968, f=3, ek=...) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_select.mx:3146
2 0x00007fffe146a86c in rel_value_exp2 (sql=0x7fffd4005438, rel=0x7fffe0d98a18, se=0x7fffd40af968, f=3, ek=..., is_last=0x7fffe0d989b4) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_select.mx:3949
3 0x00007fffe146affc in rel_value_exp (sql=0x7fffd4005438, rel=0x7fffe0d98a18, se=0x7fffd40af968, f=3, ek=...) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_select.mx:4088
4 0x00007fffe146fc84 in update_table (sql=0x7fffd4005438, qname=0x7fffd40af608, assignmentlist=0x7fffd40af758, opt_where=0x7fffd40b00d8) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_updates.mx:398
5 0x00007fffe14712c9 in rel_updates (sql=0x7fffd4005438, s=0x7fffd40b01a8) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_updates.mx:744
6 0x00007fffe145cbaa in rel_semantic (sql=0x7fffd4005438, s=0x7fffd40b01a8) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/server/rel_semantic.mx:242
7 0x00007fffe13c4ddf in sql_symbol2stmt (c=0x7fffd4005438, sym=0x7fffd40b01a8) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/backends/monet5/sql.mx:1277
8 0x00007fffe140f96b in SQLparser (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/sql/src/backends/monet5/sql_scenario.mx:1153
9 0x00007ffff7d23d33 in runPhase (c=0x605b38, phase=1) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/MonetDB5/src/mal/mal_scenario.mx:602
10 0x00007ffff7d23e6f in runScenarioBody (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/MonetDB5/src/mal/mal_scenario.mx:644
11 0x00007ffff7d240d9 in runScenario (c=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/MonetDB5/src/mal/mal_scenario.mx:679
12 0x00007ffff7cd732c in MSserveClient (dummy=0x605b38) at /ufs/manegold/_/scratch0/Monet/HG/Feb2010/source/MonetDB5/src/mal/mal_session.mx:469
13 0x00000036cf406a3a in start_thread () from /lib64/libpthread.so.0
14 0x00000036ce8de62d in clone () from /lib64/libc.so.6
15 0x0000000000000000 in ?? ()
(gdb) li
3024 } else if (f->func->fix_scale == DIGITS_ADD) {
3025 f->res.digits = t1->digits + t2->digits;
3026 }
3027 return exp_binop(l, r, f);
3028 } else {
3029 int digits = t1->digits + t2->digits;
3030 sql_exp *ol = exp_dup(l);
3031 sql_exp *or = exp_dup(r);
3032
3033 if (!EC_NUMBER(t1->type->eclass) &&
(gdb) p t1
$1 = (sql_subtype *) 0x7fffd40836c0
(gdb) p *t1
$2 = {type = 0xfee548, digits = 8, scale = 0, comp_type = 0x0}
(gdb) p t2
$3 = (sql_subtype *) 0x0
(gdb)
Jun2010 branch and default branch show the same behaviour.
## Comment 14077
Date: 2010-06-02 15:44:46 +0200
From: @drstmane
Michael,
without the prepare, what exactly do you mean with "horribly slow"?
I.e., how much data (how many records) do you have?
How long does one update take or which update rates do you experience?
What are the hardware characteristics of your machine?
Do S_W_ID & S_I_ID form a primary key?
If so, did you try to add the respective primary key constraint to your table?
You could also profile a single update query, e.g., by simply running it as
TRACE UPDATE ...
in mclient and attach the output for analysis.
Thanks,
Stefan
## Comment 14078
Date: 2010-06-02 16:24:38 +0200
From: michael.seibold
Hi,
Thanks for the response.
The issue occurs only when I use Prepared Statements. For now, I have changed my program (quick and dirty) to use normal Statements, not Prepared Statements. The changed program uses the same SQL statements and works without errors on MonetDB, but it is slow.
The data volume is about 1GB and a statement, that takes less than 100 ms on Apache Derby takes 2-3 seconds on average with MonetDB-Without-Prepared-Statements on the same machine (currently I'm testing on my laptop: Core 2 Duo 2x 2,2Ghz, 2 GB RAM).
The performance issue might be caused by the client (that accesses MonetDB via JDBC) and the quick and dirty changes, as the client has to construct the sql statements strings with many dynamic parameters for each invocation. I expect, that with JDBC Prepared Statements the construction of the dynamic sql statements is more efficient and that the database system has to do less work / use better optimizations as the canned SQL statements are known.
I don't know if MonetDB will be faster, when I use prepared statements, but I though it would be fair as I also use them for the other database systems in my test. I didn't expect, that MonetDB would crash because of that. For the comparisons I'm trying to make, I want the client code to be the same for all systems, in order to make fair comparisons.
Yes, S_W_ID & S_I_ID form a primary key. I have also defined that in the schema:
ALTER TABLE TB.STOCK_ITEM ADD CONSTRAINT STOCK_ITEM_PK PRIMARY KEY (S_W_ID, S_I_ID)
I didn't put it into the bug report, to make it simpler, sorry for that.
Thanks,
Michael
## Comment 14080
Date: 2010-06-02 16:46:15 +0200
From: @drstmane
Michael,
sorry for the inconvenience with the crash --- you just hit a bug in MonetDB that no one else trapped into before --- we'll let you know once we managed to locate and fix the problem.
In the meantime, if you want to get a feeling for the "raw" performance of MonetDB without delays due to sql statement construction, etc. in the client, you could simply let your client program (or a separate generator) dump all created SQL statements into a file, say, "workload.sql", and then run this workload through mclient, i.e.,
`mclient -lsql workload.sql`
Add option "-t" to get global wall-clock timing.
Or use the following call to get per query wall-clock timings:
`mclient -lsql -t -i < workload.sql`
That should give an indication of the performance with prepared statements.
Stefan
## Comment 14081
Date: 2010-06-04 00:39:23 +0200
From: @drstmane
Niels fixed the bug in the Jun2010 branch.
THANKS!
I back-ported Niels' fix to the Feb2010 branch and propagated it to the default branch.
I also added a test in
sql/src/test/Bugzilla-2010/Tests/crash_with_prepare_statement.ID-2549.*
Michael,
you can get the fixed code from our Mercurial repository (http://dev.monetdb.org/hg/MonetDB/) or download the nightly built super source ball from http://monetdb.cwi.nl/Download/Builds/ once nightly testing has finished later today (Fri Jun 4 2010).
Stefan
## Comment 14083
Date: 2010-06-08 08:15:46 +0200
From: michael.seibold
Hi,
I have tried out the nightly built super source ball from http://monetdb.cwi.nl/Download/Builds/. Now PreparedStatements work like a charm. Thanks a lot for the support.
I have done a preliminary performance test and it seems to me, that there is no big performance difference between using PreparedStatements and normal Statements with MonetDB. I will do some more tests on a bigger machine in the next couple of weeks.
Thanks,
Michael
(In reply to comment 7)
> Niels fixed the bug in the Jun2010 branch.
> THANKS!
>
> I back-ported Niels' fix to the Feb2010 branch and propagated it to the default
> branch.
>
> I also added a test in
> sql/src/test/Bugzilla-2010/Tests/crash_with_prepare_statement.ID-2549.*
>
>
> Michael,
>
> you can get the fixed code from our Mercurial repository
> (http://dev.monetdb.org/hg/MonetDB/) or download the nightly built super source
> ball from http://monetdb.cwi.nl/Download/Builds/ once nightly testing has
> finished later today (Fri Jun 4 2010).
>
> Stefan
## Comment 14084
Date: 2010-06-08 08:28:16 +0200
From: @drstmane
Michael,
thanks for confirming the fix!
In case the performance is not dominated by purely translating the query (but rather by executing the query), now performance gain is to be expected by using prepared queries (they to have to be executed to get their effect ;-)).
For further analysis where the time goes, you can try to profile your query by prefixing it with "TRACE" in mclient, e.g.,
TRACE UPDATE ...
(Given that we don't have your data, we would be interested in seeing the profile...)
Stefan
| crash with prepare statement | https://api.github.com/repos/MonetDB/MonetDB/issues/2549/comments | 0 | 2020-11-30T11:02:38Z | 2024-06-27T11:47:33Z | https://github.com/MonetDB/MonetDB/issues/2549 | 753,378,755 | 2,549 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-23 11:46:44 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @romulogoncalves, @njnes, @drstmane
Last updated: 2010-08-30 09:18:28 +0200
## Comment 14055
Date: 2010-05-23 11:46:44 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier:
connect to default;
Test added as connectto.sql in BugTracker-2010
Reproducible: Always
## Comment 14256
Date: 2010-07-07 15:43:19 +0200
From: @romulogoncalves
This bug is fixed by the check in:
Changeset: [f205fff0936f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f205fff0936f) for MonetDB
URL: [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f205fff0936f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f205fff0936f)
## Comment 14282
Date: 2010-07-09 11:48:13 +0200
From: @grobian
Romulo, this is on Jun2010:
Database: MonetDB v5.20.3, 'goboom'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>connect to default;
CONNECT TO: DEFAULT is not supported!
sql>
Was/is this bug only on development, or has the bugfix been backported to Jun2010? In the latter case, your test seems not to be available in Jun2010.
## Comment 14294
Date: 2010-07-09 13:06:18 +0200
From: @drstmane
Martin originally reported for the default branch "development", but possibly because he only tested it there and not on the Jun2010.
Martin checked his test into the default branch only (and not the Jun2010 branch) most probably for similar reasons; cf.,
http://dev.monetdb.org/hg/MonetDB/rev/0e39b0c870c8
http://dev.monetdb.org/hg/MonetDB/rev/3595d3930d16
Given that Romulo fixed the bug in the Jun2010 branch, I suppose the bug occurred also there.
I'll back port the test and check whether I can also verify, approve and checking the respective stable output.
## Comment 14296
Date: 2010-07-09 13:11:03 +0200
From: @drstmane
Changeset [3b9f3349bbaf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=3b9f3349bbaf) 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=3b9f3349bbaf](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=3b9f3349bbaf)
Changeset description:
renamed test for bug #2548: "connectto" -> "connectto.Bug-2548"
## Comment 14297
Date: 2010-07-09 13:17:54 +0200
From: @drstmane
Changeset [8acde0d55a68](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=8acde0d55a68) 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=8acde0d55a68](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=8acde0d55a68)
Changeset description:
backported test for bug #2548 to Jun2010 branch
approved stable output as far as I can verify it;
some domain expert (Romulo, Martin, ?)
should double check the test and its stable output
in the Jun2010 branch
## Comment 14300
Date: 2010-07-09 13:19:55 +0200
From: @grobian
romulo, can you check the output and close this bug if appropriate?
## Comment 14357
Date: 2010-07-10 10:28:51 +0200
From: @drstmane
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/connectto.Bug-2548.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Candidate/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/connectto.Bug-2548.err.00.html
## Comment 14471
Date: 2010-07-18 09:48:58 +0200
From: @drstmane
Updated URLs are:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/connectto.Bug-2548.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora12/src_test_BugTracker-2010/connectto.Bug-2548.err.00.html
## Comment 14598
Date: 2010-08-02 16:08:39 +0200
From: @drstmane
Test appears to work fine with nightly testing, now.
## Comment 14816
Date: 2010-08-30 09:18:28 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15707
Date: 2011-03-31 08:21:23 +0200
From: @drstmane
Changeset [0448c2ec4989](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0448c2ec4989) 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=0448c2ec4989](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0448c2ec4989)
Changeset description:
renamed sql/test/BugTracker-2010/Tests/connectto.Bug-2548.stable.err.Windows to sql/test/BugTracker-2010/Tests/connectto.Bug-2548.stable.err.Windows6.1
| Connect to default segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/2548/comments | 0 | 2020-11-30T11:02:34Z | 2024-06-27T11:47:32Z | https://github.com/MonetDB/MonetDB/issues/2548 | 753,378,715 | 2,548 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-23 11:05:07 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.1.1 (Mar2011) [obsolete]
CC: @njnes, @sjoerdmullender, @drstmane
Last updated: 2011-04-28 16:25:36 +0200
## Comment 14054
Date: 2010-05-23 11:05:07 +0200
From: @mlkersten
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3
Build Identifier:
create schema authorized monetdb;
causes a segfault.
Test file BugTracker-2010/Tests/crashonschema.sql
Reproducible: Always
## Comment 14082
Date: 2010-06-05 12:28:12 +0200
From: @mlkersten
It seems this bug has been fixed in the head and Jun2010
## Comment 14349
Date: 2010-07-10 08:38:02 +0200
From: @drstmane
Changeset [15deb74e59b4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=15deb74e59b4) 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=15deb74e59b4](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=15deb74e59b4)
Changeset description:
renamed test for bug #2547: "crashonschema" -> "crashonschema.Bug-2547"
## Comment 14350
Date: 2010-07-10 08:47:02 +0200
From: @drstmane
Changeset [952e47efdd0b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=952e47efdd0b) 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=952e47efdd0b](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=952e47efdd0b)
Changeset description:
renamed stable output of test for bug #2547 also in Jun2010 branch
## Comment 14351
Date: 2010-07-10 08:51:44 +0200
From: @drstmane
Changeset [64774fd570aa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=64774fd570aa) 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=64774fd570aa](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=64774fd570aa)
Changeset description:
back-ported test for bug #2547 to Jun2010
the bug is claimed to be fixed in Jun2010
and the test's stable output was already in Jun2010
## Comment 14352
Date: 2010-07-10 09:00:20 +0200
From: @drstmane
Changeset [f5cb2db5f58f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=f5cb2db5f58f) 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=f5cb2db5f58f](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=f5cb2db5f58f)
Changeset description:
ignore varying address in error message
of test for bug #2547
## Comment 14359
Date: 2010-07-10 10:37:31 +0200
From: @drstmane
While the initially crashing statements now indeed appear to work,
the last statement in the test still triggers an unexpected error:
create schema intro3
grant insert on t2010 to monetdb;
=>
QUERY = create schema intro3
ERROR = !sql_stmt symbol(b31073f8)->token = CREATE_SCHEMA
see also
Bug #2569 "INSERT INTO ... EXCEPT ... fails"
## Comment 14608
Date: 2010-08-03 17:05:23 +0200
From: @drstmane
Changeset [c3648477858c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c3648477858c) 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=c3648477858c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c3648477858c)
Changeset description:
undo of accidental checkin of incorrect error message;
see also bugs 2547 & 2569
## Comment 14915
Date: 2010-09-20 10:05:14 +0200
From: @sjoerdmullender
Although it doesn't cause a server crash, there is still something wrong according to the test that accompanies this bug. Hence I'm reopening it.
When run, the test causes the server to spew the message:
sql_stmt symbol(7fe8b4007ab8)->token = CREATE_SCHEMA
## Comment 15705
Date: 2011-03-30 13:06:07 +0200
From: @njnes
fixed (some time ago)
## Comment 15749
Date: 2011-04-28 16:25:36 +0200
From: @sjoerdmullender
The Apr2011 release has been uploaded.
| create schema leads to sql_stmt symbol(x)->token = CREATE_SCHEMA | https://api.github.com/repos/MonetDB/MonetDB/issues/2547/comments | 0 | 2020-11-30T11:02:31Z | 2024-06-27T11:47:31Z | https://github.com/MonetDB/MonetDB/issues/2547 | 753,378,683 | 2,547 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-21 15:52:53 +0200
From: @swingbit
To: clients devs <<bugs-clients>>
Version: 1.38.5 (Jun2010-SP2) [obsolete]
Last updated: 2010-11-15 09:39:09 +0100
## Comment 14051
Date: 2010-05-21 15:52:53 +0200
From: @swingbit
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9 GTB7.0
Build Identifier:
When I try to use the -f option to dump functions, the dump is empty.
[roberto@skadi] ~/lhm_code/IndexCenter/console
$ DOTMONETDBFILE=.monetdb.root msqldump -d marec_10 -p 50151 | wc -l
246592
[roberto@skadi] ~/lhm_code/IndexCenter/console
$ DOTMONETDBFILE=.monetdb.root msqldump -d marec_10 -p 50151 -f | wc -l
0
Reproducible: Always
## Comment 14052
Date: 2010-05-21 16:38:51 +0200
From: @sjoerdmullender
Do you have any functions to dump?
A normal dump (without -f) will also dump the functions (it should dump everything), the -f option is a convenience to get just the functions.
## Comment 14053
Date: 2010-05-21 17:25:18 +0200
From: @swingbit
I did not understand that -f means ONLY functions.
Then there is nothing wrong with the -f switch.
There is however a problem with recognizing which functions should be dumped.
In my example, no function was dumped because they were all recognized as "system functions".
The current behavior seems to be: dump only functions 'where sql=true', i.e. no EXTERNAL functions. I guess the initial assumption was that those are always system functions.
However, they should be dumped as well. Same goes for types (to be dumped before functions!). And same again goes for triggers.
## Comment 14853
Date: 2010-08-30 09:24:27 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 14905
Date: 2010-09-14 09:33:27 +0200
From: @sjoerdmullender
Changeset [cbd1fa5e422e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=cbd1fa5e422e) 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=cbd1fa5e422e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=cbd1fa5e422e)
Changeset description:
Implemented dumping of "external" functions.
In the process, various other changes were made:
- cosmetics;
- we can now dump the TABLE type;
- split off some code in separate functions.
This implements bug #2546.
## Comment 14906
Date: 2010-09-14 09:34:16 +0200
From: @sjoerdmullender
Dumping of external functions has been implemented.
| msqldump: external functions not dumped, types and triggers not dumped | https://api.github.com/repos/MonetDB/MonetDB/issues/2546/comments | 0 | 2020-11-30T11:02:28Z | 2024-06-27T11:47:30Z | https://github.com/MonetDB/MonetDB/issues/2546 | 753,378,652 | 2,546 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-20 15:07:30 +0200
From: @sjoerdmullender
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2010-06-10 16:31:28 +0200
## Comment 14050
Date: 2010-05-20 15:07:30 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9
Build Identifier:
When compiling with --enable-optimize --disable-debug, the mentioned file doesn't compile (on Fedora 12, at least). The errors are:
lalg2msa.c: In function ‘alg2msa_worker’:
lalg2msa.c:143: error: ‘op’ may be used uninitialized in this function
lalg2msa.c:639: error: ‘comp_kind’ may be used uninitialized in this function
lalg2msa.c:701: error: ‘func_name’ may be used uninitialized in this function
lalg2msa.c:890: error: ‘kind’ may be used uninitialized in this function
lalg2msa.c:144: error: ‘prj_list’ may be used uninitialized in this function
lalg2msa.c:145: error: ‘sel_list’ may be used uninitialized in this function
Reproducible: Always
## Comment 14087
Date: 2010-06-10 16:31:06 +0200
From: @sjoerdmullender
I haven't had a problem compiling this file for some time.
Considering it fixed.
| compiler/algebra-m5sql/lalg2msa.c doesn't compile | https://api.github.com/repos/MonetDB/MonetDB/issues/2545/comments | 0 | 2020-11-30T11:02:25Z | 2024-06-27T11:47:29Z | https://github.com/MonetDB/MonetDB/issues/2545 | 753,378,611 | 2,545 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-19 14:19:29 +0200
From: @sjoerdmullender
To: clients devs <<bugs-clients>>
Version: 1.38.1 (Jun2010) [obsolete]
Last updated: 2010-05-19 14:20:41 +0200
## Comment 14048
Date: 2010-05-19 14:19:29 +0200
From: @sjoerdmullender
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100330 Fedora/3.5.9-2.fc12 Firefox/3.5.9
Build Identifier:
this is a test for the new bugzilla interface for submitting bugs.
please ignore.
Reproducible: Always
### Steps to Reproduce:
1.step one
2.step two
3.step three
### Actual Results:
don't know yet
### Expected Results:
a proper bug report
MonetDB server v5.18.5 (64-bit), based on kernel v1.36.5 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Found 7.8GiB available memory, 4 available cpu cores
Configured for prefix: /usr
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 1.0.0-beta4 10 Nov 2009 (compiled with OpenSSL 1.0.0-fips-beta4 10 Nov 2009)
libxml2: 2.7.6 (compiled with 2.7.6)
Compiled by: mockbuild@ (x86_64-redhat-linux-gnu)
Compilation: gcc -O2 -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize
Linking : ld -IPA -m elf_x86_64
| test bug report -- please ignore | https://api.github.com/repos/MonetDB/MonetDB/issues/2544/comments | 0 | 2020-11-30T11:02:22Z | 2024-06-28T13:21:55Z | https://github.com/MonetDB/MonetDB/issues/2544 | 753,378,560 | 2,544 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-19 11:33:27 +0200
From: zeuner <<zeuner>>
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @njnes
Last updated: 2010-08-20 14:04:08 +0200
## Comment 14046
Date: 2010-05-19 11:33:27 +0200
From: zeuner <<zeuner>>
Created attachment 5
SQL code to show the issue
When an update statement changes a row with the same OID as a previous update statement in the same transaction, only the first update is stored (see attached SQL test). This is because the subsequent updates are only inserted uBAT, but not replaced into it. The attached patch fixes this, and seems to be stable for me so far.
This bug report is based on a mailing list question where the same issue was observed on a Feb2010 branch build. I did not verify this, but it might well be that the same patch could also help on that branch.
> Attached file: [multiple-updates-in-transaction.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2543_multiple-updates-in-transaction.sql_5) (application/octet-stream, 469 bytes)
> Description: SQL code to show the issue
## Comment 14047
Date: 2010-05-19 11:34:26 +0200
From: zeuner <<zeuner>>
Created attachment 6
possible fix
> Attached file: [override-previous-updates.diff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2543_override-previous-updates.diff_6) (text/plain, 305 bytes)
> Description: possible fix
## Comment 14135
Date: 2010-06-21 20:04:04 +0200
From: @njnes
Changeset [86afee7de2ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=86afee7de2ff) 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=86afee7de2ff](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=86afee7de2ff)
Changeset description:
add test for
Bugzilla Bug #2543 multiple update statements in one transaction lose updates
## Comment 14136
Date: 2010-06-21 20:05:06 +0200
From: @njnes
added test to src/test/BugTracker-2010/Tests/multiple-updates-in-transaction.Bug-2543.sql
applied fix. Indeed we need to keep updated values.
## Comment 14137
Date: 2010-06-21 20:26:55 +0200
From: @njnes
Changeset [063cbe9c5b78](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=063cbe9c5b78) 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=063cbe9c5b78](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=063cbe9c5b78)
Changeset description:
add test for
Bugzilla Bug #2543 multiple update statements in one transaction lose updates
(transplanted from 86afee7de2ff4755b3679d935a99d13023c7e5dc)
## Comment 14737
Date: 2010-08-19 17:47:02 +0200
From: @sjoerdmullender
This was released in the Jun2010-SP1 release.
| multiple update statements in one transaction lose updates | https://api.github.com/repos/MonetDB/MonetDB/issues/2543/comments | 0 | 2020-11-30T11:02:19Z | 2024-06-27T11:47:27Z | https://github.com/MonetDB/MonetDB/issues/2543 | 753,378,512 | 2,543 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-18 16:38:11 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @drstmane
Last updated: 2010-07-12 12:50:02 +0200
## Comment 14045
Date: 2010-05-18 16:38:11 +0200
From: @sjoerdmullender
When starting a server (up-to-date Jun2010 branch) with a SQL database created with the Feb2010 release, I get the error:
!mvc_init: unable to create system tables
!SQLException:SQLinit:Catalogue initialization failed
!ERROR: Incompatible database version 050000, this server supports version 051000
!ERROR: Please move away /ufs/sjoerd/Monet-virgin-candidate/var/MonetDB5/dbfarm/tst/sql_logs/sql/ and its corresponding dbfarm.
MonetDB/SQL module v2.38.0 loaded
!mvc_init: unable to create system tables
!SQLException:SQLinit:Catalogue initialization failed
!ERROR: Incompatible database version 050000, this server supports version 051000
!ERROR: Please move away /ufs/sjoerd/Monet-virgin-candidate/var/MonetDB5/dbfarm/tst/sql_logs/sql/ and its corresponding dbfarm.
This is a blocker issue.
## Comment 14089
Date: 2010-06-11 10:40:23 +0200
From: @sjoerdmullender
This seems to be fixed by Niels in changeset [dddadfc3d040](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dddadfc3d040)
## Comment 14366
Date: 2010-07-12 12:50:02 +0200
From: @drstmane
For a thorough test see also bug #2573.
| Feb2010 database cannot be read by Jun2010 version | https://api.github.com/repos/MonetDB/MonetDB/issues/2542/comments | 0 | 2020-11-30T11:02:16Z | 2024-06-27T11:47:26Z | https://github.com/MonetDB/MonetDB/issues/2542 | 753,378,465 | 2,542 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-17 17:38:45 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: -- development
CC: ashishk, fioravanzos, @hannesmuehleisen, mitja, @mlkersten, @njnes, @skinkie, @yzchang
Blocker for: #3162, #3160
Last updated: 2017-10-31 13:12:17 +0100
## Comment 14039
Date: 2010-05-17 17:38:45 +0200
From: @grobian
Many people from both inside as outside really need to be able to shrink their database size badly. The least we should do is implement the VACUUM TABLE <x> and VACUUM DATABASE commands to manually recreate the bats under the hood.
More advanced would be to have a auto_vacuum thing that allows to vacuum all tables at times such that no maintenance is necessary.
## Comment 14040
Date: 2010-05-17 19:58:28 +0200
From: @mlkersten
There is a relatively easy way to include a vacuum thread in the system (at least for non-string valued columns), which does not require user involvement. The bottleneck is the time/priority for development and the trickiness of getting it transaction safe.
## Comment 14140
Date: 2010-06-23 04:21:31 +0200
From: @skinkie
When the alter table/rename to is implemented, and within the vacuum transaction constraints can be temporary lifted, the only thing that should happen is:
start transaction;
insert into y select * from x order by primary key;
ignore constraints;
drop table x;
alter table y rename to x;
enforce constraints without recheck;
commit;
The rename not being available, and the significant overhead of the constraint recheck is problematic for the people that require the vacuum in the first place. The above sacrifices space, by at most two times the size, but sadly enforces a write lock at the same time.
I wonder if instead of a vacuum thread for auto_vacuum a solution could be in place that maintains (or reuses) the deleted record list, so if this list has entries, new inserts are not appended but in fact updated. This scarifies (primary key) fragmentation over space, which might, (or might not) really bother people. Applying auto_vacuum to the table should trigger the reuse list, and may if the table is not empty, execute the above vacuum method. The former will not solve the delete from x where y <> 1, (having one record remaining), a heuristic (deletelist to become > half table length) falling back to the first presented solution will. Having the delete not to delete records, but exclude them in the select into the new table. (insert into y select * from x where not(delete_where_part) order by primary key;)
## Comment 14165
Date: 2010-07-01 16:11:45 +0200
From: @sjoerdmullender
At the GDK level, code similar to fixstrheap in gdk_bbp.mx could be used to vacuum a string BAT in-place.
## Comment 14846
Date: 2010-08-30 09:23:21 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
## Comment 15687
Date: 2011-03-28 17:36:33 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16040
Date: 2011-07-29 11:00:06 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16279
Date: 2011-09-16 15:10:40 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17682
Date: 2012-08-24 14:55:58 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18115
Date: 2012-11-27 15:24:37 +0100
From: @yzchang
No test needed for feature request
## Comment 19233
Date: 2013-10-03 09:49:41 +0200
From: Ashish Kumar Singh <<ashishk>>
Hi,
Any plans for implementing this feature?
Regards,
Ashish
## Comment 24452
Date: 2016-10-04 11:07:07 +0200
From: fioravanzos
Hello, is there any plan to make the VACUUM statement stable?
Regards,
Stefano
## Comment 25827
Date: 2017-10-31 13:12:17 +0100
From: @hannesmuehleisen
There is the procedure VACUUM(schema, table) which should do what you described.
sql>create table test (i integer);
sql>insert into test values (1),(2),(3);
sql>delete from test where i > 2;
sql>call vacuum('sys', 'test');
| SQL:VACUUM TABLE and auto_vacuum badly necessary | https://api.github.com/repos/MonetDB/MonetDB/issues/2541/comments | 0 | 2020-11-30T11:02:13Z | 2024-06-28T13:40:38Z | https://github.com/MonetDB/MonetDB/issues/2541 | 753,378,433 | 2,541 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-14 11:28:53 +0200
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
Last updated: 2010-05-14 14:55:13 +0200
## Comment 14031
Date: 2010-05-14 11:28:53 +0200
From: @mlkersten
Very old feature has been lost in the swamps of time, while documentation still mention it. An import file starting with '~', '.' or '/' should overrule searching the module path for it. The resolution is performed in the context of the server process.
language.source("/tmp/test.mal");
language.source("~/test.mal");
Security can be 'ensured' by only allowing the MonetDB user 0 to use it.
## Comment 14032
Date: 2010-05-14 14:55:13 +0200
From: @mlkersten
Case 1 is resolved after bug fix by Fabian.
Case 2 '~' (and also '.') was not supported, because it depends on the context,
e.g. operating system. Better not to differentiate in the code.
| MAL: source file path resolution | https://api.github.com/repos/MonetDB/MonetDB/issues/2540/comments | 0 | 2020-11-30T11:02:10Z | 2024-06-27T11:47:24Z | https://github.com/MonetDB/MonetDB/issues/2540 | 753,378,388 | 2,540 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-14 10:20:57 +0200
From: zeuner <<zeuner>>
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @mlkersten, @njnes
Last updated: 2010-08-20 14:03:57 +0200
## Comment 14030
Date: 2010-05-14 10:20:57 +0200
From: zeuner <<zeuner>>
Created attachment 3
shell script to show the issue (needs mserver5 running)
Please see the attached shell script (creating a table and repeatedly loading string data and deleting it afterwards). The stored data never exceeds 1048576 rows and does not change, still the dbfarm grows linearly in disk usage.
Also, the mserver5 virtual memory size grows linearly, but I don't know if this is related.
Please note that I could not see any performance degradation through the growth. Just disk full conditions can become a problem at some point...
> Attached file: [dbfarm-growth.sh](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2539_dbfarm-growth.sh_3) (application/x-sh, 250 bytes)
> Description: shell script to show the issue (needs mserver5 running)
## Comment 14033
Date: 2010-05-14 22:28:51 +0200
From: @mlkersten
This sounds right. Strings are stored in the string heap and not removed when you delete the tuples themselves. Furthermore, subsequent insertion of (new) strings lead to an ever growing heap of string values.
A vacuum scheme would be needed to reduce the storage space.
## Comment 14034
Date: 2010-05-14 23:35:25 +0200
From: zeuner <<zeuner>>
Thanks for the clarification.
I would still regard the issue as a deficiency as most RDBMS would, while not necessarily freeing file system space, at least reuse the storage space where deleted data was stored without a VACUUM operation.
Is there at least a way to manually reclaim unused string storage, or is a scenario which includes changing string values bound to periodically recreate the database?
## Comment 14035
Date: 2010-05-14 23:38:36 +0200
From: @mlkersten
Copying a table into a new one will free the resources.
We agree on the vacuum feature. It is a matter of time prioritization.
True. Files are memory mapped. So the portion of 'useless' strings is not
touched.
## Comment 14036
Date: 2010-05-15 13:18:47 +0200
From: zeuner <<zeuner>>
Thanks for the hint. I tried to create an equivalent test scenario with bounded space consumption by creating a new table in each iteration before deleting the data (modified script attached). I see there is space reclaimed this way. However, on the long run it still seems to grow unboundedly. Some iterations end up with less space consumption than the previous one, but after every 250 iterations, I consistently get at least 2GB growth. Either I am missing something, or periodically using new tables is not sufficient to have bounded space requirements.
## Comment 14037
Date: 2010-05-15 13:20:58 +0200
From: zeuner <<zeuner>>
Created attachment 4
shell script to show the proposed workaround failing (needs mserver5 running)
> Attached file: [dbfarm-growth-new-tables.sh](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2539_dbfarm-growth-new-tables.sh_4) (application/x-sh, 473 bytes)
> Description: shell script to show the proposed workaround failing (needs mserver5 running)
## Comment 14177
Date: 2010-07-02 09:47:31 +0200
From: @njnes
mostly the logger has no time to flush the data. If monetdb has no active transactions for 5 minutes it will flush the tables and cleanup the used virtual memory.
## Comment 14183
Date: 2010-07-02 10:17:11 +0200
From: @njnes
correction the logger checks every 30 seconds for inactivity, if so it starts the log cleanup and frees memory. Unfortunately even then some tables remain in memory and on disk (incorrectly), ie we seems to leak.
## Comment 14190
Date: 2010-07-02 13:19:49 +0200
From: @njnes
Fixed the leak. Todo add test for this to test web.
## Comment 14191
Date: 2010-07-02 13:24:44 +0200
From: @grobian
fixed on Jun2010 branch
## Comment 14736
Date: 2010-08-19 17:35:13 +0200
From: @sjoerdmullender
This was released in the Jun2010-SP1 release.
| physical dbfarm storage size grows linearly while logical data size stays bounded | https://api.github.com/repos/MonetDB/MonetDB/issues/2539/comments | 0 | 2020-11-30T11:02:06Z | 2024-06-27T11:47:23Z | https://github.com/MonetDB/MonetDB/issues/2539 | 753,378,340 | 2,539 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-13 23:08:15 +0200
From: Jan Rittinger <<jan.rittinger>>
To: buildtools devs <<bugs-buildtools>>
Version: -- development
Last updated: 2010-08-20 14:03:55 +0200
## Comment 14029
Date: 2010-05-13 23:08:15 +0200
From: Jan Rittinger <<jan.rittinger>>
Currently de-bootstrap asks the user to check the accidental removal via cvs:
It might be a good idea to run "cvs -q diff --brief", now,
to check whether required files have been removed accidently.
If so, these files can be restored by "cvs update <file>".
## Comment 14079
Date: 2010-06-02 16:35:51 +0200
From: @sjoerdmullender
Fixed in all branches. Please check.
| de-bootstrap contains cvs references | https://api.github.com/repos/MonetDB/MonetDB/issues/2538/comments | 0 | 2020-11-30T11:02:03Z | 2024-06-27T11:47:22Z | https://github.com/MonetDB/MonetDB/issues/2538 | 753,378,287 | 2,538 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-11 14:57:30 +0200
From: Alex <<M8R-i23u8t>>
To: SQL devs <<bugs-sql>>
Version: 2.36.3 (Feb2010-SP1) [obsolete]
CC: @njnes
Last updated: 2010-05-18 14:26:31 +0200
## Comment 14016
Date: 2010-05-11 14:57:30 +0200
From: Alex <<M8R-i23u8t>>
-- Server crashes:
INSERT INTO Image
(ImageId
,imageBinaries)
VALUES
(MAX(ImageId)+1,'data');
-- Server crashes not:
INSERT INTO Image
(ImageId
,imageBinaries)
VALUES
( (SELECT MAX(ImageId)+1 from Image),'data');
-- MonetDB server v5.18.1, based on kernel v1.36.1
## Comment 14355
Date: 2010-07-10 10:01:50 +0200
From: @drstmane
Changeset [c29148e9f9f2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=c29148e9f9f2) 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=c29148e9f9f2](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=c29148e9f9f2)
Changeset description:
added test for bug #2537
| Server crashes if subselect is used in insert statement without 'select' | https://api.github.com/repos/MonetDB/MonetDB/issues/2537/comments | 0 | 2020-11-30T11:02:00Z | 2024-06-27T11:47:21Z | https://github.com/MonetDB/MonetDB/issues/2537 | 753,378,242 | 2,537 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-11 14:35:21 +0200
From: Jan Rittinger <<jan.rittinger>>
To: Jan Rittinger <<jan.rittinger>>
Version: 1.38.1 (Jun2010) [obsolete]
CC: bugs-common
Last updated: 2010-08-30 09:02:02 +0200
## Comment 14015
Date: 2010-05-11 14:35:21 +0200
From: Jan Rittinger <<jan.rittinger>>
ac_cv_func_fdatasync is set to yes, irrespective of the following check in configure.ag:
OSX 10.6 (Snow Leopard) somehow makes configure believe that fdatasync
exists, in reality however, it does not on this platform.
AC_CACHE_CHECK([for fdatasync],[ac_cv_func_fdatasync],[
AC_LINK_IFELSE([AC_LANG_PROGRAM([[
include <unistd.h>
]],[[
fdatasync(4);
]])],
[ac_cv_func_fdatasync=yes],
[ac_cv_func_fdatasync=no])
])
AS_IF([test "x${ac_cv_func_fdatasync}" = "xyes"],
[AC_DEFINE([HAVE_FDATASYNC],[1],[If the system has a working fdatasync])])
## Comment 14017
Date: 2010-05-11 15:18:25 +0200
From: @grobian
Changeset [0fe17ca4e57e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0fe17ca4e57e) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0fe17ca4e57e](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0fe17ca4e57e)
Changeset description:
Don't use fdatasync on OSX Snow Leopard, bug #2536.
It seems we cannot easily get around a bug in Snow Leopard that makes
configure believe that fdatasync exists. As a last resort, just skip
the check if the system is Snow Leopard.
## Comment 14018
Date: 2010-05-11 15:23:03 +0200
From: @grobian
Jan, can you check if the patch works sufficiently now?
## Comment 14735
Date: 2010-08-19 17:20:17 +0200
From: @sjoerdmullender
Repeating Fabian's question which you may not have seen:
Jan, can you check if the patch works sufficiently now?
## Comment 14782
Date: 2010-08-30 09:02:02 +0200
From: Jan Rittinger <<jan.rittinger>>
It works.
| configure for fdatasync not working on OS X 10.6 | https://api.github.com/repos/MonetDB/MonetDB/issues/2536/comments | 0 | 2020-11-30T11:01:57Z | 2024-06-27T11:47:20Z | https://github.com/MonetDB/MonetDB/issues/2536 | 753,378,214 | 2,536 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-11 14:29:45 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 2.36.5 (Feb2010-SP2) [obsolete]
CC: @njnes
Last updated: 2010-05-18 12:57:28 +0200
## Comment 14014
Date: 2010-05-11 14:29:45 +0200
From: @grobian
Seems lhs related:
sql>select (select count(*) from _tables) > 5;
+-------+
| >_L15 |
+=======+
| true |
+-------+
1 tuple
sql>select 5 < (select count(*) from _tables);
MAPI = monetdb@localhost:60000
ACTION= read_line
QUERY = select 5 < (select count(*) from _tables);
ERROR = !Connection terminated
MonetDB server v5.18.6, based on kernel v1.36.6
Serving database 'demo', using 4 threads
Compiled for x86_64-pc-linux-gnu/64bit with 64bit OIDs dynamically linked
Found 7.751 GiB available main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2010 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /ufs/fabian/scratch/monetdb/Feb2010/program-x86_64/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:60000/
MonetDB/SQL module v2.36.6 loaded
>mserver5: /ufs/fabian/scratch/monetdb/Feb2010/sql/src/server/rel_select.mx:708: rel_project_add_exp: Assertion `(rel->op == op_project || rel->op == op_groupby || (rel->op == op_union || rel->op == op_inter || rel->op == op_except))' failed.
Abort
The same happens when the query is prepared.
## Comment 14042
Date: 2010-05-18 12:56:47 +0200
From: @njnes
Changeset [46e4a05e82ac](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=46e4a05e82ac) 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=46e4a05e82ac](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=46e4a05e82ac)
Changeset description:
fix bug #2535 (handle in selection reversed predicates)
## Comment 14043
Date: 2010-05-18 13:00:16 +0200
From: @njnes
Changeset [6d0e16d9caf3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6d0e16d9caf3) 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=6d0e16d9caf3](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6d0e16d9caf3)
Changeset description:
fix bug #2535 (handle in selection reversed predicates)
(transplanted from 46e4a05e82ac932a463934a05d8d12add474693f)
## Comment 14354
Date: 2010-07-10 10:01:49 +0200
From: @drstmane
Changeset [a6cd9e12ddd6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=a6cd9e12ddd6) 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=a6cd9e12ddd6](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=a6cd9e12ddd6)
Changeset description:
added test for bug #2535
| Crash on x < (select count(*) ...) construct | https://api.github.com/repos/MonetDB/MonetDB/issues/2535/comments | 0 | 2020-11-30T11:01:54Z | 2024-06-27T11:47:19Z | https://github.com/MonetDB/MonetDB/issues/2535 | 753,378,171 | 2,535 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-11 14:26:32 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 2.36.5 (Feb2010-SP2) [obsolete]
CC: @njnes, @drstmane
Last updated: 2010-07-10 10:04:10 +0200
## Comment 14013
Date: 2010-05-11 14:26:32 +0200
From: @grobian
Consider the following:
sql>prepare select count(*) from _tables having count(*) > ?;
execute prepared statement using: EXEC 0(...)
+------------------------+--------------------------+--------------------------+
| type | digits | scale |
+========================+==========================+==========================+
| wrd | 64 | 0 |
+------------------------+--------------------------+--------------------------+
1 tuple
sql>exec 0(4);
SQLException:sql.prepare:wrong type for argument 1 of prepared statement: tinyint, expected wrd
sql>
## Comment 14041
Date: 2010-05-18 12:56:46 +0200
From: @njnes
Changeset [1ec3f6727269](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1ec3f6727269) 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=1ec3f6727269](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1ec3f6727269)
Changeset description:
fixed bug #2534 (handle type wrd in atom_cast)
## Comment 14044
Date: 2010-05-18 13:00:17 +0200
From: @njnes
Changeset [ccafaf835054](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ccafaf835054) 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=ccafaf835054](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ccafaf835054)
Changeset description:
fixed bug #2534 (handle type wrd in atom_cast)
(transplanted from 1ec3f6727269c8db9eb40c6dd78c1d988d184cbb)
## Comment 14356
Date: 2010-07-10 10:04:10 +0200
From: @drstmane
Changeset [1e48c4327e11](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1e48c4327e11) 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=1e48c4327e11](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1e48c4327e11)
Changeset description:
added test for bugs 2533 & 2534
## Comment 16766
Date: 2012-01-12 09:34:21 +0100
From: @drstmane
Changeset [b70b62559ab7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b70b62559ab7) 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=b70b62559ab7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b70b62559ab7)
Changeset description:
fixed crash (segfault) in tests:
test/BugDay_2005-10-06_2.9.3/having.SF-922614
test/BugTracker-2009/TribooleanFailureWithSubquery.SF-2679434
test/BugTracker-2010/prepare_stmt.Bug-2533.Bug-2534
| Prepared statement with wrd arg type cannot be used | https://api.github.com/repos/MonetDB/MonetDB/issues/2534/comments | 0 | 2020-11-30T11:01:51Z | 2024-06-27T11:47:18Z | https://github.com/MonetDB/MonetDB/issues/2534 | 753,378,126 | 2,534 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-11 13:19:36 +0200
From: @grobian
To: SQL devs <<bugs-sql>>
Version: 2.36.3 (Feb2010-SP1) [obsolete]
CC: @njnes
Last updated: 2010-05-18 14:33:38 +0200
## Comment 14010
Date: 2010-05-11 13:19:36 +0200
From: @grobian
SQLException:sql.prepare:wrong argument for prepared statement (expected wrd instead of tinyint)
In general, it would be helpful if the SQLExceptions provided a hint on which
database column(s) or parameters a exception was triggered.
## Comment 14011
Date: 2010-05-11 13:59:56 +0200
From: @grobian
Changeset [b72683cabccb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b72683cabccb) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b72683cabccb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b72683cabccb)
Changeset description:
Report which argument is of the wrong type, resolves bug #2533.
For prepared statement and function calls, if an error is returned
because of a conflicting type, now the argument number is also reported
to ease tracking back which caused the trouble.
Thanks Alexander Braun (SkyTec) for reporting.
## Comment 14012
Date: 2010-05-11 14:09:00 +0200
From: @grobian
implemented in
[http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b72683cabccb](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b72683cabccb)
## Comment 14353
Date: 2010-07-10 10:01:48 +0200
From: @drstmane
Changeset [1e48c4327e11](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=1e48c4327e11) 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=1e48c4327e11](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=1e48c4327e11)
Changeset description:
added test for bugs 2533 & 2534
## Comment 16765
Date: 2012-01-12 09:34:21 +0100
From: @drstmane
Changeset [b70b62559ab7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b70b62559ab7) 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=b70b62559ab7](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b70b62559ab7)
Changeset description:
fixed crash (segfault) in tests:
test/BugDay_2005-10-06_2.9.3/having.SF-922614
test/BugTracker-2009/TribooleanFailureWithSubquery.SF-2679434
test/BugTracker-2010/prepare_stmt.Bug-2533.Bug-2534
| Prepared statement errors to report column that caused the problem | https://api.github.com/repos/MonetDB/MonetDB/issues/2533/comments | 0 | 2020-11-30T11:01:48Z | 2024-06-27T11:47:17Z | https://github.com/MonetDB/MonetDB/issues/2533 | 753,378,089 | 2,533 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-11 10:24:44 +0200
From: Manuel Mayr <<mayrm>>
To: buildtools devs <<bugs-buildtools>>
Version: -- development
CC: @drstmane
Last updated: 2010-07-09 11:12:31 +0200
## Comment 14008
Date: 2010-05-11 10:24:44 +0200
From: Manuel Mayr <<mayrm>>
Bootstrapping the buildtools on OSX with autoconf 2.64 results in the following error message:
$ ./bootstrap
/Users/mayr/Science/Diss/MonetDB/buildtools/Mx
aclocal.m4:14: error: this file was generated for autoconf 2.61.
You have another version of autoconf. If you want to use that,
you should regenerate the build system entirely.
aclocal.m4:14: the top level
autom4te: /opt/local/bin/gm4 failed with exit status: 63
autoheader: '/opt/local/bin/autom4te' failed with exit status: 63
$ autoconf -V
autoconf (GNU Autoconf) 2.64
Falling back to the autoconf version the error message above suggests (2.61) helps
in my case.
buildtools/Mx/aclocal.m4:14 => seems to require autoconf 2.61
## Comment 14009
Date: 2010-05-11 13:15:07 +0200
From: @grobian
aclocal.m4 is as the name suggests a locally generated file. Did you run a de-bootstrap before trying to bootstrap again using your updated autoconf?
## Comment 14038
Date: 2010-05-15 21:38:20 +0200
From: @drstmane
Manuel,
could you please report whether removing the bootstrap generated aclocal.m4, e.g., by running ./de-bootstrap, did solve your problem?
And if so, could you please also close this bug report?
Thanks!
Stefan
## Comment 14277
Date: 2010-07-09 11:12:31 +0200
From: @grobian
This is typically caused by not properly regenerating the autotools files. We use autoconf-2.65 and autoconf-2.66 without problems.
| bootstrap fails with autoconf 2.64 | https://api.github.com/repos/MonetDB/MonetDB/issues/2532/comments | 0 | 2020-11-30T11:01:45Z | 2024-06-28T13:21:54Z | https://github.com/MonetDB/MonetDB/issues/2532 | 753,378,048 | 2,532 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-07 10:00:18 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2010-05-07 10:18:18 +0200
## Comment 14006
Date: 2010-05-07 10:00:18 +0200
From: @mlkersten
Noticed that the query cache matching needs another check
The query cache does not seem to catch identical plans.
>create function queryCache()
returns table (query string, count int)
external name sql.dump_cache;
&3
>select count(*) from tables;
&1 0 1 1 1
% .tables table_name
% L1 name
% wrd type
% 2 length
[ 26 ]
>select count(*) from tables;
&1 0 1 1 1
% .tables table_name
% L2 name
% wrd type
% 2 length
[ 26 ]
>select * from queryCache();
&1 0 3 2 3
% ., . table_name
% query, count name
% clob, int type
% 28, 1 length
[ "select * from querycache();", 1 ]
[ "select count(*) from tables;", 1 ]
[ "select count(*) from tables;", 1 ]
## Comment 14007
Date: 2010-05-07 10:18:18 +0200
From: @mlkersten
They can not be matched because, in general, the scheme of the table could have been changed. This can not be detected from this query alone.
| SQL: Query cache management | https://api.github.com/repos/MonetDB/MonetDB/issues/2531/comments | 0 | 2020-11-30T11:01:41Z | 2024-06-28T13:21:53Z | https://github.com/MonetDB/MonetDB/issues/2531 | 753,378,020 | 2,531 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-06 15:55:34 +0200
From: zeuner <<zeuner>>
To: GDK devs <<bugs-common>>
Version: 1.40.1 (Oct2010) [obsolete]
CC: zeuner
Last updated: 2010-10-28 13:21:35 +0200
## Comment 14005
Date: 2010-05-06 15:55:34 +0200
From: zeuner <<zeuner>>
I am irregularly getting this assertion when running updates and queries against SQL/MonetDB5:
mserver5: gdk_bat.mx:1861: void_inplace: Assertion `b->U->count > (id -b->H->seq)' failed.
The complete SQL code sent to the mserver5 is rather large, which makes it laborious to isolate a test case. So any pointers on how to put the assertion in context of overall expected server behaviour, or how to further narrow the problem down, would be greatly appreciated.
## Comment 15132
Date: 2010-10-28 13:21:35 +0200
From: @grobian
Does this still happen with the latest release, and more importantly with the next release candidate (Oct2010?)
| gdk_bat.mx / void_inplace assertion failure | https://api.github.com/repos/MonetDB/MonetDB/issues/2530/comments | 0 | 2020-11-30T11:01:38Z | 2024-06-27T11:47:14Z | https://github.com/MonetDB/MonetDB/issues/2530 | 753,377,975 | 2,530 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-05 03:23:25 +0200
From: zeuner <<zeuner>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes, zeuner
Last updated: 2010-08-30 09:18:31 +0200
## Comment 13998
Date: 2010-05-05 03:23:25 +0200
From: zeuner <<zeuner>>
Created attachment 1
SQL code to show the issue
By slightly changing the test submitted with bug http://bugs.monetdb.org/show_bug.cgi?id=2361, I was able
to trigger an unrelated bug (see the attached test file
fallback-bid-collision.sql). In sql/src/storage/bat/bat_storage.mx,
function delta_bind_bat, the conditional (temp || access == RD_INS ||
!bat->bid) leads to the iBAT being returned even if the main BAT is
requested by sql.bind(...,0), when there is no main BAT in the
sql_delta structure. As long as sql.bind(...,0) and sql.bind(...,1)
are combined using algebra.kunion, this doesn't seem to create
problems. But the mergetable optimizer's logic to optimize union
computations based on overlapped MAT elements does not interact
correctly with that behaviour, which leads to the data being inserted
twice in the test file.
I have attached a patch (no-fallback-ibid.diff) which avoids this
problem by disabling the iBAT fallback, creating an empty main BAT
instead.
> Attached file: [fallback-bid-collision.sql](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2529_fallback-bid-collision.sql_1) (text/plain, 975 bytes)
> Description: SQL code to show the issue
## Comment 13999
Date: 2010-05-05 03:28:34 +0200
From: zeuner <<zeuner>>
Created attachment 2
possible fix
> Attached file: [no-fallback-ibid.diff](https://github.com/MonetDB/monetdb-issues-attachments/blob/master/issue_2529_no-fallback-ibid.diff_2) (text/plain, 600 bytes)
> Description: possible fix
## Comment 14207
Date: 2010-07-02 23:25:20 +0200
From: @njnes
fixed by returning empty bat, when the primary bat is gone because of a 'delete all'
## Comment 14208
Date: 2010-07-02 23:27:50 +0200
From: @njnes
Changeset [d8a41f812526](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d8a41f812526) 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=d8a41f812526](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d8a41f812526)
Changeset description:
fixed bug #2529
In case we did a delete all, the primary bat is gone. Before we
returned the ibat (twice). Now only when the inserts are needed and
an empty bat when the primary bat is requested.
## Comment 14209
Date: 2010-07-02 23:27:51 +0200
From: @njnes
Changeset [e7065770051d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e7065770051d) 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=e7065770051d](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e7065770051d)
Changeset description:
added tests for bug #2529
## Comment 14825
Date: 2010-08-30 09:18:31 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| main BAT fallback creates collision | https://api.github.com/repos/MonetDB/MonetDB/issues/2529/comments | 0 | 2020-11-30T11:01:36Z | 2024-06-27T11:47:13Z | https://github.com/MonetDB/MonetDB/issues/2529 | 753,377,945 | 2,529 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-05-04 22:02:28 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2010-05-18 14:27:26 +0200
## Comment 13995
Date: 2010-05-04 22:02:28 +0200
From: @mlkersten
A few basket expression tests have been added in src/datacell/Tests
which produced either a segfault or incorrect code.
| SQL: Basket expressions | https://api.github.com/repos/MonetDB/MonetDB/issues/2528/comments | 0 | 2020-11-30T11:01:32Z | 2024-06-27T11:47:12Z | https://github.com/MonetDB/MonetDB/issues/2528 | 753,377,903 | 2,528 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-04-02 01:46:44 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2011-01-25 15:36:16 +0100
## Comment 13962
Date: 2010-04-02 13:46:44 +0200
From: @mlkersten
Currently \d is only available as part of mclient and indirectly by the enriched APIs. To create self-contained SQL scripts for dump/restor portions, it would be helpful if the DESCRIBE option was available as a SQL statement. In line with EXPLAIN, TRACE, DEBUG.
describe_stmt:
DESCRIBE [ TABLE | VIEW | SCHEMA | FUNCTION | TRIGGER ] name
## Comment 13963
Date: 2010-04-02 14:17:00 +0200
From: @grobian
what's the application scenario in mind here? Doesn't msqldump create a "self-contained SQL script for dump/restore"?
## Comment 13964
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2981074 at http://sourceforge.net/support/tracker.php?aid=2981074
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 15435
Date: 2011-01-25 15:36:16 +0100
From: @grobian
\d and mysqldump work for me
| SQL: DESCRIBE | https://api.github.com/repos/MonetDB/MonetDB/issues/2527/comments | 0 | 2020-11-30T11:01:29Z | 2024-06-28T13:42:19Z | https://github.com/MonetDB/MonetDB/issues/2527 | 753,377,861 | 2,527 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-04-02 09:43:07 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: 11.27.13 (Jul2017-SP4)
CC: akhilesh.visouriya, Erietta.Liarou, sreejith.sharma
Last updated: 2019-02-28 16:02:17 +0100
## Comment 13960
Date: 2010-04-02 09:43:07 +0200
From: @mlkersten
SQL supports 3-level naming. We do 2 with a warning when calling the 3-level [[database_name '.'] correlation_name '.']column_name
## Comment 13961
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2981001 at http://sourceforge.net/support/tracker.php?aid=2981001
## Comment 17086
Date: 2012-03-15 18:17:21 +0100
From: @sjoerdmullender
*** Bug #2854 has been marked as a duplicate of this bug. ***
## Comment 17088
Date: 2012-03-15 18:17:59 +0100
From: @sjoerdmullender
*** Bug #3062 has been marked as a duplicate of this bug. ***
## Comment 26911
Date: 2019-02-28 15:24:17 +0100
From: Akhilesh <<akhilesh.visouriya>>
Hi Team,
We are facing performance issue while executing below queries, taking around 45 mins after creating partitions(Merge table concept) and order index.
We are using 100 CPU Cores linux machine and having sufficient memory.
Without applying Merge table concept, query just keep running and not coming out, then we are killing forcibly.
1) SELECT M_key, ID FROM "TABLE_TEST" WHERE ID IN (<50,000 UNIQUE IDS>);
2) SELECT COUNT(*) FROM "TABLE_TEST" WHERE ID IN (<50,000 UNIQUE IDS>);
Table "TABLE_TEST" having 122 million rows and 60 columns(data type INT).
We created 10 partitions using Merge table concept, and applied order index in column ID post partitions.
Column ID used in 'IN' clause is primary key.
Could you please help us in solving this issue ?
Thanks in advance.
Regards,
Akhilesh
## Comment 26912
Date: 2019-02-28 16:02:17 +0100
From: @sjoerdmullender
Please open a new bug report for a new issue. This has nothing whatsoever to do with three-level naming.
| SQL: level 3 naming | https://api.github.com/repos/MonetDB/MonetDB/issues/2526/comments | 1 | 2020-11-30T11:01:26Z | 2024-06-28T13:42:18Z | https://github.com/MonetDB/MonetDB/issues/2526 | 753,377,808 | 2,526 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-04-01 08:34:52 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: duc
Last updated: 2016-04-11 11:45:36 +0200
## Comment 13958
Date: 2010-04-01 20:34:52 +0200
From: @mlkersten
Todo: use CSV files to populate tables automatically.
## Comment 13959
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2980676 at http://sourceforge.net/support/tracker.php?aid=2980676
| SQL: CSV Vaults | https://api.github.com/repos/MonetDB/MonetDB/issues/2525/comments | 0 | 2020-11-30T11:01:23Z | 2024-06-28T13:42:17Z | https://github.com/MonetDB/MonetDB/issues/2525 | 753,377,754 | 2,525 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-03-28 12:40:17 +0200
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2011-01-25 15:37:58 +0100
## Comment 13956
Date: 2010-03-28 12:40:17 +0200
From: @mlkersten
Make the binary attachment complete by provision of the COPY INTO variant.
## Comment 13957
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2977953 at http://sourceforge.net/support/tracker.php?aid=2977953
## Comment 15436
Date: 2011-01-25 15:37:58 +0100
From: @grobian
doesn't this already exist? bat attach
| SQL: COPY INTO BINARY | https://api.github.com/repos/MonetDB/MonetDB/issues/2524/comments | 0 | 2020-11-30T11:01:20Z | 2024-06-27T11:47:08Z | https://github.com/MonetDB/MonetDB/issues/2524 | 753,377,720 | 2,524 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-03-19 03:01:10 +0100
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2010-03-19 04:42:53 +0100
## Comment 13953
Date: 2010-03-19 15:01:10 +0100
From: @skinkie
As part of the mapreduce functionality I wonder if this technological advantage can also be used to do a join between two different databases.
## Comment 13954
Date: 2010-03-19 16:42:52 +0100
From: @mlkersten
The combinations of technologies are not related. As such this feature request will never be granted the way it is posed. Heterogenous distributed database processing goes beyond single joins, and the scope of map-reduce for distributed querying is limited.
## Comment 13955
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2973202 at http://sourceforge.net/support/tracker.php?aid=2973202
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Join between two different databases | https://api.github.com/repos/MonetDB/MonetDB/issues/2523/comments | 0 | 2020-11-30T11:01:18Z | 2024-06-28T13:42:17Z | https://github.com/MonetDB/MonetDB/issues/2523 | 753,377,683 | 2,523 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-03-09 11:22:00 +0100
From: Mitja Kleider <<mkleider>>
To: SQL devs <<bugs-sql>>
Version: 2.38.1 (Jun2010)
CC: @mlkersten
Last updated: 2010-08-20 14:04:04 +0200
## Comment 13950
Date: 2010-03-09 23:22:00 +0100
From: Mitja Kleider <<mkleider>>
I would like to use merovingian and load the geom module as if I would
be running
> mserver5 --dbinit="include geom;include sql;sql.start();"
## Comment 13951
Date: 2010-03-25 04:17:37 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: intronic@users.sourceforge.net ----
me too
## Comment 13952
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2967006 at http://sourceforge.net/support/tracker.php?aid=2967006
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-merovingian@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 14000
Date: 2010-05-05 15:02:42 +0200
From: @grobian
After some thinking, this is best solved by deploying a modules.autoload scheme in mserver5. This could solve problems that are related to this, like rdf.
## Comment 14001
Date: 2010-05-05 15:30:17 +0200
From: @mlkersten
You can always set the variable "dbinit" in the monetdb.conf file. Its value is taken unless overruled on the command line. The drawback is that it holds for all
databases served.
Merovingian might consider facilitating arbitrary setting of environment
variables for mserver5 calls
## Comment 14002
Date: 2010-05-05 15:32:12 +0200
From: @mlkersten
Furthermore, the string value is interpreted as a MAL block, which means you can practically encoded anything you like, e.g. reading a local file to further initialize the system.
## Comment 14003
Date: 2010-05-05 15:34:06 +0200
From: @grobian
I'm working on a proper solution here.
## Comment 14019
Date: 2010-05-12 16:58:18 +0200
From: @grobian
Changeset [e1c42586a988](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=e1c42586a988) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e1c42586a988](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=e1c42586a988)
Changeset description:
Put start scripts in autoload directory for modules installed.
For bug #2522, generate start scripts in the autoload directory of the
MonetDB5 libdir that are loaded from mal_init. This way, only when a
module is available, it will be attempted to be loaded, avoiding
needless worrying warnings and allowing Testing to control which modules
are loaded and which not.
## Comment 14028
Date: 2010-05-13 19:36:13 +0200
From: @grobian
Changeset [d0e8c79678ab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=d0e8c79678ab) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d0e8c79678ab](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=d0e8c79678ab)
Changeset description:
Put start scripts in autoload directory for modules installed.
For bug #2522, generate start scripts in the autoload directory of the
MonetDB5 libdir that are loaded from mal_init. This way, only when a
module is available, it will be attempted to be loaded, avoiding
needless worrying warnings and allowing Testing to control which modules
are loaded and which not.
## Comment 14146
Date: 2010-06-28 18:14:47 +0200
From: @sjoerdmullender
In the upcoming Jun2010 release, the geom module will automatically be loaded, if it was installed.
## Comment 14734
Date: 2010-08-19 17:18:25 +0200
From: @sjoerdmullender
This is in the Jun2010 release.
| automatically load geom module if it exists. | https://api.github.com/repos/MonetDB/MonetDB/issues/2522/comments | 0 | 2020-11-30T11:01:15Z | 2024-06-27T11:47:06Z | https://github.com/MonetDB/MonetDB/issues/2522 | 753,377,644 | 2,522 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-03-08 02:33:22 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2016-04-11 11:44:47 +0200
## Comment 13948
Date: 2010-03-08 14:33:22 +0100
From: @skinkie
CREATE TABLE "sys"."node_tags" (
"node" int,
"k" varchar(255),
"v" varchar(1024),
CONSTRAINT "pk_node_tags" UNIQUE ("node", "k", "v"),
CONSTRAINT "fk_node_tags_node" FOREIGN KEY ("node") REFERENCES "sys"."nodes_legacy" ("id")
);
The above table results in a SQL catalogue that knows the way,k,v properties should be unique. The following query could therefore be answered as 0 results.
select count(node), node, k, v from node_tags group by node, k, v having count(node) > 1;
While for the following query the entire table can be returned:
select count(node), node, k, v from node_tags group by node, k, v having count(node) = 1;
Since the BAT information is not available between BATs, but is in the SQL catalogue, it can be a relational algebra optimisation step.
## Comment 13949
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2965433 at http://sourceforge.net/support/tracker.php?aid=2965433
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| Optimise out group by operator in SQL level by constraint | https://api.github.com/repos/MonetDB/MonetDB/issues/2521/comments | 0 | 2020-11-30T11:01:12Z | 2024-06-28T13:42:16Z | https://github.com/MonetDB/MonetDB/issues/2521 | 753,377,596 | 2,521 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-02-19 08:19:22 +0100
From: Mitja Kleider <<mkleider>>
To: clients devs <<bugs-clients>>
Version: -- development
CC: @gijzelaerr
Last updated: 2010-05-13 14:53:32 +0200
## Comment 13946
Date: 2010-02-19 20:19:22 +0100
From: Mitja Kleider <<mkleider>>
>>> cursor.execute('SELECT * FROM nodes_legacy')
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python2.6/monetdb/sql/cursors.py", line 203, in execute
self.__store_result(block)
File "/usr/lib/python2.6/monetdb/sql/cursors.py", line 445, in __store_result
values = self.__parse_tuple(line)
File "/usr/lib/python2.6/monetdb/sql/cursors.py", line 526, in __parse_tuple
zip(elements, self.description)])
File "/usr/lib/python2.6/monetdb/sql/converters.py", line 140, in convert
return self.mapping[type_code](data)
KeyError: 'timestamptz'
## Comment 13947
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2955128 at http://sourceforge.net/support/tracker.php?aid=2955128
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 14023
Date: 2010-05-13 14:52:42 +0200
From: @gijzelaerr
Changeset [63a11eca5310](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=63a11eca5310) made by Gijs Molenaar <gijs.molenaar@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=63a11eca5310](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=63a11eca5310)
Changeset description:
fixed bug #2520, added support for undocumented field timestamptz
## Comment 14024
Date: 2010-05-13 14:53:32 +0200
From: @gijzelaerr
Sorry for the delay, i missed this bugreport. timestamptz is processed by the latest monetdb Python API version now.
| python monetdb.sql: timestamptz not supported | https://api.github.com/repos/MonetDB/MonetDB/issues/2520/comments | 0 | 2020-11-30T11:01:09Z | 2024-06-27T11:47:04Z | https://github.com/MonetDB/MonetDB/issues/2520 | 753,377,571 | 2,520 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-30 11:34:21 +0100
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
Duplicates: #2517
Last updated: 2011-07-05 17:40:52 +0200
## Comment 13944
Date: 2010-01-30 11:34:21 +0100
From: @mlkersten
CREATE TABLE "pages" (
"id" int NOT NULL AUTO_INCREMENT,
"page" varchar(1024) NOT NULL,
PRIMARY KEY ("id")
);
An input file with just the information should be sufficient, e.g.
copy records into pages(page) from 'file';
should be sufficient.
Also, the copy code does not require key constraint check
to he generated.
## Comment 13945
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2942760 at http://sourceforge.net/support/tracker.php?aid=2942760
## Comment 15897
Date: 2011-07-05 17:40:52 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #2517 ***
| SQL: COPY INTO projected table | https://api.github.com/repos/MonetDB/MonetDB/issues/2519/comments | 0 | 2020-11-30T11:01:06Z | 2024-06-28T13:42:15Z | https://github.com/MonetDB/MonetDB/issues/2519 | 753,377,526 | 2,519 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-11 02:49:02 +0100
From: Guillaume Yziquel <<yziquel>>
To: @sjoerdmullender
Version: -- development
Last updated: 2010-02-10 03:20:09 +0100
## Comment 13939
Date: 2010-01-11 02:49:02 +0100
From: Guillaume Yziquel <<yziquel>>
The Debian binary packages distribute an embeddedclient.h targetted at SQL, and not MAL. Therefore, the embedded_mal symbol of libembeddedmal.so does not have a header. Of course, you can always rewrite it yourself, but it would be cleaner if it were distributed with the binary package.
## Comment 13940
Date: 2010-01-11 17:36:41 +0100
From: @sjoerdmullender
Fixed in CVS (but not yet tested).
## Comment 13941
Date: 2010-01-26 03:20:16 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
## Comment 13942
Date: 2010-02-10 03:20:09 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
## Comment 13943
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2929558 at http://sourceforge.net/support/tracker.php?aid=2929558
| Debian embeddedclient.h forgot MAL | https://api.github.com/repos/MonetDB/MonetDB/issues/2518/comments | 0 | 2020-11-30T11:01:02Z | 2024-06-28T13:42:14Z | https://github.com/MonetDB/MonetDB/issues/2518 | 753,377,469 | 2,518 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-08 08:06:25 +0100
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2012-05-09 17:21:17 +0200
## Comment 13936
Date: 2010-01-08 20:06:25 +0100
From: @mlkersten
CREATE TABLE "pages" (
"id" int NOT NULL AUTO_INCREMENT,
"page" varchar(1024) NOT NULL,
PRIMARY KEY ("id")
);
An input file with just the information should be sufficient, e.g.
copy records into pages(page) from 'file';
should be sufficient.
Also, the copy code does not require key constraint check
to he generated.
## Comment 13937
Date: 2010-01-30 10:54:39 +0100
From: @njnes
this is a feature request
## Comment 13938
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2928456 at http://sourceforge.net/support/tracker.php?aid=2928456
## Comment 15898
Date: 2011-07-05 17:40:52 +0200
From: @sjoerdmullender
*** Bug #2519 has been marked as a duplicate of this bug. ***
| SQL: copy into issues | https://api.github.com/repos/MonetDB/MonetDB/issues/2517/comments | 0 | 2020-11-30T11:00:59Z | 2024-06-28T13:42:14Z | https://github.com/MonetDB/MonetDB/issues/2517 | 753,377,424 | 2,517 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-05 12:45:25 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2016-04-11 11:44:59 +0200
## Comment 13932
Date: 2010-01-05 12:45:25 +0100
From: @skinkie
It seems in a query like:
explain select kvk from kvk where length('hello') = length(bedrijfsnaam) and bedrijfsnaam like '%hello%';
The like operation is before the length, I have attached the mal explain of it. This is the plan:
project (
| select (
| | table(sys.kvk) [ kvk.kvk, kvk.bedrijfsnaam, kvk.%TID% NOT NULL ]
| ) [ length(kvk.bedrijfsnaam) = length('hello'), convert(kvk.bedrijfsnaam) like convert('%hello%') ]
) [ kvk.kvk ]
If like is indeed before the length equality function (it seems to be finished after the 2nd barrier), shouldn't the cost for the like operation be increased?
## Comment 13933
Date: 2010-01-05 13:29:49 +0100
From: @mlkersten
Optimizers generally do not have any knowlegde about the cost of (user-defined) functions. MonetDB does not use a cost-based reordering of the plan either to benefit from this specific case.
## Comment 13934
Date: 2010-01-05 13:53:27 +0100
From: @skinkie
It currently does do a cost assessment in exp_count(int *cnt, int seqnr, sql_exp *e), sql/src/server/rel_optimizer.mx. Is it there where a preference is set for the like operation?
Never the less, I do see your point regarding (user-defined) functions, what I do not understand is that the actual operations are also (user defined) function, for them a cost is set. It seems that the long term goal could be the dynamic cost evaluation of each function with respect to the dataset starting with the heuristic as it is set now. Regarding to this specific case what prevents adding a specific cost to the length function?
## Comment 13935
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2926187 at http://sourceforge.net/support/tracker.php?aid=2926187
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| SQL: increase cost of a like operation | https://api.github.com/repos/MonetDB/MonetDB/issues/2516/comments | 0 | 2020-11-30T11:00:56Z | 2024-06-28T13:42:13Z | https://github.com/MonetDB/MonetDB/issues/2516 | 753,377,390 | 2,516 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-05 12:35:46 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2010-01-05 01:27:06 +0100
## Comment 13926
Date: 2010-01-05 12:35:46 +0100
From: @skinkie
In a query: select * from x where a like '%%'; it is obvious to see that this query could be rewritten to select * from x; The calculation of this like expression obviously takes time. The negative case might look even more fruitful, since it can prevent an entire query from running.
## Comment 13927
Date: 2010-01-05 12:44:22 +0100
From: @grobian
you can also just not emit such a stupid query
## Comment 13928
Date: 2010-01-05 12:50:05 +0100
From: @skinkie
If I shutdown my MonetDB public server, that would probably give a performance increase as well. Anything else in the New Year, Fabian?
## Comment 13929
Date: 2010-01-05 13:02:42 +0100
From: @grobian
stop filing rediculous feature requests?
This is outside of the domain of the DBMS, the application can easily handle this.
## Comment 13930
Date: 2010-01-05 13:27:06 +0100
From: @mlkersten
This transformation is not generic enough to handle at the SQL level. It can be handled by the pcre library, providing a shortcut.
## Comment 13931
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2926181 at http://sourceforge.net/support/tracker.php?aid=2926181
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| SQL: Prevent clause, query by precomputing | https://api.github.com/repos/MonetDB/MonetDB/issues/2515/comments | 0 | 2020-11-30T11:00:52Z | 2024-06-28T07:23:09Z | https://github.com/MonetDB/MonetDB/issues/2515 | 753,377,347 | 2,515 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-26 11:33:29 +0100
From: @grobian
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2012-05-09 17:23:00 +0200
## Comment 13924
Date: 2009-12-26 11:33:29 +0100
From: @grobian
As indicated by a user on the MonetDB users mailing list, if you keep on creating prepared statements, the server will at least grow memory wise, since the server never releases the prepared statements (the execX() functions). We need an Xdestroy or similar statement to release the resources held by the prepared statements. This Xdestroy can be called by JDBC and ODBC (the primary consumers, afaict) in their close/cleanup methods.
## Comment 13925
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2921388 at http://sourceforge.net/support/tracker.php?aid=2921388
## Comment 17245
Date: 2012-05-09 17:23:00 +0200
From: @njnes
has been fixed some time ago
| SQL: ability to destroy serverside prepared statements | https://api.github.com/repos/MonetDB/MonetDB/issues/2514/comments | 0 | 2020-11-30T11:00:49Z | 2024-06-27T11:46:58Z | https://github.com/MonetDB/MonetDB/issues/2514 | 753,377,316 | 2,514 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-26 11:00:05 +0100
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
CC: holger.pirk
Last updated: 2012-11-27 11:02:06 +0100
## Comment 13922
Date: 2009-12-26 11:00:05 +0100
From: @skinkie
When the IN operator is applied on a column and the column has a zero count, the (..) does not have to be executed.
The same goes Update and Delete.
## Comment 13923
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2921380 at http://sourceforge.net/support/tracker.php?aid=2921380
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 18025
Date: 2012-11-27 11:02:06 +0100
From: Holger <<holger.pirk>>
What does "(..)" mean? Could you provide an SQL statement for this issue?
| UPDATE/DELETE/IN operator empty case | https://api.github.com/repos/MonetDB/MonetDB/issues/2513/comments | 0 | 2020-11-30T11:00:47Z | 2024-06-27T11:46:58Z | https://github.com/MonetDB/MonetDB/issues/2513 | 753,377,280 | 2,513 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-23 05:12:56 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2016-04-11 11:45:54 +0200
## Comment 13920
Date: 2009-11-23 17:12:56 +0100
From: @skinkie
Using an 'index' that is able to differentiate on stringlength a typical string lookup can be improved. Using a 2.4M row string table, the (smallint) lookup consisting of string length is done in less than 200ms. The same 'fulltext' operation using %the string%, takes around 2500ms. Using a combination string_size >= length('string') and string ilike '%string%' the first lookup time can be reduced.
The (i)like operation has be striped from modifiers, due to the constant length we can assume that the string therefore always be longer.
## Comment 13921
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2902566 at http://sourceforge.net/support/tracker.php?aid=2902566
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| SQL: Improve (i)like preformance on diverse stringdata | https://api.github.com/repos/MonetDB/MonetDB/issues/2512/comments | 0 | 2020-11-30T11:00:44Z | 2024-06-28T07:19:39Z | https://github.com/MonetDB/MonetDB/issues/2512 | 753,377,239 | 2,512 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-16 12:22:50 +0100
From: @mlkersten
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2016-04-11 11:45:08 +0200
## Comment 13916
Date: 2009-11-16 00:22:50 +0100
From: @mlkersten
The DESCRIBE {SCHEMA | TABLE | ..} <objectname> is a good start for populating a slave with the scheme information needed.
## Comment 13917
Date: 2009-11-16 10:38:28 +0100
From: @grobian
I think this is called \d in mclient or mdump --schema-only or something
## Comment 13918
Date: 2009-12-04 11:23:33 +0100
From: @mlkersten
The code for SQL dumping should be moved to the SQL source tree.
Then the \d option can be dropped in favor of the above structure.
## Comment 13919
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2898225 at http://sourceforge.net/support/tracker.php?aid=2898225
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-sql@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| SQL: describe object | https://api.github.com/repos/MonetDB/MonetDB/issues/2511/comments | 0 | 2020-11-30T11:00:41Z | 2024-06-28T07:19:39Z | https://github.com/MonetDB/MonetDB/issues/2511 | 753,377,207 | 2,511 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.