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-01-29 01:36:29 +0100
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2011-07-13 15:36:25 +0200
## Comment 12989
Date: 2010-01-29 13:36:29 +0100
From: @skinkie
I'm currently running the last 1000 queries done on the system to figure out where it went wrong, so far no luck in reproduction. Maybe someone else sees an interesting detail from this backtrace:
0 strcmp () at ../sysdeps/x86_64/strcmp.S:99
1 0x00007fffea6e488d in STRbatLower (ret=0x30161e0, l=0x3016180)
at ../../../../src/modules/kernel/batstr.mx:283
2 0x00007ffff7ae0089 in DFLOWstep (t=0x28ff388, fs=0x7fffcdd657f0)
at ../../../src/mal/mal_interpreter.mx:1796
3 0x00007ffff7ae548b in runDFLOWworker (t=0x28ff388)
at ../../../src/mal/mal_interpreter.mx:992
4 0x00007ffff579b894 in start_thread (arg=<value optimized out>)
at pthread_create.c:297
5 0x00007ffff48c8f9d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
6 0x0000000000000000 in ?? ()
## Comment 12990
Date: 2010-01-29 14:45:44 +0100
From: @skinkie
Ran last 1000 queries, nothing happened.
## Comment 12991
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2942200 at http://sourceforge.net/support/tracker.php?aid=2942200
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 15937
Date: 2011-07-13 15:36:25 +0200
From: @sjoerdmullender
Looks like a glitch, and there is no chance at all this can be reproduced.
| STRbatLower crash | https://api.github.com/repos/MonetDB/MonetDB/issues/2310/comments | 0 | 2020-11-30T10:36:45Z | 2024-06-28T07:25:38Z | https://github.com/MonetDB/MonetDB/issues/2310 | 753,360,535 | 2,310 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-24 09:21:19 +0100
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2010-01-24 11:06:11 +0100
## Comment 12985
Date: 2010-01-24 21:21:19 +0100
From: @sjoerdmullender
Using a database created with the HEAD version of 2009-12-02, but running with a server checked out from HEAD on 2010-01-24, the second consecutive dump (running msqldump) causes a segfault at
at /home/sjoerd/src/MonetDB/devel/MonetDB/src/gdk/gdk_bbp.mx:1830
1830 assert(BBP_cache(i)->batSharecnt >= 0);
The reason for the segfault is
(gdb) p BBP[i]
$1 = {b = {0x0, 0x0}, nme = {0x615288 "tmp_141", 0x6152a8 "tmpr_141"}, bak = {
0x0, 0x0}, next = {0, 0}, cache = 0x6150b8, path = 0x6152d8 "01/141",
refs = 0, lrefs = 4, lastused = 32996, status = 32}
(This is a new report based on a comment in 2935207 which was for a different bug.)
## Comment 12986
Date: 2010-01-24 21:23:58 +0100
From: @sjoerdmullender
It seems a BAT is decref'ed when it already has a refcount 0.
The crash does not occur when loading the database in the same version as the version in which it is dumped.
## Comment 12987
Date: 2010-01-24 23:06:11 +0100
From: @sjoerdmullender
Niels' checkin to gdk_bbp.mx fixed this.
No test since this involves using two different versions of the software.
## Comment 12988
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2938842 at http://sourceforge.net/support/tracker.php?aid=2938842
| second dump causes crash | https://api.github.com/repos/MonetDB/MonetDB/issues/2309/comments | 0 | 2020-11-30T10:36:41Z | 2024-06-27T11:43:40Z | https://github.com/MonetDB/MonetDB/issues/2309 | 753,360,498 | 2,309 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-23 07:04:29 +0100
From: zeuner <<zeuner>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2010-01-30 02:54:20 +0100
## Comment 12983
Date: 2010-01-23 19:04:29 +0100
From: zeuner <<zeuner>>
The --host argument currently fails to accept a value. A patch is attached.
## Comment 12984
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2938069 at http://sourceforge.net/support/tracker.php?aid=2938069
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.
| cannot specify server host in stethoscope | https://api.github.com/repos/MonetDB/MonetDB/issues/2308/comments | 0 | 2020-11-30T10:36:38Z | 2024-06-27T11:43:39Z | https://github.com/MonetDB/MonetDB/issues/2308 | 753,360,455 | 2,308 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-23 06:53:47 +0100
From: zeuner <<zeuner>>
To: @njnes
Version: -- development
Last updated: 2010-01-30 10:52:34 +0100
## Comment 12977
Date: 2010-01-23 18:53:47 +0100
From: zeuner <<zeuner>>
The attached SQL statements lead to wrong output on MonetDB-SQL Feb2010. The final SELECT statement should result in the string 'modified' in the column "value", but it doesn't. Most likely it is a memory-related bug as most of the time, I get an empty string there, but during isolation of a reasonably small test case, I also got arbitrary binary data, and on occasion a string length overflow assertion breaking inside str.mx.
The test system runs CentOS 5.4 on x86_64, having MonetDB compiled with 64-bit OIDs. The compiler was "gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-46)".
## Comment 12978
Date: 2010-01-24 05:33:35 +0100
From: zeuner <<zeuner>>
I encountered a similar data corruption on other queries. Interestingly, the corrupted column was also initialized from a max() aggregate. I also had max() aggregates over integer columns in the same query, but these were processed correctly, so it seems to apply only to string columns.
## Comment 12979
Date: 2010-01-24 08:29:49 +0100
From: @mlkersten
to be sure, you are using a check out of the candidate code for the Feb2010 release of what date?
There are major changes in that area for which any indication of an error is relevant information.
## Comment 12980
Date: 2010-01-24 10:16:56 +0100
From: zeuner <<zeuner>>
I first became aware of the issue on a 2010-01-22 checkout. After tracking down how to trigger it, I tried again using a 2010-01-23 checkout, which made no difference.
## Comment 12981
Date: 2010-01-24 16:41:04 +0100
From: @njnes
fixed in the candidate feb2010 branch. Sometimes the bats with strings were incorrectly initialized.
Also added the test to src/test/BugTracker-2010
## Comment 12982
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2938065 at http://sourceforge.net/support/tracker.php?aid=2938065
| corrupted values after multiple INSERT/DELETEs | https://api.github.com/repos/MonetDB/MonetDB/issues/2307/comments | 0 | 2020-11-30T10:36:35Z | 2024-06-27T11:43:39Z | https://github.com/MonetDB/MonetDB/issues/2307 | 753,360,416 | 2,307 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-22 11:02:37 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2010-01-30 10:53:30 +0100
## Comment 12975
Date: 2010-01-22 11:02:37 +0100
From: @mlkersten
create temporary table x(
tag timestamp default now(),
id serial,
payload integer
);
causes a segfault
## Comment 12976
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2937063 at http://sourceforge.net/support/tracker.php?aid=2937063
| SQL: segfault on serial | https://api.github.com/repos/MonetDB/MonetDB/issues/2306/comments | 0 | 2020-11-30T10:36:32Z | 2024-06-28T07:25:38Z | https://github.com/MonetDB/MonetDB/issues/2306 | 753,360,382 | 2,306 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-21 10:43:33 +0100
From: zeuner <<zeuner>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2010-02-03 02:00:41 +0100
## Comment 12972
Date: 2010-01-21 22:43:33 +0100
From: zeuner <<zeuner>>
While for most variable-sized BATs the constraint H->heap.size == U->capacity << H->shift holds, it does not for those created by VIEWcreate_ (src/gdk/gdk_align.mx). As GDKupgradevarheap uses heap.size to decide what area to copy, and capacity to decide how much space to allocate, BATs created this way can cause writes to unallocated space when reaching this function.
The attached patch eliminates this source of memory-related crashes by consistently using heap.size for both allocation and copying.
## Comment 12973
Date: 2010-02-03 14:00:41 +0100
From: @sjoerdmullender
The essence of the patch was applied, and it seems to work well.
No test needed.
## Comment 12974
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2936616 at http://sourceforge.net/support/tracker.php?aid=2936616
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.
| GDKupgradevarheap: copied area and allocated space mismatch | https://api.github.com/repos/MonetDB/MonetDB/issues/2305/comments | 0 | 2020-11-30T10:36:28Z | 2024-06-27T11:43:36Z | https://github.com/MonetDB/MonetDB/issues/2305 | 753,360,346 | 2,305 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-19 09:26:28 +0100
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2010-01-24 06:06:08 +0100
## Comment 12963
Date: 2010-01-19 21:26:28 +0100
From: @skinkie
msqldump on an old database (old string format) results in a crashing server; the server responds:
../../../../src/modules/atoms/str.mx:1647: strLength: Assertion `l <2147483647' failed.
## Comment 12964
Date: 2010-01-21 10:16:02 +0100
From: @sjoerdmullender
The ususal question:
WHAT DID YOU DO?
Version of server in which the database was created?
Version of server with which you dumped?
Version of client doing the dumping?
How can you reproduce the problem?
Any private patches to the software?
## Comment 12965
Date: 2010-01-21 14:17:46 +0100
From: @skinkie
1) I executed msqldump (first sentence of the initial comment);
2) CVS head of begin december
3) I can't dump because there is an error (CVS head of 19 January)
4) Client (CVS head of 19 January)
5) Execute msqldump
6) None.
## Comment 12966
Date: 2010-01-21 17:23:27 +0100
From: @skinkie
Interesting it breaks on the *second* run of msqldump the first one was running with a problem. I broke it off and tried again.
[Switching to Thread 0x7fffe487c710 (LWP 28581)]
0x00007ffff6ac5b88 in decref (i=97, logical=1, releaseShare=0)
at ../../../src/gdk/gdk_bbp.mx:1830
1830 ../../../src/gdk/gdk_bbp.mx: No such file or directory.
in ../../../src/gdk/gdk_bbp.mx
(gdb) bt
0 0x00007ffff6ac5b88 in decref (i=97, logical=1, releaseShare=0)
at ../../../src/gdk/gdk_bbp.mx:1830
1 0x00007ffff6ac651d in BBPdecref (i=97, logical=1)
at ../../../src/gdk/gdk_bbp.mx:1897
2 0x00007fffe4f92492 in temp_destroy (b=97)
at ../../../../src/storage/bat/bat_utils.mx:134
3 0x00007fffe4f8f9f8 in destroy_delta (b=0x1348a28)
at ../../../../src/storage/bat/bat_storage.mx:962
4 0x00007fffe4f8faa3 in destroy_bat (tr=0x0, b=0x1348a28)
at ../../../../src/storage/bat/bat_storage.mx:976
5 0x00007fffe4f8fae8 in destroy_col (tr=0x0, c=0x1348998)
at ../../../../src/storage/bat/bat_storage.mx:984
6 0x00007fffe4f841f4 in reset_column (tr=0x1336d98, fc=0x1348998,
pfc=0x1087e38) at ../../../src/storage/store.mx:2750
7 0x00007fffe4f83d15 in reset_changeset (tr=0x1336d98, fs=0x1348848,
pfs=0x1087cb8, b=0x13487f8, rf=0x7fffe4f8417d <reset_column>,
fd=0x7fffe4f80f1d <column_dup>) at ../../../src/storage/store.mx:2673
8 0x00007fffe4f8443e in reset_table (tr=0x1336d98, ft=0x13487f8,
pft=0x1087c68) at ../../../src/storage/store.mx:2796
9 0x00007fffe4f83d15 in reset_changeset (tr=0x1336d98, fs=0x1336e38,
pfs=0x1085a48, b=0x1336e18, rf=0x7fffe4f84325 <reset_table>,
fd=0x7fffe4f81326 <table_dup>) at ../../../src/storage/store.mx:2673
10 0x00007fffe4f84688 in reset_schema (tr=0x1336d98, fs=0x1336e18,
---Type <return> to continue, or q <return> to quit---
pfs=0x1085a28) at ../../../src/storage/store.mx:2825
11 0x00007fffe4f83d15 in reset_changeset (tr=0x1336d98, fs=0x1336dc0,
pfs=0x10859d0, b=0x10859a8, rf=0x7fffe4f84528 <reset_schema>,
fd=0x7fffe4f81ab7 <schema_dup>) at ../../../src/storage/store.mx:2673
12 0x00007fffe4f8480d in reset_trans (tr=0x1336d98, ptr=0x10859a8)
at ../../../src/storage/store.mx:2853
13 0x00007fffe4f8a9b3 in sql_trans_begin (s=0x1336d48)
at ../../../src/storage/store.mx:4577
14 0x00007fffe4f34b82 in mvc_trans (m=0x13347f8)
at ../../../src/server/sql_mvc.mx:379
15 0x00007fffe4eed9f5 in monet5_user_get_def_schema (m=0x13347f8, user=0)
at ../../../../src/backends/monet5/sql_user.mx:463
16 0x00007fffe4eef0d6 in SQLinitClient (c=0x605a90)
at ../../../../src/backends/monet5/sql_scenario.mx:431
17 0x00007ffff7b099df in runPhase (c=0x605a90, phase=5)
at ../../../src/mal/mal_scenario.mx:602
18 0x00007ffff7b09aa2 in runScenarioBody (c=0x605a90)
at ../../../src/mal/mal_scenario.mx:634
19 0x00007ffff7b09d92 in runScenario (c=0x605a90)
at ../../../src/mal/mal_scenario.mx:679
20 0x00007ffff7abe7fc in MSserveClient (dummy=0x605a90)
at ../../../src/mal/mal_session.mx:474
21 0x00007ffff5797894 in start_thread (arg=<value optimized out>)
---Type <return> to continue, or q <return> to quit---
at pthread_create.c:297
22 0x00007ffff48c4f9d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
23 0x0000000000000000 in ?? ()
## Comment 12967
Date: 2010-01-21 17:29:14 +0100
From: @skinkie
Now the backup ran (produced output) but also ended in:
(gdb) bt
0 0x00007ffff6ac5b88 in decref (i=97, logical=1, releaseShare=0) at ../../../src/gdk/gdk_bbp.mx:1830
1 0x00007ffff6ac651d in BBPdecref (i=97, logical=1) at ../../../src/gdk/gdk_bbp.mx:1897
2 0x00007fffe4f92492 in temp_destroy (b=97) at ../../../../src/storage/bat/bat_utils.mx:134
3 0x00007fffe4f8f9f8 in destroy_delta (b=0x1348a28) at ../../../../src/storage/bat/bat_storage.mx:962
4 0x00007fffe4f8faa3 in destroy_bat (tr=0x0, b=0x1348a28) at ../../../../src/storage/bat/bat_storage.mx:976
5 0x00007fffe4f8fae8 in destroy_col (tr=0x0, c=0x1348998) at ../../../../src/storage/bat/bat_storage.mx:984
6 0x00007fffe4f841f4 in reset_column (tr=0x1336d98, fc=0x1348998, pfc=0x1087e38) at ../../../src/storage/store.mx:2750
7 0x00007fffe4f83d15 in reset_changeset (tr=0x1336d98, fs=0x1348848, pfs=0x1087cb8, b=0x13487f8, rf=0x7fffe4f8417d <reset_column>, fd=0x7fffe4f80f1d <column_dup>)
at ../../../src/storage/store.mx:2673
8 0x00007fffe4f8443e in reset_table (tr=0x1336d98, ft=0x13487f8, pft=0x1087c68) at ../../../src/storage/store.mx:2796
9 0x00007fffe4f83d15 in reset_changeset (tr=0x1336d98, fs=0x1336e38, pfs=0x1085a48, b=0x1336e18, rf=0x7fffe4f84325 <reset_table>, fd=0x7fffe4f81326 <table_dup>)
at ../../../src/storage/store.mx:2673
10 0x00007fffe4f84688 in reset_schema (tr=0x1336d98, fs=0x1336e18, pfs=0x1085a28) at ../../../src/storage/store.mx:2825
11 0x00007fffe4f83d15 in reset_changeset (tr=0x1336d98, fs=0x1336dc0, pfs=0x10859d0, b=0x10859a8, rf=0x7fffe4f84528 <reset_schema>, fd=0x7fffe4f81ab7 <schema_dup>)
at ../../../src/storage/store.mx:2673
12 0x00007fffe4f8480d in reset_trans (tr=0x1336d98, ptr=0x10859a8) at ../../../src/storage/store.mx:2853
13 0x00007fffe4f8a9b3 in sql_trans_begin (s=0x1336d48) at ../../../src/storage/store.mx:4577
14 0x00007fffe4f34b82 in mvc_trans (m=0x13347f8) at ../../../src/server/sql_mvc.mx:379
15 0x00007fffe4eed9f5 in monet5_user_get_def_schema (m=0x13347f8, user=1) at ../../../../src/backends/monet5/sql_user.mx:463
16 0x00007fffe4eef0d6 in SQLinitClient (c=0x605a90) at ../../../../src/backends/monet5/sql_scenario.mx:431
17 0x00007ffff7b099df in runPhase (c=0x605a90, phase=5) at ../../../src/mal/mal_scenario.mx:602
18 0x00007ffff7b09aa2 in runScenarioBody (c=0x605a90) at ../../../src/mal/mal_scenario.mx:634
19 0x00007ffff7b09d92 in runScenario (c=0x605a90) at ../../../src/mal/mal_scenario.mx:679
20 0x00007ffff7abe7fc in MSserveClient (dummy=0x605a90) at ../../../src/mal/mal_session.mx:474
21 0x00007ffff5797894 in start_thread (arg=<value optimized out>) at pthread_create.c:297
22 0x00007ffff48c4f9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
23 0x0000000000000000 in ?? ()
## Comment 12968
Date: 2010-01-21 17:37:54 +0100
From: @skinkie
And to make it even more interesting; this is what msqldump exports:
230830920000 "Overjordaans B.V." "Noordzijde 67 A" "2977XB" "Goudriaan" "Hoofdvestiging\015" 0
This is what I get from the current database in raw mode (seems to be an extra \r maybe it was in the source data):
[ 1082163, 230830920000, "Overjordaans B.V.", "Noordzijde 67 A", "2977XB", "Goudriaan", "Hoofdvestiging\015", 23083092, 0, 17, 15, 0 ]
And this is what I see if I import it again:
SQLException:sql:value 'Hoofdvestiging\015' from line 2414663 field 6 not inserted, expecting type str
SQLException:importTable:failed to import table
## Comment 12969
Date: 2010-01-21 17:50:44 +0100
From: @skinkie
So a second import run after removing the \015 stuff.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe487c710 (LWP 25358)]
0x00007ffff6c48d93 in GDKfree_ (blk=0x30500000000) at ../../../src/gdk/gdk_utils.mx:1121
1121 size = GDK_MEM_BLKSIZE(s);
(gdb) bt
0 0x00007ffff6c48d93 in GDKfree_ (blk=0x30500000000) at ../../../src/gdk/gdk_utils.mx:1121
1 0x00007ffff6c48f24 in GDKfree (blk=0x30500000000) at ../../../src/gdk/gdk_utils.mx:1167
2 0x00007fffe4f0a933 in stmt_destroy (s=0x1531098) at ../../../src/server/sql_statement.mx:671
3 0x00007fffe4f38812 in stack_pop_until (sql=0x1504458, top=9) at ../../../src/server/sql_mvc.mx:1540
4 0x00007fffe4f35b53 in mvc_reset (m=0x1504458, rs=0x1500390, ws=0x1ba77a0, debug=0, globalvars=9) at ../../../src/server/sql_mvc.mx:672
5 0x00007fffe4eef0b3 in SQLinitClient (c=0x605a90) at ../../../../src/backends/monet5/sql_scenario.mx:427
6 0x00007ffff7b099df in runPhase (c=0x605a90, phase=5) at ../../../src/mal/mal_scenario.mx:602
7 0x00007ffff7b09aa2 in runScenarioBody (c=0x605a90) at ../../../src/mal/mal_scenario.mx:634
8 0x00007ffff7b09d92 in runScenario (c=0x605a90) at ../../../src/mal/mal_scenario.mx:679
9 0x00007ffff7abe7fc in MSserveClient (dummy=0x605a90) at ../../../src/mal/mal_session.mx:474
10 0x00007ffff5797894 in start_thread (arg=<value optimized out>) at pthread_create.c:297
11 0x00007ffff48c4f9d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
12 0x0000000000000000 in ?? ()
## Comment 12970
Date: 2010-01-24 18:06:08 +0100
From: @sjoerdmullender
The originally reported bug is fixed by my patch to gdk_atoms.mx.
All other problems, if they still occur, are different bugs and should be reported separately.
No test, since this involves multiple versions of the software, and we don't have an infrastructure to test that.
## Comment 12971
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2935207 at http://sourceforge.net/support/tracker.php?aid=2935207
| msqldump, export/import crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/2304/comments | 0 | 2020-11-30T10:36:24Z | 2024-06-27T11:43:35Z | https://github.com/MonetDB/MonetDB/issues/2304 | 753,360,284 | 2,304 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-18 06:15:24 +0100
From: @swingbit
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2010-02-03 10:44:14 +0100
## Comment 12961
Date: 2010-01-18 18:15:24 +0100
From: @swingbit
When using a whitelist for pftijah indexing, as in <TijahOptions whitelist="tag1 tag2 tag3"/>,
it seems that the order in which the tags are written does matter.
So, <TijahOptions whitelist="tag3 tag1 tag2"/> would produce a different index.
I couldn't figure out exactly what conditions cause the problem.
However, I have the impression it wouldn't happen when those tag names don't appear nested into each other.
The test in attachment uses 2 simple xml files (actually html).
When using only one (either) of them, I don't see the bug.
When using both, one of the expected tag names in the dictionary disappears
(that is "span", which is in the subtree of one of the tags in whitelist)
## Comment 12962
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2934409 at http://sourceforge.net/support/tracker.php?aid=2934409
| PFTIJAH: indexing whitelist gives inconsistent results | https://api.github.com/repos/MonetDB/MonetDB/issues/2303/comments | 0 | 2020-11-30T10:36:21Z | 2024-06-27T11:43:35Z | https://github.com/MonetDB/MonetDB/issues/2303 | 753,360,243 | 2,303 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-16 07:59:53 +0100
From: Guillaume Yziquel <<yziquel>>
To: @sjoerdmullender
Version: -- development
Last updated: 2010-01-17 11:38:40 +0100
## Comment 12958
Date: 2010-01-16 19:59:53 +0100
From: Guillaume Yziquel <<yziquel>>
diff --git a/src/python/setup.py b/src/python/setup.py
index ff3f664..11c9b5b 100644
--- a/src/python/setup.py
+++ b/src/python/setup.py
@@ -21,7 +21,7 @@ setup(name='monetdb.sql',
version='1.0',
description='Native MonetDB driver',
author='Gijs Molenaar',
- author_email='gijs.molenaar@cw.nl',
+ author_email='gijs.molenaar@cwi.nl',
url='http://www.monetdb.nl',
packages=['monetdb', 'monetdb.sql'],
)
## Comment 12959
Date: 2010-01-17 11:38:39 +0100
From: @sjoerdmullender
Thansk. Fixed in CVS.
## Comment 12960
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2933480 at http://sourceforge.net/support/tracker.php?aid=2933480
| email typo in python lib. | https://api.github.com/repos/MonetDB/MonetDB/issues/2302/comments | 0 | 2020-11-30T10:36:18Z | 2024-06-27T11:43:34Z | https://github.com/MonetDB/MonetDB/issues/2302 | 753,360,198 | 2,302 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-13 05:57:17 +0100
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2010-01-21 01:52:29 +0100
## Comment 12954
Date: 2010-01-13 17:57:17 +0100
From: @swingbit
Found by chance while looking into a problem with pftijah term dictionary, the HEAD seems to compute wrong histograms on string bats.
Nov2009 branch seems correct.
In attachment, the files needed to run a test. It indexes a small xml file and then inspects the terrm dictionary.
Just source the runme.bash file (it just moves the xml file in /tmp and runs Mserver with the test mil script)
I don't think this is related to pathfinder at all, but this was the easiest way to create a reproducible test.
I suspect the bug is in gdk, as it may be related to the recent changes that store hash values in string heaps.
## Comment 12955
Date: 2010-01-14 12:33:59 +0100
From: @sjoerdmullender
Good catch.
There was a break missing which caused that we went through the bat twice to increment counts. I.e. all values were double the correct value.
Fixed in CVS.
## Comment 12956
Date: 2010-01-21 13:52:28 +0100
From: @sjoerdmullender
Test added: MonetDB4/tests/BugTracker bad_histgram.SF-2931465.
## Comment 12957
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2931465 at http://sourceforge.net/support/tracker.php?aid=2931465
| wrong histogram() | https://api.github.com/repos/MonetDB/MonetDB/issues/2301/comments | 0 | 2020-11-30T10:36:14Z | 2024-06-27T11:43:33Z | https://github.com/MonetDB/MonetDB/issues/2301 | 753,360,167 | 2,301 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-13 03:46:35 +0100
From: @grobian
To: Merovingian devs <<bugs-merovingian>>
Version: -- development
Last updated: 2010-05-04 13:03:40 +0200
## Comment 12952
Date: 2010-01-13 15:46:35 +0100
From: @grobian
Merovingian will read the control channel password from .merovingian_pass including the trailing newline. This causes unexpected permission denied errors since the client needs to include the trailing newline in the password too. Merovingian should ignore trailing newlines when reading the password, since it is fairly common to have one.
## Comment 12953
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2931392 at http://sourceforge.net/support/tracker.php?aid=2931392
## Comment 13986
Date: 2010-05-04 13:03:40 +0200
From: @grobian
Fixed in Feb2010 release.
| Merovingian: control channel passwords include trailing \n | https://api.github.com/repos/MonetDB/MonetDB/issues/2300/comments | 0 | 2020-11-30T10:36:11Z | 2024-06-27T11:43:32Z | https://github.com/MonetDB/MonetDB/issues/2300 | 753,360,138 | 2,300 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-11 05:01:37 +0100
From: @swingbit
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2010-02-03 10:46:39 +0100
## Comment 12947
Date: 2010-01-11 17:01:37 +0100
From: @swingbit
I create the pftijah index with a whitelist, as in:
<TijahOptions stemmer="porter-english" whitelist="invention-title abstract description claim"/>
The whitelist works well. The tag dictionary contains only the tags I wanted + all the tags included.
mil>bat("tj_DFLT_FT_INDEX_tagdict").print();
---------------------------------
h t name
void str type
---------------------------------
[ 0@0, "_DOCUMENT_ROOT" ]
[ 1@0, "invention-title" ]
[ 2@0, "abstract" ]
[ 3@0, "p" ]
[ 4@0, "description" ]
[ 5@0, "ul" ]
[ 6@0, "li" ]
[ 7@0, "sup" ]
[ 8@0, "sl" ]
[ 9@0, "heading" ]
[ 10@0, "u" ]
[ 11@0, "tables" ]
[ 12@0, "table" ]
[ 13@0, "tgroup" ]
[ 14@0, "tbody" ]
[ 15@0, "row" ]
[ 16@0, "entry" ]
[ 17@0, "sub" ]
[ 18@0, "img" ]
[ 19@0, "b" ]
[ 20@0, "claim" ]
[ 21@0, "claim-text" ]
However, the "tj_DFLT_FT_INDEX_param" bat contains only the FIRST tag specified in my whitelist:
mil>bat("tj_DFLT_FT_INDEX_param").print();;
-------------------------------------------------
h t name
str str type
-------------------------------------------------
[ "curFragment", "0" ]
[ "preExpansion", "4" ]
[ "_version", "1.1" ]
[ "stemmer", "porter-english" ]
[ "tokenizer", "flex" ]
[ "name", "DFLT_FT_INDEX" ]
[ "fragmentSize", "1073741823" ]
[ "delay_finalize", "0" ]
[ "whitelist", "invention-title" ]
[ "lastStopWord", "430" ]
[ "_last_tijahPre", "7662" ]
[ "status", "finalized" ]
[ "collectionSize", "7055" ]
[ "_last_finalizedPre", "7661" ]
## Comment 12948
Date: 2010-02-01 15:54:53 +0100
From: Jan Flokstra <<jflokstra>>
Strange bug! When I do in the HEAD:
tijah:create-ft-index(("S1","S2","S3"),<TijahOptions ft-index="TRY" stemmer="por
ter-english" whitelist="invention-title panel tag1 tag2 tag3"/>)
And then I print the bat you printed I get a good result.
MonetDB>bat("tj_TRY_param").print();
-----------------------------------------------------------------
h t name
str str type
-----------------------------------------------------------------
[ "stemmer", "porter-english" ]
[ "fragmentSize", "1073741823" ]
[ "curFragment", "0" ]
[ "preExpansion", "4" ]
[ "lastStopWord", "0" ]
[ "_version", "1.1" ]
[ "name", "TRY" ]
[ "_last_tijahPre", "1" ]
[ "tokenizer", "flex" ]
[ "delay_finalize", "0" ]
[ "whitelist", "invention-title panel tag1 tag2 tag3" ]
[ "collectionSize", nil ]
[ "status", "finalized" ]
[ "_last_finalizedPre", "0" ]
MonetDB>
I wil try to reproduce the error another way but I'm a litle bit stymied because I do not change the whitelist parameter value during creation.
## Comment 12949
Date: 2010-02-01 16:10:59 +0100
From: Jan Flokstra <<jflokstra>>
I now reproduced the error. It only occurs when documents are indexed. It does not occurwhen no documents are indexed. It think an inserted string in a [str,str] bat is modified in the "C" program AFTER the string is inserted in the BAT. I will try to fix it by modifying a copy of the whitelist value.
## Comment 12950
Date: 2010-02-01 16:26:26 +0100
From: Jan Flokstra <<jflokstra>>
I fixed it by making a copy of the value before tokenizing it with strtok(). This works for me.
## Comment 12951
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2929885 at http://sourceforge.net/support/tracker.php?aid=2929885
| PFTIJAH: whitelist in "_param" bat incomplete | https://api.github.com/repos/MonetDB/MonetDB/issues/2299/comments | 0 | 2020-11-30T10:36:08Z | 2024-06-27T11:43:31Z | https://github.com/MonetDB/MonetDB/issues/2299 | 753,360,102 | 2,299 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-07 06:38:04 +0100
From: Layirina Alphonse Ninamou <<nlalphonse>>
To: @yzchang
Version: -- development
CC: @drstmane
Last updated: 2011-05-03 10:45:54 +0200
## Comment 12944
Date: 2010-01-07 06:38:04 +0100
From: Layirina Alphonse Ninamou <<nlalphonse>>
Bonjour !
je viens d'installer monetdb sous UBUNTU 9.10 . quand j'essaie de me connecter sur l'Administrative GUI après avoir lancé le serveur, il ne se passe rien. Je vous prie de bien vouloir me dire que faire pour commencer.
Merci d'avance .
## Comment 12945
Date: 2010-01-07 13:38:18 +0100
From: @yzchang
Hello Layirina,
Thanks for using MonetDB/XQuery and XRPC. Unfortunately, I can't read French. Would you please reformulate your question/problem in English? Thank you very much.
Regards,
Jennie
## Comment 12946
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2927359 at http://sourceforge.net/support/tracker.php?aid=2927359
## Comment 15782
Date: 2011-05-03 10:45:54 +0200
From: @drstmane
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.
| Can't connect to the Administrative GUI | https://api.github.com/repos/MonetDB/MonetDB/issues/2298/comments | 0 | 2020-11-30T10:36:04Z | 2024-06-28T07:25:37Z | https://github.com/MonetDB/MonetDB/issues/2298 | 753,360,073 | 2,298 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-06 10:21:39 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2010-01-11 10:55:37 +0100
## Comment 12941
Date: 2010-01-06 22:21:39 +0100
From: @skinkie
>include sql;
MonetDB/SQL module v2.35.0 loaded
[New Thread 0x7fffe4f37710 (LWP 24664)]
>sql.start();
>select not(invalidtable.bla) from tables;
Program received signal SIGSEGV, Segmentation fault.
0x00007fffe540aa4f in exp_subtype (e=0x0) at ../../../src/server/rel_exp.mx:446
446 switch(e->type) {
(gdb) bt
0 0x00007fffe540aa4f in exp_subtype (e=0x0) at ../../../src/server/rel_exp.mx:446
1 0x00007fffe53fca28 in rel_unop_ (sql=0x11b0138, e=0x0, s=0x118ae08, fname=0x7fffe547414e "not", table_func=0)
at ../../../src/server/rel_select.mx:2927
2 0x00007fffe53fa66b in rel_logical_value_exp (sql=0x11b0138, rel=0x7fffffffd188, sc=0x11b2368, f=3) at ../../../src/server/rel_select.mx:2395
3 0x00007fffe5400d7f in rel_value_exp2 (sql=0x11b0138, rel=0x7fffffffd188, se=0x11b2368, f=3, ek=..., is_last=0x7fffffffd084)
at ../../../src/server/rel_select.mx:4053
4 0x00007fffe5400e0a in rel_value_exp (sql=0x11b0138, rel=0x7fffffffd188, se=0x11b2368, f=3, ek=...) at ../../../src/server/rel_select.mx:4068
5 0x00007fffe5400ed5 in column_exp (sql=0x11b0138, rel=0x7fffffffd188, column_e=0x11b2408, f=3) at ../../../src/server/rel_select.mx:4081
6 0x00007fffe5400fef in rel_column_exp (sql=0x11b0138, rel=0x7fffffffd188, column_e=0x11b2408, f=3) at ../../../src/server/rel_select.mx:4109
7 0x00007fffe5402242 in rel_select_exp (sql=0x11b0138, rel=0x11fa4d8, outer=0x0, sn=0x11b26c8, ek=...) at ../../../src/server/rel_select.mx:4413
8 0x00007fffe5402deb in rel_query (sql=0x11b0138, rel=0x0, sq=0x11b26c8, toplevel=1, ek=...) at ../../../src/server/rel_select.mx:4604
9 0x00007fffe540426a in rel_subquery (sql=0x11b0138, rel=0x0, sq=0x11b26c8, ek=...) at ../../../src/server/rel_select.mx:4947
10 0x00007fffe5404be1 in rel_selects (sql=0x11b0138, s=0x11b26c8) at ../../../src/server/rel_select.mx:5111
11 0x00007fffe53f30d9 in rel_semantic (sql=0x11b0138, s=0x11b26c8) at ../../../src/server/rel_semantic.mx:320
12 0x00007fffe5361748 in sql_symbol2stmt (c=0x11b0138, sym=0x11b26c8) at ../../../../src/backends/monet5/sql.mx:1263
13 0x00007fffe53a16f2 in SQLparser (c=0x604d20) at ../../../../src/backends/monet5/sql_scenario.mx:1153
14 0x00007ffff7b0a58f in runPhase (c=0x604d20, phase=1) at ../../../src/mal/mal_scenario.mx:602
15 0x00007ffff7b0a6e6 in runScenarioBody (c=0x604d20) at ../../../src/mal/mal_scenario.mx:645
16 0x00007ffff7b0a942 in runScenario (c=0x604d20) at ../../../src/mal/mal_scenario.mx:679
17 0x00007ffff7ac080c in MSserveClient (dummy=0x604d20) at ../../../src/mal/mal_session.mx:474
18 0x00000000004033b1 in main (argc=3, av=0x7fffffffdd08) at ../../../src/tools/mserver5.mx:640
## Comment 12942
Date: 2010-01-11 22:55:33 +0100
From: @njnes
fixed by properly handling the error. Added test to BugTracker-2009
## Comment 12943
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2927174 at http://sourceforge.net/support/tracker.php?aid=2927174
| SQL: not(invalidtable.bla) segfaults | https://api.github.com/repos/MonetDB/MonetDB/issues/2297/comments | 0 | 2020-11-30T10:36:00Z | 2024-06-27T11:43:29Z | https://github.com/MonetDB/MonetDB/issues/2297 | 753,360,032 | 2,297 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-05 09:20:36 +0100
From: Makoto YUI <<yuin405>>
To: @njnes
Version: -- development
CC: @drstmane
Last updated: 2010-10-18 18:50:16 +0200
## Comment 12938
Date: 2010-01-05 21:20:36 +0100
From: Makoto YUI <<yuin405>>
The following query causes "SELECT: subquery result missing" error and server crashes on Nov2009-SP1/Linux X86-64.
select
s_name,
sum(score) as totalscore,
rank() over (order by sum(score) desc) -- cannot use alias 'totalscore' here
from score_table
group by s_name
-- preparation
create table score_table (
s_name varchar(20),
subject varchar(10),
score int
);
insert into score_table values('foo','english',70);
insert into score_table values('foo','history',50);
insert into score_table values('foo','math',60);
insert into score_table values('bar','english',45);
insert into score_table values('bar','history',75);
Slightly related discussion (though the issue is aggregation in group-by) is found in
http://markmail.org/thread/33hxthbvr7csb66o
-- Note then that the following expression works properly.
select
s_name,
sum(score),
from score_table
group by s_name
order by sum(score) desc
## Comment 12939
Date: 2010-04-16 17:08:23 +0200
From: @sjoerdmullender
Added a test in sql: src/test/BugTracker-2010 rank-over-crash.SF-2926454.
## Comment 12940
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2926454 at http://sourceforge.net/support/tracker.php?aid=2926454
## Comment 15058
Date: 2010-10-18 18:50:16 +0200
From: @drstmane
Appears to work since Jun2010-SP1 (or at least Jun2010-SP2);
cf.,
http://dev.monetdb.org/hg/MonetDB/rev/48c4879cc71d
resp.
http://dev.monetdb.org/hg/MonetDB/rev/72c034ea5f47
| Error on "rank() over (order by sum(.." | https://api.github.com/repos/MonetDB/MonetDB/issues/2296/comments | 0 | 2020-11-30T10:35:56Z | 2024-06-27T11:43:28Z | https://github.com/MonetDB/MonetDB/issues/2296 | 753,359,985 | 2,296 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-04 06:44:51 +0100
From: Mark Bucciarelli <<mkbucc>>
To: Gijs Molenaar <<gijs>>
Version: -- development
Last updated: 2010-01-05 04:44:46 +0100
## Comment 12933
Date: 2010-01-04 18:44:51 +0100
From: Mark Bucciarelli <<mkbucc>>
Before this patch,
$time python test5.py
takes 7 seconds of real time.
After the patch, it takes 0.35s of real time.
I copied the socket options from MonetDB/src/common/stream.c.
## Comment 12934
Date: 2010-01-05 16:29:27 +0100
From: @gijzelaerr
Tested patch, can confirm speed improvement. Modified for Python 3 support also. Change is commited to Nov2009 branch. Ticked can be closed (can't do myself).
## Comment 12935
Date: 2010-01-05 16:44:46 +0100
From: @sjoerdmullender
Closing.
Gijs, now you should be able to do that yourself. You could have asked...
## Comment 12936
Date: 2010-01-05 16:45:52 +0100
From: @gijzelaerr
Sorry mister perfect
## Comment 12937
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2925750 at http://sourceforge.net/support/tracker.php?aid=2925750
| setsockopt in Python client greatly improves performace | https://api.github.com/repos/MonetDB/MonetDB/issues/2295/comments | 0 | 2020-11-30T10:35:53Z | 2024-06-27T11:43:26Z | https://github.com/MonetDB/MonetDB/issues/2295 | 753,359,950 | 2,295 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-04 04:37:30 +0100
From: Mark Bucciarelli <<mkbucc>>
To: @njnes
Version: -- development
Last updated: 2010-01-04 11:32:54 +0100
## Comment 12922
Date: 2010-01-04 16:37:30 +0100
From: Mark Bucciarelli <<mkbucc>>
This is the Nov. 09 branch, built from CVS.
The mclient -D option stops dead when it hits a field with a UTF-8 character.
In addition, the return value to the shell is zero, indicating no error.
See attached test files that create this scenario on my machine.
Note that I can run
$ cat test6.sql
just fine, so it's not something related to the locale setting for my
terminal.
(Furthermore, I believe if piping to stdout to a file, it shouldn't even
matter what the locale setting for the terminal is.)
This is a really bad one--if you are using dump for backups mclient
gives no indication that there was an error.
## Comment 12923
Date: 2010-01-04 16:39:45 +0100
From: Mark Bucciarelli <<mkbucc>>
If you run inside mclient interactive shell, it also fails:
sql>select * from city;
+------+------+------+------+------------------------+------------------------+------+------+------+
| id | name | regi | int1 | lat | long | int2 | int3 | int4 |
: : : on : : : : : : :
+======+======+======+======+========================+========================+======+======+======+
| 198 | Gjak | Euro | 0 | 20.430799484252901 | 42.380298614502003 | 0 | 0 | null |
: :1 tuple
write error
sql>\D
START TRANSACTION;
SET SCHEMA "test";
CREATE TABLE "test"."city" (
"id" int,
"name" varchar(100),
"region" varchar(100),
"int1" int,
"lat" double,
"long" double,
"int2" int,
"int3" int,
"int4" int
);
COPY 1 RECORDS INTO "test"."city" FROM stdin USING DELIMITERS '\t','\n','"';
198 "Gjakovsql>
## Comment 12924
Date: 2010-01-04 18:20:11 +0100
From: Mark Bucciarelli <<mkbucc>>
Sorry, this was against an old (two weeks?) checkout of CVS head.
When I ran the test files against 2009_Nov, the test passed. I'll leave it open
in case it really is an issue for HEAD.
## Comment 12925
Date: 2010-01-04 19:58:04 +0100
From: @sjoerdmullender
What is your locale? Give the command
locale
in a shell and post the result.
mclient uses your locale to determine how to translate the UTF-8 characters it gets from the server to whatever your terminal window uses. If your locale is e.g. C, then there is no way to translate the "e with diaeresis" in the table, so mclient complains about that (the write error you reported). I admit, the error message could be improved, but there is nothing else mclient can do.
If your locale settings are indeed C (or Posix), then you can tell mclient which encoding to use to overrule this by using the -E (--encoding) option. You can, for example, use
mclient -Eutf-8 -lsql ...
if you know your terminal window can handle UTF-8.
## Comment 12926
Date: 2010-01-04 20:08:58 +0100
From: Mark Bucciarelli <<mkbucc>>
I can cat the test6.sql just fine so my terminal handles UTF8.
And the attached test script pipes the output to a file--shouldn't that always work irrespective of my terminal's local is? I'll pretty sure you can do something like
$ cat file_with_utf8.txt > another_file.txt
even with a locale of C.
To answer your question:
$locale
LANG=en_US.UTF-8
LC_CTYPE="C"
LC_NUMERIC="C"
LC_TIME="C"
LC_COLLATE="C"
LC_MONETARY="C"
LC_MESSAGES="C"
LC_PAPER="C"
LC_NAME="C"
LC_ADDRESS="C"
LC_TELEPHONE="C"
LC_MEASUREMENT="C"
LC_IDENTIFICATION="C"
LC_ALL=C
$
## Comment 12927
Date: 2010-01-04 20:14:13 +0100
From: Mark Bucciarelli <<mkbucc>>
Also, I think mclient in this case must exit with
a value of 1 not 0. (I don't care so much about
the text of the error message).
Otherwise, there is no way to tell that the
dump failed, which is really bad for a
production system with automated backups.
I'll try and work up a patch.
## Comment 12928
Date: 2010-01-04 20:52:54 +0100
From: @sjoerdmullender
I agree that the error code of mclient is not right. I just fixed that in the code.
mclient uses the LC_CTYPE value to determine the encoding of the terminal. In your case that is "C", so that means that you (implicitly) told mclient that it can only write ASCII data. Converting the e with diaeresis to ASCII is not possible, so mclient bails.
If your terminal can do more than ASCII, you should set your locale to reflect that and specify LC_CTYPE=en_US.UTF-8 in your environment.
Mclient is doing the right thing in this respect (apart from the error code which I fixed).
## Comment 12929
Date: 2010-01-04 21:03:19 +0100
From: Mark Bucciarelli <<mkbucc>>
Thank you for changing mclient error value!
However, I disagree that mclient is behaving properly.
For example, what if I want to pipe the mclient output to a program that understands UTF-8?
My terminal locale is completely irrelevant in this case.
## Comment 12930
Date: 2010-01-04 22:37:20 +0100
From: @sjoerdmullender
Mclient cannot read your mind. You tell it what encoding to use. The default is to use the locale (LC_CTYPE which defaults to LANG but in your case is different), and if that isn't the correct encoding you can tell it what the correct encoding is with the -E option. There is no bug here.
## Comment 12931
Date: 2010-01-04 23:32:54 +0100
From: Mark Bucciarelli <<mkbucc>>
Thanks for the tip on the -E argument. I can
use that to get what I want.
It still doesn't make sense to me that using
the same terminal I can insert data that will
then abort the dump.
But I get the sense it ain't gonna change. :)
Closing the ticket as fixed.
Thanks for your help!
## Comment 12932
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2925674 at http://sourceforge.net/support/tracker.php?aid=2925674
| mclient dump fails on UTF-8 char and gives no error | https://api.github.com/repos/MonetDB/MonetDB/issues/2294/comments | 0 | 2020-11-30T10:35:49Z | 2024-06-27T11:43:25Z | https://github.com/MonetDB/MonetDB/issues/2294 | 753,359,876 | 2,294 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-03 08:46:36 +0100
From: Guillaume Yziquel <<yziquel>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2010-01-04 12:33:46 +0100
## Comment 12916
Date: 2010-01-03 20:46:36 +0100
From: Guillaume Yziquel <<yziquel>>
Hello.
Operating System: Debian testing + sid. amd64.
Compiler: gcc (Debian 4.3.4-6) 4.3.4
Parser: lex 2.5.35, flex 2.5.35, bison (GNU Bison) 2.4.1
autoconf: autoconf (GNU Autoconf) 2.61
automake: automake (GNU automake) 1.11
libtool: ltmain.sh (GNU libtool) 2.2.6b
To reproduce the bug, follow instructions on http://www.mail-archive.com/caml-list@yquem.inria.fr/msg05449.html
You will need OCaml to compile the binding. Then do make gdb-byte, and just run. -> segfault.
click on snapshot for the binding: http://yziquel.homelinux.org/gitweb/?p=ocaml-monetdb5.git;a=tree
I've been running into dynamic loading issues while dynamically loading libmonetdb5.so from OCaml bytecode. In a nutshell, I get a segfault because the uninitialised data section (BSS) is somehow not initialised to 0. However, implementation of mal_box.c relies on the fact that the BSS is set to 0. Therefore, the function findBox contains a line "box[i] != NULL && idcmp(..., box[i]->name)". box[i] != NULL evaluates to true since BSS is not initialised to 0, but box[i]->name segfaults, quite logically.
I've googled quite a bit, and while BSS seems very very often to be initialised to 0, it doesn't seem to be always the case. So could it be possible to have the code of MonetDB not assume by default that BSS is initialised to 0?
## Comment 12917
Date: 2010-01-03 22:30:15 +0100
From: @mlkersten
A patch to the mal_box file has been checked in to deal with this issue as it should, i.e. only access memory when it is initialized. Code to be checked for other cases of this pattern
## Comment 12918
Date: 2010-01-04 00:08:08 +0100
From: Guillaume Yziquel <<yziquel>>
In fact, it's a symbol collision that got resolved the wrong way round. There's a box function in /lib/libncurses.so.5.
int box(WINDOW *win, chtype verch, chtype horch);
The border, wborder and box routines draw a box around the edges of a window.
And this library is loaded very early on by ocamlrun, the ocaml bytecode interpreter.
## Comment 12919
Date: 2010-01-04 00:33:46 +0100
From: @mlkersten
Name clash resolved and checked the code in M5 for other global variables.
This should fix the bud. Fix applied to Feb2010 release only. No test needed.
## Comment 12920
Date: 2010-01-04 09:56:14 +0100
From: @sjoerdmullender
I must say, I found the theory that the BSS wasn't cleared very strange. The C language specification guarantees that all static and global (i.e. anything not on the stack) variables are initialized to a zero bit pattern (if not initialized explicitly).
## Comment 12921
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2925338 at http://sourceforge.net/support/tracker.php?aid=2925338
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.
| BSS not necessarily initialised to 0. | https://api.github.com/repos/MonetDB/MonetDB/issues/2293/comments | 0 | 2020-11-30T10:35:46Z | 2024-06-28T07:25:37Z | https://github.com/MonetDB/MonetDB/issues/2293 | 753,359,841 | 2,293 |
[
"MonetDB",
"MonetDB"
] | Date: 2010-01-02 09:01:29 +0100
From: Mark Kubacki <<hurrikane>>
To: @sjoerdmullender
Version: -- development
Last updated: 2010-01-21 10:24:07 +0100
## Comment 12913
Date: 2010-01-02 21:01:29 +0100
From: Mark Kubacki <<hurrikane>>
Given MonetDB-1.34.2 (Nov2009-SP2) and installed CURL (tested with net-misc/curl-7.19.6) following command leads to errors:
Reproduce:
cd MonetDB-1.34.2
./configure --with-curl
make
Expected:
compiles fine
Got:
[... configuring OK]
[... 2 lines by make, then:]
stream.c: In function ‘open_urlstream’:
stream.c:1214: error: ‘FALSE’ undeclared (first use in this function)
stream.c:1214: error: (Each undeclared identifier is reported only once
stream.c:1214: error: for each function it appears in.)
stream.c:1214: warning: type defaults to ‘int’ in declaration of ‘type name’
[...]
stream.c:1215: error: ‘TRUE’ undeclared (first use in this function)
stream.c:1215: warning: type defaults to ‘int’ in declaration of ‘type name’
[...]
make: *** [all] Error 2
Additional information:
OS: GNU/Linux-2.6.30
Dist: Gentoo 10.0
Portage 2.1.6.13 (default/linux/amd64/10.0, gcc-4.4.1, glibc-2.9_p20081201-r2, 2.6.30-gentoo-r5 x86_64)
app-shells/bash: 4.0_p28
dev-lang/python: 2.6.2-r1
dev-util/ccache: 2.4-r7
dev-util/cmake: 2.6.4-r3
sys-apps/baselayout: 1.12.11.1
sys-apps/sandbox: 1.6-r2
sys-devel/autoconf: 2.63-r1
sys-devel/automake: 1.9.6-r2, 1.10.2
sys-devel/binutils: 2.20
sys-devel/gcc-config: 1.4.1
sys-devel/libtool: 2.2.6a
virtual/os-headers: 2.6.30-r1
## Comment 12914
Date: 2010-01-21 10:24:07 +0100
From: @sjoerdmullender
Fixed in CVS. The symbols TRUE and FALSE were used but not defined. They have been replaced by the actual values (1 and 0).
No test needed: compilation issue.
## Comment 12915
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2924999 at http://sourceforge.net/support/tracker.php?aid=2924999
| compiling fails with --with-curl | https://api.github.com/repos/MonetDB/MonetDB/issues/2292/comments | 0 | 2020-11-30T10:35:41Z | 2024-06-27T11:43:23Z | https://github.com/MonetDB/MonetDB/issues/2292 | 753,359,797 | 2,292 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-26 06:01:31 +0100
From: @skinkie
To: SQL devs <<bugs-sql>>
Version: 11.13.9 (Oct2012-SP3)
CC: @njnes, sellam
Last updated: 2013-02-19 13:17:59 +0100
## Comment 12911
Date: 2009-12-26 06:01:31 +0100
From: @skinkie
sql>select (4.4054292 - 4.40572025343667)^2;
+------------------------+
| sql_sub_single_value |
+========================+
| 8.4712102997417702e-08 |
+------------------------+
1 tuple
sql>select (52.0903881 - 52.091375762174)^2;
+------------------------+
| sql_sub_single_value |
+========================+
| 9.7547656995040638e-07 |
+------------------------+
1 tuple
sql>select (4.4054292 - 4.40572025343667)^2 + (52.0903881 - 52.091375762174)^2;
+------------------------+
| sql_sub_single_value |
+========================+
| null |
+------------------------+
1 tuple
I would expect 1.0602e-06. As the outcome of the following would be:
sql>select cast((4.4054292 - 4.40572025343667)^2 as double) + cast((52.0903881 - 52.091375762174)^2 as double);
+------------------------+
| sql_sub_single_value |
+========================+
| 1.0601886729478242e-06 |
+------------------------+
1 tuple
sql>select cast((4.4054292 - 4.40572025343667)^2 + (52.0903881 - 52.091375762174)^2 as double);
+------------------------+
| sql_sub_single_value |
+========================+
| null |
+------------------------+
1 tuple
## Comment 12912
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2921310 at http://sourceforge.net/support/tracker.php?aid=2921310
## Comment 15425
Date: 2011-01-25 15:13:56 +0100
From: @grobian
Changeset [ff0617c4732c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=ff0617c4732c) 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=ff0617c4732c](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=ff0617c4732c)
Changeset description:
Add test for bug #2291
## Comment 15426
Date: 2011-01-25 15:17:30 +0100
From: @grobian
Feels like the automagic casting isn't working correctly here. With larger values it indeed works fine without the explicit double casts.
## Comment 15685
Date: 2011-03-28 17:36:32 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16037
Date: 2011-07-29 11:00:04 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16193
Date: 2011-09-07 17:15:24 +0200
From: @sjoerdmullender
The problem is completely different from what is being suggested.
The problem has to do with operator priorities.
sql>\fcsv
sql>select (4.4054292 - 4.40572025343667)^2 + (52.0903881 - 52.091375762174)^2;
sql>select ((4.4054292 - 4.40572025343667)^2) + ((52.0903881 - 52.091375762174)^2);
1.0601886729478242e-06
The reason for the result can be found in sql_parser.y. There we have:
...
%left <operation> '='
%left <operation> '&' '|' '^' LEFT_SHIFT RIGHT_SHIFT
%left <operation> '+' '-'
%left <operation> '*'
%left <operation> '/' '%'
...
In other words, the ^ operator has equal priority to & and |, which is lower than + and - (and certainly lower than * and /).
## Comment 16274
Date: 2011-09-16 15:10:38 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17227
Date: 2012-05-07 13:55:14 +0200
From: @njnes
are there changes needed or should we close this bug as is.
## Comment 17228
Date: 2012-05-07 14:08:22 +0200
From: @sjoerdmullender
We should do something about the priority of the operators, or we should do something about the semantics of the operators.
It makes no sense to have a "power" operator with the same priority as bitwise AND and OR. The power operator should have a priority higher than multiplication.
Also, I find it strange to have C-like bitwise AND and OR operators, but have the ^ operator mean something totally different than what it does in C. Although we can't do this in the current release cycle, I'd like to use a different operator for power.
## Comment 17679
Date: 2012-08-24 14:55:57 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18204
Date: 2012-11-28 13:45:44 +0100
From: sellam
Changeset [6e6c5d533911](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=6e6c5d533911) made by Thibault Sellam <sellam@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6e6c5d533911](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=6e6c5d533911)
Changeset description:
Added test for bug #2291
## Comment 18216
Date: 2012-11-28 18:57:44 +0100
From: @njnes
lets fix this in default.
No longer use ^ for power but for binary xor.
Add ~ (binary not).
Solve the operator precedence
## Comment 18372
Date: 2013-01-22 09:29:13 +0100
From: @sjoerdmullender
Oct2012-SP3 has been released.
## Comment 18438
Date: 2013-01-29 09:17:51 +0100
From: @sjoerdmullender
Correct version / fix information.
The problem was resolved in the default branch before the Feb2013 branch was branched off.
## Comment 18512
Date: 2013-02-19 13:17:59 +0100
From: @sjoerdmullender
Feb2013 has been released.
| small doubles end up as NULL after arithmetic | https://api.github.com/repos/MonetDB/MonetDB/issues/2291/comments | 0 | 2020-11-30T10:35:37Z | 2024-06-27T11:43:22Z | https://github.com/MonetDB/MonetDB/issues/2291 | 753,359,765 | 2,291 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-23 08:35:13 +0100
From: Mark Bucciarelli <<mkbucc>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2010-01-21 11:11:46 +0100
## Comment 12903
Date: 2009-12-23 20:35:13 +0100
From: Mark Bucciarelli <<mkbucc>>
I could only find one instance in the code base
of this function.
The attached patch fixes the issue.
Note that I crash if the call fails; seems like
a decent route as something is seriously
wrong in this case.
The other option was to log a warning
and set cpus = 1.
The other code paths don't check the
return value of the sysctl call.
## Comment 12904
Date: 2009-12-23 23:11:28 +0100
From: Mark Bucciarelli <<mkbucc>>
whoops, bad patch. don't apply, i'll post new one.
## Comment 12905
Date: 2009-12-23 23:49:39 +0100
From: Mark Bucciarelli <<mkbucc>>
This patch is better; it passes the right
arguments to sysctl() call.
## Comment 12906
Date: 2009-12-24 09:01:29 +0100
From: @grobian
Patch looks ok to me, I will apply it.
## Comment 12907
Date: 2009-12-24 13:20:39 +0100
From: @grobian
Heh, I made some local modifications to your patch, but my computer died (the heating might be on again...) So can't commit your patch now.
## Comment 12908
Date: 2010-01-21 10:26:16 +0100
From: @sjoerdmullender
Fabian, any news on this?
## Comment 12909
Date: 2010-01-21 11:11:46 +0100
From: @grobian
oops, committed now in stable, thanks!
## Comment 12910
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2920265 at http://sourceforge.net/support/tracker.php?aid=2920265
| OpenBSD doesn't support sysctlbyname | https://api.github.com/repos/MonetDB/MonetDB/issues/2290/comments | 0 | 2020-11-30T10:35:35Z | 2024-06-27T11:43:21Z | https://github.com/MonetDB/MonetDB/issues/2290 | 753,359,728 | 2,290 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-23 01:55:27 +0100
From: Mark Bucciarelli <<mkbucc>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-12-23 02:20:53 +0100
## Comment 12900
Date: 2009-12-23 13:55:27 +0100
From: Mark Bucciarelli <<mkbucc>>
When inserting 187,317 records with mclient
(in auto-commit mode), I hit seven foreign
key violations.
In each case, the error message output by
mclient was off by thousands of records.
For example, the output below suggested that
the error occured on db_viewer id 30891. In
actual fact, it happened on record 33,742.
These offsets ranged from 2,851 to 4,427
records.
MAPI = django@localhost:50000
QUERY =
INSERT INTO "db_viewer" VALUES(30888,1759,1880,'2009-11-03 14:57:45','2009-11-13 21:20:18+00:00',0,2,NULL,NULL,0,NULL,NULL,0,NULL,NULL);
INSERT INTO "db_viewer" VALUES(30889,19630,6970,'2009-11-03 14:57:58+00:00','2009-11-03 14:57:58+00:00',0,1,NULL,NULL,0,NULL,NULL,0,NULL,NULL);
INSERT INTO "db_viewer" VALUES(30890,41946,6971,'2009-11-03 14:58:14','2009-11-22 16:20:01+00:00',0,3,NULL,NULL,0,NULL,NULL,0,NULL,NULL);
INSERT INTO "db_viewer" VALUES(30891,4447,321,'2009-11-03 14:58:22','2009-11-18 15:22:56+00:
ERROR = !SQLException:assert:INSERT INTO: FOREIGN KEY constraint 'db_viewer.db_viewer_lastUserAgent_id_fkey' violated
gcc 4.3.3
32bit i386
ubuntu 9.04
## Comment 12901
Date: 2009-12-23 14:20:53 +0100
From: @sjoerdmullender
mclient sends quite large buffers to the server, and the server then find an error with one of the queries in that buffer and tells mclient that it found an error. There is a shortcoming in the protocol that the server doesn't tell mclient which query in the buffer caused the error, so mclient doesn't know that. All mclient can do is tell you that somewhere in the buffer it sent there was an error (and what the error message that it did get from the server was). Since the buffers are fairly large, mclient only remembers part of the buffer it sent, so it tells you basically, somewhere in the buffer that start with this string there was an error.
So, I'm afraid this is expected behavior.
It is a feature request to fix this behavior (https://sourceforge.net/tracker/?func=detail&aid=2871572&group_id=56967&atid=482471).
The main reason we haven't fixed this yet is that the server would have to remember the query it is executing. This would be a fair bit of work, and at least until now, we've always had other priorities.
## Comment 12902
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2920022 at http://sourceforge.net/support/tracker.php?aid=2920022
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.
| Foreign key violation error message gives wrong record | https://api.github.com/repos/MonetDB/MonetDB/issues/2289/comments | 0 | 2020-11-30T10:35:32Z | 2024-06-28T07:25:37Z | https://github.com/MonetDB/MonetDB/issues/2289 | 753,359,681 | 2,289 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-21 09:54:26 +0100
From: Mark Bucciarelli <<mkbucc>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-12-21 10:04:42 +0100
## Comment 12897
Date: 2009-12-21 21:54:26 +0100
From: Mark Bucciarelli <<mkbucc>>
Trying to build -r Nov2009 make fails with the following message:
gcc -DHAVE_CONFIG_H -I. -g -O2 -MT disclaimer.o -MD -MP -MF .deps/disclaimer.Tpo -c -o disclaimer.o disclaimer.c
mv -f .deps/disclaimer.Tpo .deps/disclaimer.Po
gcc -g -O2 -o Mx Mx.o Def.o Form.o Tok.o Code.o Display.o Print.o Io.o Sys.o disclaimer.o
make[3]: Leaving directory `/home/mark/src/monetdb/buildtools/Mx'
make[2]: Leaving directory `/home/mark/src/monetdb/buildtools/Mx'
Making all in mel
make[2]: Entering directory `/home/mark/src/monetdb/buildtools/mel'
make[2]: *** No rule to make target `all'. Stop.
make[2]: Leaving directory `/home/mark/src/monetdb/buildtools/mel'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/mark/src/monetdb/buildtools'
make: *** [all] Error 2
Steps:
$ cvs -z3 \
> -d:pserver:anonymous@monetdb.cvs.sourceforge.net:/cvsroot/monetdb \
> checkout \
> -r Nov2009 \
> -P buildtools
$cd buildtools
$ ./bootstrap
$ ./configure
$ make
Versions of autotools:
$ automake --version
automake (GNU automake) 1.10.2
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 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.
Written by Tom Tromey <tromey@redhat.com>
and Alexandre Duret-Lutz <adl@gnu.org>.
$ autoconf --version
autoconf (GNU Autoconf) 2.63
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
$ libtool --version
ltmain.sh (GNU libtool) 2.2.6
Written by Gordon Matzigkeit <gord@gnu.ai.mit.edu>, 1996
Copyright (C) 2008 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.
$
autogen.py is in /usr/local/bin
## Comment 12898
Date: 2009-12-21 22:04:42 +0100
From: Mark Bucciarelli <<mkbucc>>
Sorry, I was missing g++ and bison.
Closing as invalid.
## Comment 12899
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2918918 at http://sourceforge.net/support/tracker.php?aid=2918918
| Can't build Nov2009 CVS branch, make fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2288/comments | 0 | 2020-11-30T10:35:28Z | 2024-06-28T07:25:36Z | https://github.com/MonetDB/MonetDB/issues/2288 | 753,359,626 | 2,288 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-18 08:49:38 +0100
From: Mark Bucciarelli <<mkbucc>>
To: Gijs Molenaar <<gijs>>
Version: -- development
Last updated: 2010-01-12 05:32:02 +0100
## Comment 12889
Date: 2009-12-18 20:49:38 +0100
From: Mark Bucciarelli <<mkbucc>>
See attached test file, the test file output on
my system and a patch that fixes this issue.
In short, if you insert a field with the
value 'abc\ndef' you get back 'abc\\ndef'
## Comment 12890
Date: 2009-12-21 09:45:38 +0100
From: @drstmane
Gijs,
could you please have a look at this one?
Thanks!
Stefan
## Comment 12891
Date: 2009-12-21 13:41:45 +0100
From: @gijzelaerr
Looking in to it. Nice patch by the way. Will add the test to the api tests also.
## Comment 12892
Date: 2009-12-21 17:35:59 +0100
From: @gijzelaerr
Added a modified version of the fix to the Nov2009 CVS tree.
## Comment 12893
Date: 2009-12-22 11:12:07 +0100
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: gijzelaar@users.sourceforge.net ----
Please let us know if the new Nov2009 CVS version fixes your problem, then I can close this bug.
## Comment 12894
Date: 2009-12-22 21:15:19 +0100
From: Mark Bucciarelli <<mkbucc>>
Yes, latest code from Nov2009 branch works for me. Thanks!
## Comment 12895
Date: 2010-01-12 17:32:00 +0100
From: @sjoerdmullender
Fix will be in Nov2009-SP2 release.
## Comment 12896
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2917219 at http://sourceforge.net/support/tracker.php?aid=2917219
| Python client doesn't handle fields with newline characters | https://api.github.com/repos/MonetDB/MonetDB/issues/2287/comments | 0 | 2020-11-30T10:35:25Z | 2024-06-27T11:43:18Z | https://github.com/MonetDB/MonetDB/issues/2287 | 753,359,578 | 2,287 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-17 12:51:08 +0100
From: Mark Bucciarelli <<mkbucc>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-12-17 07:05:15 +0100
## Comment 12883
Date: 2009-12-17 00:51:08 +0100
From: Mark Bucciarelli <<mkbucc>>
Maybe by design?
I could use the -P option in the django driver I am building for MonetDB.
The only way I could find to start mclient without
interaction was to write the params to
DOTMONETDBFILE then set that environmental
variable. Doable, but awkward.
The man page mentions the -P argument, can it
get back into mclient optargs?
## Comment 12884
Date: 2009-12-17 10:32:03 +0100
From: @grobian
It looks like you're using the development sources where this option indeed was removed.
## Comment 12885
Date: 2009-12-17 14:21:31 +0100
From: Mark Bucciarelli <<mkbucc>>
Yes, I am using version from CVS. Sounds like this option was removed by design.
Django provides a wrapper around the backend database client shell, and it stores the backend username and password in a configuration file.
To wrap mclient in Python, do I now need to use the DOTMONETDBFILE dance I described above, or is there another option?
## Comment 12886
Date: 2009-12-17 15:33:11 +0100
From: @grobian
I don't understand why django doesn't just use the python connector for MonetDB instead of wasting performance and resources on an external program.
But yes, dropping it was intentional, and the only way around it is using the DOTMONETDBFILE.
## Comment 12887
Date: 2009-12-17 19:05:15 +0100
From: Mark Bucciarelli <<mkbucc>>
It's just a wrapper to provide an consistent interface to a db shell,
no matter what the backend. The actual driver uses the Python
API.
I'll just prompt for the password.
Thanks!
## Comment 12888
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2915905 at http://sourceforge.net/support/tracker.php?aid=2915905
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.
| mclient doesn't support --password | https://api.github.com/repos/MonetDB/MonetDB/issues/2286/comments | 0 | 2020-11-30T10:35:21Z | 2024-06-28T07:25:36Z | https://github.com/MonetDB/MonetDB/issues/2286 | 753,359,533 | 2,286 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-16 02:59:58 +0100
From: Andreas Streichardt <<m0p>>
To: Gabriele Modena <<gabriele_modena>>
Version: -- development
Last updated: 2010-06-14 15:57:05 +0200
## Comment 12877
Date: 2009-12-16 14:59:58 +0100
From: Andreas Streichardt <<m0p>>
1. I am on php 5.3.1. and the extension won't compile. This is documented here:
https://sourceforge.net/tracker/?func=detail&aid=2847738&group_id=56967&atid=482468
I hit the same bug. The bugfix is rather trivial (see attached diff)
2. The installation process is somehow completely different to the normal php extension installation process.
The normal process would be:
phpize
./configure
make
make install
Somehow this is different in monetdb and you need to execute some hard coded makefile.
There isn't much needed to fix this:
1. The config.m4 has to be modified (some old? path problems).
2. The config.h file php generates has to be included (so that COMPILE_DL_MONETDB is set)
php might even depend on some stuff which is not present in the hardcoded makefile so this seems a fragile process.
These issues have been fixed in the attached patch
## Comment 12878
Date: 2009-12-16 15:20:56 +0100
From: @drstmane
Andreas,
thanks for your detailed and constructive report!
Please note, though, that the SWIG-based "Cimpl" version of our MonetDB PHP interface is considered deprecated, since the have the new "native" PHP interface.
Once we're confident that the latter fully replaces the former, we will drop the former.
Hence, my question is, whether you are only reporting the compilation problems (and suggesting a fix), or also actively using the PHP interface. If the latter, could you please test & compare both interfaces (SWIG-based & native) and report whether the latter works (at least) as fine as the former (for you), or whether there are problems or missing features.
Thanks in advance!
Stefan
## Comment 12879
Date: 2009-12-16 16:04:11 +0100
From: Andreas Streichardt <<m0p>>
Oh, didn't see that.
I am not yet actively using monetdb. I am currently analyzing several analytical databases - one of which is monetdb. I have a small testsuite created in php and when i noticed that i couldn't compile the monetdb php extension i started searching for the reasons:
A few hard (sorry :S) comments about the native implmementation:
It looks as if this implementation has not been done by a PHP programmer. This is how you would have developed something in PHP maybe 5-10 years ago.
If you look at up-to-date frameworks like Zend Framework, Symfony and the like you will see that PHP coding has changed MUCH in the last years. It is very very close to Java and one would probably expect a Java-Like native implementation today.
The code uses global variables all over the place. In our environment for example global variables are strictly forbidden.
The constants are not even prefixed.
function &mapi_execute($conn=NULL, $query) {
Returning by reference is deprecated.
The first variable has a default value but the second is required? :S
if ($conn == NULL) {
return FALSE;
This will be true for more cases than you would think:
$conn=array();
$conn="";
$conn=0;
+ more
check using ===, isnull or the like
Numerous lines of code will throw notices due to not checking if for examle an array key is set.
foreach ($data as $row) {
/*
PHP5.2 complains when $row[0] is accessed with:
Notice: Uninitialized string offset: 0
In order to avoid the E_NOTICE error substr($row, 0, 1) is used
to access the first character of a string
*/
if (substr($row, 0, 1) == MSG_QUERY) {
PHP doesn't report bogus notices. The problem was probably something different. Probably an empty string. So this is simply a hack.
The code uses split() all over the place. split() is deprecated.
This code will of course work but most professional PHP coders wouldn't dare to use this interface. This is the good thing about a C extension. global variables are fairly common and not visible to the whining PHP programmer ;)
Furthermore i would have performance concerns. I didn't test it yet but i would expect it to be MUCH slower than the C implementation. This is probably the first database extension written purely in PHP (which is not really famous for its speed ;) ). On the low level side an implementation should probably be always be coded in C (at least that's what the others do for a good reason).
Desperately hoping the critic was helpful and not too harsh!
## Comment 12880
Date: 2009-12-16 16:19:48 +0100
From: @drstmane
Thank your for your honest comments!
I'm pretty sure, we can all take and handle such frank but constructive feedback. ;-)
We'll discuss the details internally.
Please keep us posted about your experiences with MonetDB --- then probably best via the mailing lists and/or new bug reports (if "necessary" ;-))
## Comment 12881
Date: 2009-12-16 16:22:42 +0100
From: @drstmane
Gabriele,
maybe you find some useful information in Andreas' comments?
Stefan
## Comment 12882
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2915566 at http://sourceforge.net/support/tracker.php?aid=2915566
## Comment 14105
Date: 2010-06-14 15:57:05 +0200
From: @grobian
We won't develop a C-based implementation of a PHP module any more. Any contributions in this field are welcome though.
| Provide C-implementation of PHP driver | https://api.github.com/repos/MonetDB/MonetDB/issues/2285/comments | 0 | 2020-11-30T10:35:18Z | 2024-06-28T13:43:49Z | https://github.com/MonetDB/MonetDB/issues/2285 | 753,359,482 | 2,285 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-15 05:30:02 +0100
From: Mark Bucciarelli <<mkbucc>>
To: @sjoerdmullender
Version: -- development
Last updated: 2010-03-05 01:28:13 +0100
## Comment 12867
Date: 2009-12-15 05:30:02 +0100
From: Mark Bucciarelli <<mkbucc>>
On OpenBSD you need -lcrypto with -lssl. It looks like
MonetDB5-server-5.16.0/aclocal.m4 is trying to check
for this, but the configure output looks wrong:
../MonetDB5-server-5.16.0/configure line 34000
if test "x$ac_cv_lib_crypto_ERR_get_error" = x""yes; then
OPENSSL_LIBS="$OPENSSL_LIBS -lcrypto"
fi
I think the right side of the test be
= "xyes"; then
When I compile the test program by hand with the -lssl and -lcrypto args it compiles just fine.
## Comment 12868
Date: 2009-12-15 05:41:54 +0100
From: Mark Bucciarelli <<mkbucc>>
Not sure about my original analysis. But when I changed lin 33868
of ../MonetDB5-server-5.16.0/configure from
LIBS="-lssl $LIBS"
to
LIBS="-lssl -lcrypto $LIBS"
Now configure can find openssl libs (it says the version I have
is too old, when it used to say openssl not found).
## Comment 12869
Date: 2009-12-15 14:28:25 +0100
From: @grobian
weird this is autoconf generated code, and it seems the -lssl check above is identical, but apparently did work for you.
## Comment 12870
Date: 2009-12-15 17:50:18 +0100
From: Mark Bucciarelli <<mkbucc>>
Just to be clear; I manually edited the configure file that was generated by autoconf.
I changed: -lssl to -lssl -lcrypto in two places and the configure script changed behavior.
Before the change, it said I didn't have OpenSSL installed. After the change, it said my
version is too old (which is the correct answer).
The original configure did run the ERR_get_error check, but I think the logic
in that section is somehow broken. I'm not a user of autotools, so I couldn't
sort out what the issue was.
Here's the relevant output from a configure run from before my manual edits:
...
checking for SSL_read in -lssl... no
checking for ERR_get_error in -lcrypto... yes
...
configure: error: MonetDB 5 requires OpenSSL (OpenSSL library not found)
$
## Comment 12871
Date: 2010-01-21 10:51:00 +0100
From: @sjoerdmullender
Could you try the attached diff to buildtools/conf/MonetDB.m4 to see if that works?
You will need to rebuild and install the buildtools and then try the MonetDB5 configure again.
## Comment 12872
Date: 2010-01-21 13:39:48 +0100
From: Mark Bucciarelli <<mkbucc>>
I won't be able to try until early Feb.
Will this apply against latest stable branch?
## Comment 12873
Date: 2010-01-21 17:20:42 +0100
From: @sjoerdmullender
It'll probably apply (I didn't try). But you can also easily do it by hand in case it doesn't. All I did was add an extra argument to the call to AC_CHECK_LIB(ssl, ...). The extra argument is [-lcrypto] (i.e. add a comma and the string [-lcrypto] including brackets to just before the closing parenthesis).
## Comment 12874
Date: 2010-03-05 00:30:11 +0100
From: Mark Bucciarelli <<mkbucc>>
Hi,
I manually applied your change to Feb2010.
...
checking for ERR_get_error in -lcrypto... yes
checking for OpenSSL >= 0x0090800f... yes
checking for dlopen in -ldl... no
...
Please apply to tree!
:)
## Comment 12875
Date: 2010-03-05 13:28:12 +0100
From: @sjoerdmullender
Patch applied.
No test needed.
## Comment 12876
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2914578 at http://sourceforge.net/support/tracker.php?aid=2914578
| Test for -lcrypto with -lssl not working | https://api.github.com/repos/MonetDB/MonetDB/issues/2284/comments | 0 | 2020-11-30T10:35:14Z | 2024-06-27T11:43:15Z | https://github.com/MonetDB/MonetDB/issues/2284 | 753,359,426 | 2,284 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-15 04:43:33 +0100
From: Mark Bucciarelli <<mkbucc>>
To: @sjoerdmullender
Version: -- development
Last updated: 2010-01-21 11:13:48 +0100
## Comment 12861
Date: 2009-12-15 04:43:33 +0100
From: Mark Bucciarelli <<mkbucc>>
monetdb-config requires bash, and not all *nix systems
provide this by default.
It seemed to run fine with a shebang of /bin/sh -- if you don't need bash,
please remove the dependency.
## Comment 12862
Date: 2009-12-15 09:09:25 +0100
From: @grobian
What is /bin/sh in your case? I think it should be possible to write the scripts for /bin/sh, but we just have to keep in mind that on other platforms (e.g. Solaris) /bin/sh is nowhere near posix shell.
## Comment 12863
Date: 2009-12-15 14:45:02 +0100
From: @grobian
I removed the dependency for MonetDB, MonetDB5, clients and sql
## Comment 12864
Date: 2009-12-15 17:42:44 +0100
From: Mark Bucciarelli <<mkbucc>>
/bin/sh is a public domain Bourne shell.
Reading notes section of OpenBSD manual page, looks like this one
may also have some isues when you need POSIX compliance.
Not sure what to say; I have very little experience with POSIX compliance
issues.
NOTES
sh is implemented as a run-time option of pdksh, with only those sh fea-
tures whose syntax or semantics are incompatible with a traditional
Bourne shell disabled. Since this leaves some sh extensions exposed,
caution should be used where backwards compatibility with traditional
Bourne or POSIX compliant shells is an issue.
## Comment 12865
Date: 2010-01-21 11:13:47 +0100
From: @sjoerdmullender
The *-config scripts are now complete bash-free.
The only bash scripts that we still have are scripts used by testing.
## Comment 12866
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2914563 at http://sourceforge.net/support/tracker.php?aid=2914563
| Remove dependence on bash | https://api.github.com/repos/MonetDB/MonetDB/issues/2283/comments | 0 | 2020-11-30T10:35:10Z | 2024-06-27T11:43:14Z | https://github.com/MonetDB/MonetDB/issues/2283 | 753,359,374 | 2,283 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-15 04:24:51 +0100
From: Mark Bucciarelli <<mkbucc>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-12-15 09:58:51 +0100
## Comment 12858
Date: 2009-12-15 04:24:51 +0100
From: Mark Bucciarelli <<mkbucc>>
dnl MonetDB code requires some POSIX and XOPEN extensions
*-*-solaris*)
dnl Basically, we introduced a small hell by requiring C99 for the
...
yes-*-*)
case "$host_os" in
cygwin*|freebsd*|irix*|darwin*)
;;
*)
AC_DEFINE(_POSIX_C_SOURCE, 200112L, [Compiler flag])
AC_DEFINE(_POSIX_SOURCE, 1, [Compiler flag])
AC_DEFINE(_XOPEN_SOURCE, 600, [Compiler flag])
;;
esac
...
The line:
cygwin*|freebsd*|irix*|darwin*)
should include |openbsd*
Thanks.
## Comment 12859
Date: 2009-12-15 09:58:51 +0100
From: @sjoerdmullender
Fixed in CVS.
## Comment 12860
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2914558 at http://sourceforge.net/support/tracker.php?aid=2914558
| Modify MonetDB.m4 to support OpenBSD | https://api.github.com/repos/MonetDB/MonetDB/issues/2282/comments | 0 | 2020-11-30T10:35:07Z | 2024-06-27T11:43:13Z | https://github.com/MonetDB/MonetDB/issues/2282 | 753,359,340 | 2,282 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-14 03:23:59 +0100
From: @grobian
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2011-01-25 15:07:27 +0100
## Comment 12854
Date: 2009-12-14 15:23:59 +0100
From: @grobian
using ulimit to cause memory shortage on my system (1.3G real memory, 1G virtual memory), the AVG_of_SQRT.SF-2757642.test (from src/test/BugTracker-2009) quickly segfaults like this:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 5 (LWP 5)]
0xfffffd7f4200f8cb in SQLload_file (cntxt=0x6061d8, as=0xfffffd7ffddfdde0,
b=0x1403e30, out=0x0, csep=0x123ca68 "|", rsep=0x123cb88 "\n",
quote=0 '\000', skip=-4220415, maxrow=100000000)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/modules/mal/tablet_sql.mx:501
501 task->fields[0][task->next] = s;
(gdb) bt
0 0xfffffd7f4200f8cb in SQLload_file (cntxt=0x6061d8, as=0xfffffd7ffddfdde0,
b=0x1403e30, out=0x0, csep=0x123ca68 "|", rsep=0x123cb88 "\n",
quote=0 '\000', skip=-4220415, maxrow=100000000)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/modules/mal/tablet_sql.mx:501
1 0xfffffd7e618737bf in mvc_import_table (cntxt=0x6061d8, m=0x1217428,
bs=0x1403e30, sname=0x71ab48 "sys", tname=0x71a868 "n8",
sep=0x123ca68 "|", rsep=0x123cb88 "\n", ssep=0x0, ns=0x123ca88 "null",
sz=100000000, offset=0)
at /export/scratch/mirror/fabian/monetdb/Nov2009/sql/src/backends/monet5/sql_result.mx:502
2 0xfffffd7e6182b0f3 in mvc_import_table_wrap (cntxt=0x6061d8, mb=0x1640c58,
stk=0xfffffd7ffddfed20, pci=0x1640fb8)
at /export/scratch/mirror/fabian/monetdb/Nov2009/sql/src/backends/monet5/sql.mx:2508
3 0xfffffd7f4c62b1f9 in runMALsequence (cntxt=0x6061d8, mb=0x1640c58,
startpc=1, stoppc=0, stk=0xfffffd7ffddfed20, env=0x121a128,
pcicaller=0x124b988)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_interpreter.mx:1851
4 0xfffffd7f4c621fb9 in runMAL (cntxt=0x6061d8, mb=0x1640c58, startpc=1,
mbcaller=0x121aa38, env=0x121a128, pcicaller=0x124b988)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_interprete---Type <return> to continue, or q <return> to quit---q
Quit
(gdb) l
496 }
497
498 if ((e != NULL && *e != 0) || ateof) {
499 /* found a complete record, or an incomplete one at the end of the file */
500 if ( --skip < 0 ) {
501 task->fields[0][task->next] = s;
502 *e = '\0';
503 if ( SQLload_file_line(task, as, s, csep,rsep) < 0) {
504 ifdef _DEBUG_TABLET_
505 stream_printf(GDKout,"line failed:\n");
(gdb) p task
$1 = (READERtask *) 0x124bf68
(gdb) p task->fields
$2 = (char ***) 0x123cac8
(gdb) p task->fields[0]
$3 = (char **) 0xfffffd7ff8800010
(gdb) p task->fields[0][task->next]
Cannot access memory at address 0xfffffd7ffa833000
(gdb) p task->next
$4 = 4220414
(gdb)
## Comment 12855
Date: 2009-12-15 11:44:27 +0100
From: @grobian
same happens on a limited environment under Linux:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fc509933950 (LWP 32240)]
0x00007fc50e973345 in SQLload_file (cntxt=0x605788, as=0x7fc50992d650,
b=0x1a33a40, out=0x0, csep=0x1adfb08 "|", rsep=0x19eeb28 "\n",
quote=0 '\0', skip=-10610687, maxrow=100000000)
at /ufs/fabian/scratch/monetdb/Nov2009/five/src/modules/mal/tablet_sql.mx:499
499 task->fields[0][task->next] = s;
(gdb) p task->next
$1 = 10610686
(gdb)
sql>copy 100000000 records into i8 from 'src/test/BugTracker-2009/parallel_bulk-load.SF-2771052.csv';
## Comment 12856
Date: 2009-12-16 08:34:46 +0100
From: @mlkersten
Correct. In a memory constraint environment the GDKrealloc of the task entry may fail.
After testing it can be closed.
## Comment 12857
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2914191 at http://sourceforge.net/support/tracker.php?aid=2914191
## Comment 15424
Date: 2011-01-25 15:07:27 +0100
From: @grobian
this was tested some time ago
| SQL: copy into crash (tablet_sql) | https://api.github.com/repos/MonetDB/MonetDB/issues/2281/comments | 0 | 2020-11-30T10:35:03Z | 2024-06-27T11:43:12Z | https://github.com/MonetDB/MonetDB/issues/2281 | 753,359,297 | 2,281 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-14 11:43:00 +0100
From: Layirina Alphonse Ninamou <<nlalphonse>>
To: @sjoerdmullender
Version: -- development
Last updated: 2010-04-16 05:15:18 +0200
## Comment 12850
Date: 2009-12-14 11:43:00 +0100
From: Layirina Alphonse Ninamou <<nlalphonse>>
En fait voici le message que je reçois quand j'essaie de démarrer "MonetDB XQUERY Client".
initiating connection on socket failed: No such file or directory
Appuyez sur une touche pour continuer...
## Comment 12851
Date: 2009-12-14 12:48:07 +0100
From: @sjoerdmullender
This means there is no server running.
## Comment 12852
Date: 2010-04-16 17:15:18 +0200
From: @sjoerdmullender
If my conclusion was correct, this is not a bug.
If my conclusion is not correct, please open another bug, and please write in English. Our French is not nearly as good as our English.
## Comment 12853
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2914096 at http://sourceforge.net/support/tracker.php?aid=2914096
| MonetDb/XQUERY : Impossible de demarrer le server | https://api.github.com/repos/MonetDB/MonetDB/issues/2280/comments | 0 | 2020-11-30T10:35:00Z | 2024-06-28T07:25:36Z | https://github.com/MonetDB/MonetDB/issues/2280 | 753,359,260 | 2,280 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-13 10:37:44 +0100
From: Layirina Alphonse Ninamou <<nlalphonse>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-12-14 12:31:15 +0100
## Comment 12846
Date: 2009-12-13 22:37:44 +0100
From: Layirina Alphonse Ninamou <<nlalphonse>>
Bonjour !
je viens d'installer MonetDb \Xquery (la dernière version disponible sur le site http://www.monetdb.nl/monetdb/Download ).
Et quand j'essaie de lancer le server, la console disparait toute de suite après l'apparition de quelques lignes et quand j'essaie de lancer "Monet DB client " je reçois sur la console le message ci-dessous. Pourriez-vous me dire que faire pour que ça fonctionne ? je vous remercie d'avance .
MALException:setScenario:Scenario not initialized 'xquery'
Appuyez sur une touche pour continuer...
## Comment 12847
Date: 2009-12-14 00:31:15 +0100
From: @peterboncz
Pardon, je ne parle pas francais..
You installed MonetDB5/SQL, and you cannot connect to a MonetDB5 server requesting an xquery session.
You must install MonetDB4/XQuery. If you install both MonetDB5/SQL and MonetDB4/XQuery, you must make them use different mapi_port (--set mapi_port=NUMBER), then connect with the extra switch -P NUMBER in mclient
jéspere ca suffit
## Comment 12848
Date: 2009-12-14 09:49:24 +0100
From: @sjoerdmullender
Probably you have an MonetDB5/SQL server running when you tried starting the MonetDB4/XQuery server. Those servers cannot both run at the same time (in the default Windows configuration). So, stop the SQL server, then start the XQuery server, then start the XQuery client.
## Comment 12849
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2913877 at http://sourceforge.net/support/tracker.php?aid=2913877
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.
| MonetDb/XQUERY : Impossible de demarrer le server | https://api.github.com/repos/MonetDB/MonetDB/issues/2279/comments | 0 | 2020-11-30T10:34:56Z | 2024-06-28T07:25:35Z | https://github.com/MonetDB/MonetDB/issues/2279 | 753,359,219 | 2,279 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-11 01:39:51 +0100
From: Martin Dürre <<mduerre>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-12-18 08:43:48 +0100
## Comment 12834
Date: 2009-12-11 13:39:51 +0100
From: Martin Dürre <<mduerre>>
Hello MonetDB-Team
After:
merovingian
monetdb create testx
monetdb start testx
monetdb status testx
/*
name state uptime health last crash
testx locked 60s 100%, 0s -
*/
mclient -l sql -d testx -u monetdb
// Password: monetdb
// Abort trap
merovingian log says:
2009-12-11 13:32:47 MSG merovingian[162]: proxying client localhost:49698 for database 'testx' to mapi:monetdb://127.0.0.1:50002/testx
2009-12-11 13:32:48 MSG merovingian[162]: client localhost:49698 has disconnected from proxy
Thanks,
Martin
## Comment 12835
Date: 2009-12-11 13:46:12 +0100
From: @grobian
hi Martin,
can you please look in ~/Library/Logs/CrashReporter/mclient.log (or something) to see if there's any more information that can reveal where your trap is caused by?
## Comment 12836
Date: 2009-12-11 13:58:47 +0100
From: Martin Dürre <<mduerre>>
Hi,
here is the corresponding crash-File:
Process: mclient [215]
Path: /usr/local/bin/mclient
Identifier: mclient
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: sh [159]
Date/Time: 2009-12-11 13:40:03.255 +0100
OS Version: Mac OS X 10.5.8 (9L31a)
Report Version: 6
Anonymous UUID: CF257F10-B422-47BC-B896-105DBA432D13
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 0
Thread 0 Crashed:
0 libSystem.B.dylib 0x9270fe42 __kill + 10
1 libSystem.B.dylib 0x9278223a raise + 26
2 libSystem.B.dylib 0x9278e622 __abort + 97
3 libSystem.B.dylib 0x9275a43e sys_cache_control + 0
4 libSystem.B.dylib 0x9273dca9 __strncat_chk + 43
5 libMapi.1.dylib 0x0001d5e5 __inline_strncat_chk + 40 (_string.h:135)
6 libMapi.1.dylib 0x0001b074 mapi_start_talking + 1676 (Mapi.mx:2453)
7 libMapi.1.dylib 0x0001d3b4 mapi_start_talking + 10700 (Mapi.mx:2818)
8 libMapi.1.dylib 0x0001d60c mapi_reconnect + 37 (Mapi.mx:2850)
9 libMapi.1.dylib 0x0001d666 mapi_connect + 82 (Mapi.mx:2864)
10 mclient 0x00008713 main + 4944 (MapiClient.mx:2166)
11 mclient 0x00001f8a start + 54
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x9275a3cf ecx: 0xbfffa6dc edx: 0x9270fe42
edi: 0x003008c8 esi: 0x00000000 ebp: 0xbfffa6f8 esp: 0xbfffa6dc
ss: 0x0000001f efl: 0x00000282 eip: 0x9270fe42 cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0xa0290101
Binary Images:
0x1000 - 0x10fff +mclient ??? (???) <f4dd788b30c62eec7dbbd1ad6ea3531e> /usr/local/bin/mclient
0x16000 - 0x28ffc +libMapi.1.dylib ??? (???) <aa9a87fbb7a1c9e101f1b03c434e3e26> /usr/local/lib/libMapi.1.dylib
0x31000 - 0x37fff +libstream.1.dylib ??? (???) <18e41f735a46e9aad7d422ca1fab082d> /usr/local/lib/libstream.1.dylib
0x3f000 - 0x40ffc +libmutils.1.dylib ??? (???) <61808294a332d0a37781a5d4e63fdf88> /usr/local/lib/libmutils.1.dylib
0x44000 - 0x7cfeb +libssl.0.9.8.dylib ??? (???) <463006fb472192b95d158901eb1eff7f> /opt/local/lib/libssl.0.9.8.dylib
0x90000 - 0xa0ffd +libz.1.dylib ??? (???) <a3bea29149481a5c9fd056566c80b4df> /opt/local/lib/libz.1.dylib
0x162000 - 0x265fe7 +libcrypto.0.9.8.dylib ??? (???) <f90fe0999ba5e8a9a4cc825a2071ef61> /opt/local/lib/libcrypto.0.9.8.dylib
0x8fe00000 - 0x8fe2db43 dyld 97.1 (???) <458eed38a009e5658a79579e7bc26603> /usr/lib/dyld
0x90a11000 - 0x90a15fff libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
0x926a1000 - 0x92808ff3 libSystem.B.dylib ??? (???) <ae47ca9b1686b065f8ac4d2de09cc432> /usr/lib/libSystem.B.dylib
0x94232000 - 0x94240ffd libz.1.dylib ??? (???) <a98b3b221a72b54faf73ded3dd7000e5> /usr/lib/libz.1.dylib
0x95122000 - 0x9512efff libbz2.1.0.dylib ??? (???) <887bb6f73d23088fe42946cd9f134876> /usr/lib/libbz2.1.0.dylib
0x958a7000 - 0x9599bff4 libiconv.2.dylib ??? (???) <96ff4c6f84c4a1623cb78287371cdd3f> /usr/lib/libiconv.2.dylib
0x96d28000 - 0x96d2ffe9 libgcc_s.1.dylib ??? (???) <e280ddf3f5fb3049e674edcb109f389a> /usr/lib/libgcc_s.1.dylib
0xffff0000 - 0xffff1780 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
Maybe it helps.
Thanks again,
Martin
## Comment 12837
Date: 2009-12-11 14:14:06 +0100
From: @grobian
Thanks, that helps to see where the problem occurs. I'm still in the dark why, though.
## Comment 12838
Date: 2009-12-11 14:38:41 +0100
From: @grobian
From your crash log I see you have a library mismatch, your mclient is indirectly linked against both /usr/lib/libz.dylib and /usr/local/lib/libz.dylib. I think this comes from early compilation attempts which did not include the proper linking as we discussed on a previous bug.
Can you please start from scratch compiling everything using the correct LDFLAGS and check what happens then? We are not able to reproduce this problem on our Mac(s) here.
## Comment 12839
Date: 2009-12-11 14:50:58 +0100
From: Martin Dürre <<mduerre>>
Okay, i'll give it another try later.
## Comment 12840
Date: 2009-12-15 15:19:30 +0100
From: Martin Dürre <<mduerre>>
Hello again,
I build all packages again, order as provided in the documentation.
With
../$package_name/configure LDFLAGS="-search_path_first -L/opt/local/var/macports/software/openssl/0.9.8l_0+darwin/opt/local/lib/"
The "Abort Trap"-Error maintains, crash file equals to the one already posted.
I got a warning while compiling:
ld warning: duplicate dylib /usr/lib/libz.1.dylib
I don't know (and wasn't able to google neither) how to remove one of the duplicates from the libpath.
Do I have to set DYLD_LIBRARY_PATH manually? That's something that's not really recommended.
Greetings,
Martin
## Comment 12841
Date: 2009-12-15 15:28:32 +0100
From: @grobian
I would have expected you do this instead:
$ export CPPFLAGS=
$ export CFLAGS="-I/opt/local/var/macports/software/openssl/0.9.8l_0+darwin/opt/local/include"
$ export CXXFLAGS=${CFLAGS}
$ export LDFLAGS="-L/opt/local/var/macports/software/openssl/0.9.8l_0+darwin/opt/local/lib"
$ ./configure --prefix=/some/place
$ make && make install
$ cd next-package
$ ./configure --prefix=/some/place
...
## Comment 12842
Date: 2009-12-15 15:30:06 +0100
From: @grobian
or instead of calling configure and make yourself, just call monetdb-install.sh after exporting those values
## Comment 12843
Date: 2009-12-17 23:06:58 +0100
From: Martin Dürre <<mduerre>>
Seemed to have worked. I first got some database inconsistency errors, but now everything seems to work fine.
Thank you very much.
I hope that I'll come up with some real bugs, that could help to improve your project ;)
## Comment 12844
Date: 2009-12-18 08:43:47 +0100
From: @grobian
ok, thanks for testing
## Comment 12845
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2912631 at http://sourceforge.net/support/tracker.php?aid=2912631
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.
| Connectiing with mclient fails: Abort trap | https://api.github.com/repos/MonetDB/MonetDB/issues/2278/comments | 0 | 2020-11-30T10:34:53Z | 2024-06-28T07:25:35Z | https://github.com/MonetDB/MonetDB/issues/2278 | 753,359,179 | 2,278 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-10 01:39:57 +0100
From: Ben Companjen <<bencompanjen>>
To: @njnes
Version: -- development
Last updated: 2009-12-10 01:42:40 +0100
## Comment 12831
Date: 2009-12-10 13:39:57 +0100
From: Ben Companjen <<bencompanjen>>
<offtopic>
It took me forever (many tries, hours) to realize that the Nov2009 release will not compile on my MacBook Pro running OS X 10.5.8. I may file another report on this
I managed to install Aug2009-SP2 with SQL and XQuery.
</offtopic>
Creating a database using 'monetdb create test' works fine. 'monetdb status' shows the database's status 'stopped'.
When I want it to start, using 'monetdb start test', it crashes after starting. Terminal shows:
$ monetdb start test
starting database 'test'... FAILED:
starting 'test' failed: database 'test' has crashed after starting, manual intervention needed, check merovingian's logfile for details
The log then shows:
2009-12-10 13:05:29 MSG merovingian[91012]: starting database 'test' due to control signal
2009-12-10 13:05:29 MSG merovingian[91012]: starting database 'test', up min/avg/max: 0s/0s/0s, crash average: 0.00 0.00 0.00 (0-0=0)
2009-12-10 13:05:29 MSG test[91301]: arguments: /Users/ben/MonetDB/bin/mserver5 --config=/Users/ben/MonetDB/etc/monetdb5.conf --dbname=test --dbinit=include sql; --set monet_daemon=yes --set mapi_open=false --set mapi_autosense=true --set mapi_port=50001 --set monet_vault_key=/Users/ben/MonetDB/var/MonetDB5/dbfarm/test/.vaultkey
2009-12-10 13:05:29 ERR test[91301]: dyld: lazy symbol binding failed: Symbol not found: _SHA512
2009-12-10 13:05:29 ERR test[91301]: Referenced from: /Users/ben/MonetDB/lib/libmonetdb5.5.dylib
2009-12-10 13:05:29 ERR test[91301]: Expected in: flat namespace
2009-12-10 13:05:29 ERR test[91301]:
2009-12-10 13:05:29 ERR test[91301]: dyld: Symbol not found: _SHA512
2009-12-10 13:05:29 ERR test[91301]: Referenced from: /Users/ben/MonetDB/lib/libmonetdb5.5.dylib
2009-12-10 13:05:29 ERR test[91301]: Expected in: flat namespace
2009-12-10 13:05:29 ERR test[91301]:
2009-12-10 13:05:29 MSG merovingian[91012]: database 'test' (91301) was killed by signal 5
2009-12-10 13:05:39 ERR merovingian[91012]: failed to fork mserver: database 'test' has crashed after starting, manual intervention needed, check merovingian's logfile for details
Any ideas on this?
## Comment 12832
Date: 2009-12-10 13:42:40 +0100
From: @grobian
yes, you failed to properly link the product.
Dupe of 2911937
## Comment 12833
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2911975 at http://sourceforge.net/support/tracker.php?aid=2911975
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| monetdb start db -> dyld: Symbol not found: _SHA512 | https://api.github.com/repos/MonetDB/MonetDB/issues/2277/comments | 0 | 2020-11-30T10:34:50Z | 2024-06-28T07:25:34Z | https://github.com/MonetDB/MonetDB/issues/2277 | 753,359,126 | 2,277 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-10 12:10:22 +0100
From: Martin Dürre <<mduerre>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-12-11 08:29:43 +0100
## Comment 12819
Date: 2009-12-10 12:10:22 +0100
From: Martin Dürre <<mduerre>>
System Version: Mac OS X 10.5.8 (9L31a)
Kernel Version: Darwin 9.8.0
Compiler with version i686-apple-darwin9-gcc-4.0.1;
Parser tools with version flex, bison.
And on Linux and Unix systems:
autoconf (GNU Autoconf) 2.61;
automake (GNU automake) 1.10;
Apple Computer, Inc. version cctools-698.1.
Hello MonetDBTeam,
Trying to install monetDb according to http://monetdb.cwi.nl/MonetDB/Documentation/Linux-Installation.htmlLinux-Installation.
Updated pcre and openssl.
Build doesn't obviously fail.
Running make check results in Error:
./RunMtest: line 77: exec: Mtest.py: not found
Running Mserver --dbinit 'module(sql_server);' results in Error:
!ERROR: moduleClient: module(sql_server) load error.
Running mserver5 --dbinit 'include sql; results in Error
dyld: lazy symbol binding failed: Symbol not found: _SHA512
Referenced from: /usr/local/lib/libmonetdb5.5.dylib
Expected in: flat namespace
dyld: Symbol not found: _SHA512
Referenced from: /usr/local/lib/libmonetdb5.5.dylib
Expected in: flat namespace
Seems to be related to http://sourceforge.net/support/tracker.php?aid=2887777.
Greetings,
Martin
## Comment 12820
Date: 2009-12-10 12:41:36 +0100
From: Martin Dürre <<mduerre>>
After getting and building cvs:testing, Mytest.py is found, make check in different directories is throwing errors.
Other errors still to be found.
## Comment 12821
Date: 2009-12-10 12:43:14 +0100
From: Martin Dürre <<mduerre>>
Having the same problems using the superball distribution.
## Comment 12822
Date: 2009-12-10 13:16:11 +0100
From: @grobian
your traps indicate a linking problem. What does otool -L /usr/local/lib/libmonetdb5.5.dylib result in?
## Comment 12823
Date: 2009-12-10 13:20:09 +0100
From: Martin Dürre <<mduerre>>
Here is my otool -L /usr/local/lib/libmonetdb5.5.dylib output:
/usr/local/lib/libmonetdb5.5.dylib:
/usr/local/lib/libmonetdb5.5.dylib (compatibility version 23.0.0, current version 23.0.0)
/usr/local/lib/libbat.1.dylib (compatibility version 37.0.0, current version 37.0.0)
/usr/local/lib/libmutils.1.dylib (compatibility version 37.0.0, current version 37.0.0)
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4)
/usr/local/lib/libstream.1.dylib (compatibility version 37.0.0, current version 37.0.0)
/usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
/usr/lib/libcrypto.0.9.7.dylib (compatibility version 0.9.7, current version 0.9.7)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
## Comment 12824
Date: 2009-12-10 13:26:21 +0100
From: @grobian
Let me guess, you have a -I and -L mismatch, e.g. configure checked for the required openssl against the headers of your updated version, but then linkage was performed against the system /usr/lib/libssl.dylib. Since libtool passes -undefined suppress by default you didn't notice during linktime you use the wrong lib.
## Comment 12825
Date: 2009-12-10 13:28:58 +0100
From: @grobian
you may have forgotten -search_path_first in your LDFLAGS
## Comment 12826
Date: 2009-12-10 18:20:06 +0100
From: Martin Dürre <<mduerre>>
Okay, just because i'm just beginning to get familar with the whole unix build process.
The problem is the line
/usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current version0.9.7) .
that states that openssl v097 is linked?
Some questions about it:
1. Is openssl requiered only by the MonetDB5 and sql Package? Because "Mserver --dbinit 'module(pathfinder); mil_start();'" seems to work.
2. I build the package again using './configure LDFLAGS="-search_path_first"'. Errors remain.
3. I there something i have to do after manually updating openssl to make the new libssl.dylib available?
Thanks for your help, somehow i seem to be stuck...
## Comment 12827
Date: 2009-12-10 18:33:37 +0100
From: @grobian
> Okay, just because i'm just beginning to get familar with the whole unix
> build process.
> The problem is the line
>
> /usr/lib/libssl.0.9.7.dylib (compatibility version 0.9.7, current
> version0.9.7) .
>
> that states that openssl v097 is linked?
yeah, but more importantly, it tells that the library from the host os is used (/usr/lib) which is insufficient (I just know that) and hence cannot work right
> Some questions about it:
> 1. Is openssl requiered only by the MonetDB5 and sql Package? Because
> "Mserver --dbinit 'module(pathfinder); mil_start();'" seems to work.
Yes, MonetDB4 is a fair bit older and not equipped with the more advanced security features of MonetDB5, which indeed require a recent OpenSSL.
> 2. I build the package again using './configure
> LDFLAGS="-search_path_first"'. Errors remain.
You need something like:
LDFLAGS="-search_path_first -L/path/to/separately/installed/lbs"
> 3. I there something i have to do after manually updating openssl to make
> the new libssl.dylib available?
yes, tell the linker where to find it using -L instructions (I hope you didn't overwrite your system provided version, that is...)
## Comment 12828
Date: 2009-12-11 00:17:26 +0100
From: Martin Dürre <<mduerre>>
Setting the path to a proper version of openssl hopefully worked for most parts.
Here is a look at otool -L /usr/local/lib/libmonetdb5.5.dyli:
/usr/local/lib/libmonetdb5.5.dylib:
/usr/local/lib/libmonetdb5.5.dylib (compatibility version 23.0.0, current version 23.0.0)
/usr/local/lib/libbat.1.dylib (compatibility version 37.0.0, current version 37.0.0)
/usr/local/lib/libmutils.1.dylib (compatibility version 37.0.0, current version 37.0.0)
/opt/local/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0)
/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3)
/usr/lib/libbz2.1.0.dylib (compatibility version 1.0.0, current version 1.0.5)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.4)
/usr/local/lib/libstream.1.dylib (compatibility version 37.0.0, current version 37.0.0)
/opt/local/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
For testing your installation the install guideline proposes make check and Mtest.py.
Both of them only run after getting and building the package testing that not is mentioned in the documentation. The tests themselfs seem to fail or to be skipped. Is there any real use in testing my install that way right now?
One problem left (at least I hope so ;)
Mserver --dbinit 'module(sql_server);'
starts the server but fails loading the module:
!ERROR: moduleClient: module(sql_server) load error.
Could it be that I missed something else because:
mserver5 --dbinit 'include sql;'
Mserver --dbinit 'module(pathfinder);'
are working.
Thanks again. Good night!
## Comment 12829
Date: 2009-12-11 08:29:43 +0100
From: @grobian
Please report new bugs for your additional issues.
Documentation should probably say that Mtest is only there when monetdb-testing is installed.
You can compare Mtest's output with that of our testing platforms:
http://monetdb.cwi.nl/Development/TestWeb/index.html
Mserver (MonetDB 4) + SQL is not supported.
## Comment 12830
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2911937 at http://sourceforge.net/support/tracker.php?aid=2911937
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.
| Linking seems to fail. | https://api.github.com/repos/MonetDB/MonetDB/issues/2276/comments | 0 | 2020-11-30T10:34:46Z | 2024-06-28T07:25:34Z | https://github.com/MonetDB/MonetDB/issues/2276 | 753,359,079 | 2,276 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-08 10:50:21 +0100
From: SergeyKazachenko <<bamboo7431>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-12-10 06:16:03 +0100
## Comment 12815
Date: 2009-12-08 22:50:21 +0100
From: SergeyKazachenko <<bamboo7431>>
I'm on Windows XP Professional.
Downloaded and installed MonetDB5-SQL-Installer-i386-20091119.msi
When I try to launch MonetDB SQL Server, I get the message box with "mserver5.exe" in the title and the message "This application has failed to start because lib_replication.lib was not found. Re-installing the application may fix this problem"
I cannot find the file lib_replication.lib anywhere, so it's not a PATH issue
The DOS box contains the following:
MonetDB server v5.16.0, based on kernel v1.34.0
Serving database 'demo', using 1 thread
Compiled for i686-pc-win32/32bit with 32bit OIDs dynamically linked
Detected 3.248 GiB (3487125504 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see C:\Program Files\MonetDB\MonetDB5\etc\monetdb5.conf)
WARNING: LoaderException:loadLibrary:File not found:replication
!MALException:malInclude:could not open file: opt_replication
!MALException:malInclude:could not open file: replication
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
WARNING: LoaderException:loadLibrary:Loading errorThe specified module could no
t be found.
.sql
!SyntaxException:parseError:function slave.open(tag:int, t:timestamp):bit;
!SyntaxException:parseError: ^<module> not defined
!TypeException:slave.open[3]:'algebra.exist' undefined in: c1:any := algebra.exi
st(X5:bat[:int,:oid], tag:any)
!TypeException:slave.open[7]:'algebra.exist' undefined in: c1:any := algebra.exi
st(X14:bat[:int,:oid], tag:any)
!TypeException:slave.open[3]:'tag' may not be used before being initialized
!TypeException:slave.open[7]:'tag' may not be used before being initialized
!SyntaxException:parseError:function slave.close(uri:str, tag:int, t:timestamp):
bit;
!SyntaxException:parseError: ^<module> not defined
!TypeException:slave.close[1]:'uri' may not be used before being initialized
!TypeException:slave.close[2]:'tag' may not be used before being initialized
!TypeException:slave.close[3]:'t' may not be used before being initialized
!TypeException:user.main[1]:'sql.prelude' undefined in: _1:void := sql.prelude()
>
## Comment 12816
Date: 2009-12-10 13:25:47 +0100
From: @sjoerdmullender
We made an error when packaging the Windows package, we forgot to include some new files in the installer.
Since the Nov2009-SP1 release is about to be created and tested, I can provide the (first?) release candidate for you to test. See <http://homepages.cwi.nl/~sjoerd/downloads/release/>.
## Comment 12817
Date: 2009-12-10 18:15:24 +0100
From: SergeyKazachenko <<bamboo7431>>
Thanks, this seems to work. At least it starts...
## Comment 12818
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2911008 at http://sourceforge.net/support/tracker.php?aid=2911008
| Cannot start because lib_replication.dll was not found | https://api.github.com/repos/MonetDB/MonetDB/issues/2275/comments | 0 | 2020-11-30T10:34:42Z | 2024-06-27T11:43:05Z | https://github.com/MonetDB/MonetDB/issues/2275 | 753,359,026 | 2,275 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-04 08:55:28 +0100
From: Floris Ouwendijk <<floris233>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
CC: @sjoerdmullender
Last updated: 2010-09-14 14:20:00 +0200
## Comment 12810
Date: 2009-12-04 08:55:28 +0100
From: Floris Ouwendijk <<floris233>>
It seems that adding a not clause to a query returns only a single item in the Nov2009 version (in May2008 SP2 it works).
I have reduced our data to the following testcase:
Insert the following as x.xml into the database:
-----------------------------------------------------
<r>
<a xid='1'><container t='2'/></a>
<a xid='2'><container t='2'/></a>
<a xid='3'><container t='2'/></a>
<a xid='4'><container t='2'/></a>
<a xid='5'><p><x xx='5'/></p></a>
<a xid='6'><p><x xx='6'/></p></a>
</r>
-----------------------------------------------------
The query doc("x.xml")//a[p/x/@xx] returns two elements, while doc("x.xml")//a[not(xyz) and p/x/@xx] returns a single element.
## Comment 12811
Date: 2009-12-04 08:58:18 +0100
From: Floris Ouwendijk <<floris233>>
Addition: it seems that the order is important too:
doc("x.xml")//a[p/x/@xx and not(xyz)] gives the proper result.
## Comment 12812
Date: 2009-12-05 14:30:06 +0100
From: @drstmane
All three queries indeed work fine also with Aug2009-SP2.
(Guess your "May200*8* SP2" is actually a "May200*9* SP2", right? ;-))
I can confirm that the first (doc("x.xml")//a[p/x/@xx]) and third (doc("x.xml")//a[p/x/@xx and not(xyz)]) query also work fine with Nov2009 as reported.
I can also confirm that the second query (doc("x.xml")//a[not(xyz) and p/x/@xx]) fails as reported with Nov2009.
Looking at the differences between the pf-generated MIL for the second query of both Aug2009-SP2 and Nov2009 (both attached), I see (among other differences) the following:
--- /tmp/x.mil.Aug2009-SP2.2 2009-12-05 14:05:24.000000000 +0100
+++ /tmp/x.mil.Nov2009.2 2009-12-05 14:20:09.000000000 +0100
[...]
@@ -276,9 +287,7 @@
a0003 := unused;
End rule: "Rel: project(Rel)"
Begin rule: "Rel: sort_distinct(Rel)"
- a0000 := a0009.reverse ().sort ().reverse ();
- a0000 := a0000.CTrefine (a0010);
- a0000 := a0000.CTrefine (a0011);
+ a0000 := a0009;
a0000 := a0000.reverse ().kunique ().tmark (0@0);
a0002 := a0000.leftjoin (a0009);
a0002 := a0002.reverse ().mark (0@0).reverse ();
[...]
Re-adding the "lost" sort seems to make the MIL code produce the expected answer.
Maybe Jan (R) might quickly have an idea what might go wrong, here ...
## Comment 12813
Date: 2009-12-06 00:12:11 +0100
From: Jan Rittinger <<jan.rittinger>>
Fixed in CVS -- it turned out to be an incorrect fd property check, introduced when optimizing the distinct operator planning.
## Comment 12814
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2908615 at http://sourceforge.net/support/tracker.php?aid=2908615
## Comment 14912
Date: 2010-09-14 14:19:30 +0200
From: @sjoerdmullender
Changeset [7f5f807a32e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=7f5f807a32e5) 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=7f5f807a32e5](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=7f5f807a32e5)
Changeset description:
Added test for bug #2274.
| Not clause breaks result | https://api.github.com/repos/MonetDB/MonetDB/issues/2274/comments | 0 | 2020-11-30T10:34:39Z | 2024-06-27T11:43:04Z | https://github.com/MonetDB/MonetDB/issues/2274 | 753,358,992 | 2,274 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-02 02:12:27 +0100
From: @drstmane
To: Tang Nan <<ntang928>>
Version: -- development
Last updated: 2010-03-17 08:10:52 +0100
## Comment 12806
Date: 2009-12-02 14:12:27 +0100
From: @drstmane
On Windows, the Microsoft compiler correctly(!) complains about various type-inconsistencies that might lead to overflows and hence unexpected or incorrect behaviors on all platforms.
For details see
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Mic.32.32.d.1-Windows6.0..2009.12.02_07-00-56/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/permastore/2009-12-02/Current/make-MonetDB5-Mic.32.32.d.1-Windows6.0.errors.htmll354
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Mic.64.32.d.1-Windows6.0..2009.12.02_07-00-56/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/permastore/2009-12-02/Current/make-MonetDB5-Mic.64.32.d.1-Windows6.0.errors.htmll353
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Mic.64.64.d.1-Windows6.0..2009.12.02_07-00-56/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/permastore/2009-12-02/Current/make-MonetDB5-Mic.64.64.d.1-Windows6.0.errors.htmll353
See also
ID: 2890702 "M5: pma.mx fails to compile on various platforms"
https://sourceforge.net/tracker/?func=detail&aid=2890702&group_id=56967&atid=482468
and (e.g.)
for i in 2 3 4 5 6 7 ; do ( cvs log -Nr1.$i src/modules/mal/pma.mx ; cvs diff -r1.{$[i-1],$i} src/modules/mal/pma.mx ) | cdiff ; done
Do not hesitate to ask in case you have any questions about proper and portable type usage in MonetDB.
## Comment 12807
Date: 2010-03-17 19:46:09 +0100
From: @mlkersten
Is this issue still present? Or can it be closed.
## Comment 12808
Date: 2010-03-17 20:10:52 +0100
From: @drstmane
compilation appears to have been fixed by
===================================================================
2009/12/04 - ntang928: MonetDB5/src/modules/mal/pma.mx,1.8
fix some bugs about type conversion failure on Windows
===================================================================
2009/12/05 - ntang928: MonetDB5/src/modules/mal/pma.mx,1.9
minor revision for type conversion and error message processing
===================================================================
2009/12/06 - ntang928: MonetDB5/src/modules/mal/pma.mx,1.10
for correcting type conversion warnings
===================================================================
However, in case the code should ever be used, it should be double checked for type consistency.
E.g., type BUN is not equal to type wrd, and dereferencing a pointer to a wrd as a BUN will not alwasy result in what one might expect, surely not with 32-bit OIDs on a 64-bit big-endian system ...
Closing this one.
I'll whether I understand the code well enough to take care of the type issue(s) ...
## Comment 12809
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2907463 at http://sourceforge.net/support/tracker.php?aid=2907463
| M5: pma.mx fails to compile on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/2273/comments | 0 | 2020-11-30T10:34:36Z | 2024-06-27T11:43:03Z | https://github.com/MonetDB/MonetDB/issues/2273 | 753,358,944 | 2,273 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-12-01 10:55:16 +0100
From: @grobian
To: @njnes
Version: -- development
Last updated: 2010-01-17 01:51:18 +0100
## Comment 12803
Date: 2009-12-01 10:55:16 +0100
From: @grobian
The server reports the width of a timestamp column to narrow:
sql>select now();
+----------------------------+
| current_timestamp |
+============================+
| 2009-12-01 |
: 09:51:10.000000+00:00 :
+----------------------------+
1 tuple
sql>\fraw
sql>select now();
% . table_name
% current_timestamp name
% timestamptz type
% 26 length
[ 2009-12-01 09:52:06.000000+00:00 ]
sql>
26 is indeed too narrow, causing mclient to wrap the column needlessly. The actual length is 32, it seems the timezone isn't counted.
The following demonstrates that the length is just wrong for timestamp with time zone fields:
sql>select cast(now() as timestamp with time zone);
+----------------------------+
| current_timestamp |
+============================+
| 2009-12-01 |
: 09:55:00.000000+00:00 :
+----------------------------+
1 tuple
sql>select cast(now() as timestamp);
+----------------------------+
| current_timestamp |
+============================+
| 2009-12-01 09:55:05.000000 |
+----------------------------+
1 tuple
sql>
## Comment 12804
Date: 2010-01-17 13:51:18 +0100
From: @njnes
fixed in stable. Info on timezone is now correctly passed to the export_length function.
No test needed as the timestamp.sql test allready covers this
## Comment 12805
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2906649 at http://sourceforge.net/support/tracker.php?aid=2906649
| SQL: timestampz width reported to narrow | https://api.github.com/repos/MonetDB/MonetDB/issues/2272/comments | 0 | 2020-11-30T10:34:31Z | 2024-06-27T11:43:02Z | https://github.com/MonetDB/MonetDB/issues/2272 | 753,358,888 | 2,272 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-24 02:41:41 +0100
From: @skinkie
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-11-27 08:54:37 +0100
## Comment 12798
Date: 2009-11-24 14:41:41 +0100
From: @skinkie
/opt/monetdb-head/bin/mserver5 --dbfarm=/home/skinkie/monetdb --dbname=monitor --dbinit="include sql;" --threads 1
MonetDB server v5.17.0, based on kernel v1.35.0
Serving database 'monitor', using 2 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Detected 4.000 GiB (4295331840 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /opt/monetdb-head/etc/monetdb5.conf)
01 1 140683233527553 sp = 140734711916164
01 nrofthreads 0
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.35.0 loaded
01 BBPdir: writing BBP.dir (527 bats).
WARNING: could not open file: /home/skinkie/monetdb/1
## Comment 12799
Date: 2009-11-24 14:48:50 +0100
From: @grobian
there is just bogus in the monetdb5.conf file (misleading to say the least)
there is no overwriting going on here, as the database properly reports to be serving "monitor", it simply complains that it can't find a file "1" to open. The --thread option seems to enable some magical debug output, and not do what you expect.
Try --set gdk_nr_threads=1
## Comment 12800
Date: 2009-11-24 15:32:23 +0100
From: @drstmane
a)
yes, the --threads option exist, but it does not take any argument; as monetdb5.conf says, "--threads" is merely a short cut for "--debug=$[1+128]", i.e., for setting debug bits 1 (thread-specific debug output) and 128 (PARMASK = Thread management).
(As Fabian said, if you want to set the number of threads, you need to us "--set gdk_nr_threads=1"; cf. e.g., http://monetdb.cwi.nl/projects/monetdb/Development/Releases/Nov2008/index.htmlIssues)
b)
The error is perfectly fine and correct:
Your mserver5 commanline specifies three option with arguments (--dbfarm=/home/skinkie/monetdb, --dbname=monitor, --dbinit="include sql;"), one without argument (--threads), and (the name of) one (MAL-)script to be executed (1) --- see also `mserver5 --help` --- the latter does not seem to exist in your working directory (you didn't specify an absolute path), and MonetDB informs you about that.
IMHO all fine and correct.
## Comment 12801
Date: 2009-11-27 08:54:22 +0100
From: @drstmane
Closing --- see my previous comment.
## Comment 12802
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2903122 at http://sourceforge.net/support/tracker.php?aid=2903122
| M5: --threads option exists? (monetdb5.conf documentation) | https://api.github.com/repos/MonetDB/MonetDB/issues/2271/comments | 0 | 2020-11-30T10:34:28Z | 2024-06-28T07:25:33Z | https://github.com/MonetDB/MonetDB/issues/2271 | 753,358,838 | 2,271 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-24 02:29:23 +0100
From: @skinkie
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-11-27 08:52:24 +0100
## Comment 12792
Date: 2009-11-24 14:29:23 +0100
From: @skinkie
Reproduce with:
create (as root) a dbfarm directory
switch to the normal user
start monet with this dbfarm directory and (thus) a new database
The error that arrises is:
!FATAL: GDKlockHome: could not move to /home/skinkie/monetdb/monitor/
It seems MonetDB did not check if the directory could not be created.
## Comment 12793
Date: 2009-11-24 14:32:37 +0100
From: @skinkie
Fabian hinted also to write this is a permission error. Hence the dbfarm dir was owned by root, and not by the user that tried to start the database.
## Comment 12794
Date: 2009-11-24 15:36:06 +0100
From: @drstmane
MonetDB does (try to) "move" (`cd`) to the dbfarm/dbname.
If this fails for whatever reason (e.g., because the user isn't allowed to do so by filesystem access rights), this fails and MonetDB returns an error.
Perfectly reasonable with me ...
## Comment 12795
Date: 2009-11-24 15:38:36 +0100
From: @grobian
The bug here is that the message is misleading. MonetDB normally creates the directory for the dbname (monitor), however that failed (it must be), but apparently MonetDB didn't complain about that. It only fails once it tries to set its lock.
We should complain earlier when we can't create the dbname dir, if it doesn't exist already.
## Comment 12796
Date: 2009-11-27 08:52:24 +0100
From: @drstmane
===================================================================
2009/11/27 - stmane: MonetDB/src/gdk/gdk_utils.mx,1.255.2.6
fixing ID: 2903111 "Wrong error / no check for new database dir"
https://sourceforge.net/tracker/?func=detail&aid=2903111&group_id=56967&atid=482468
give more detailed error message, whether we fail to create
/dbfarm/dbname, or whether we fail to move (cd) to it
===================================================================
Closing w/o test, as this is merely an error message convenience, and making a portable test with platform-invariant output would be an overkill.
## Comment 12797
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2903111 at http://sourceforge.net/support/tracker.php?aid=2903111
| Wrong error / no check for new database dir | https://api.github.com/repos/MonetDB/MonetDB/issues/2270/comments | 0 | 2020-11-30T10:34:25Z | 2024-06-27T11:43:00Z | https://github.com/MonetDB/MonetDB/issues/2270 | 753,358,793 | 2,270 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-24 01:46:56 +0100
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2010-04-18 05:56:02 +0200
## Comment 12789
Date: 2009-11-24 13:46:56 +0100
From: @grobian
side effect of quicktest (running all tests in All using mclient on the same server):
stderr of test 'inspect05` in directory 'src/modules/mal` itself:
mserver5 --dbfarm=/tmp/tmp.vlQ0XpqTNy/server/mal/src_modules_mal/dbfarm --dbname=mTests_src_modules_mal --set mapi_port=54000 --set monet_daemon=yes
warning: please don't forget to set your vault key!
(see /export/scratch/stripe/fabian/monetdb/current/program-i86pc/etc/monetdb5.conf)
mclient -i -lmal -p54000 < src/modules/mal/Tests/inspect05.mal
MAPI = monetdb@localhost:54000
ACTION= read_line
QUERY = k:= inspect.getKind();
ERROR = !Connection terminated
additional server output (if any) follows
EOT src/modules/mal/Tests/inspect05.mal
stdout of test 'inspect05` in directory 'src/modules/mal` itself:
mserver5 --dbfarm=/tmp/tmp.vlQ0XpqTNy/server/mal/src_modules_mal/dbfarm --dbname=mTests_src_modules_mal --set mapi_port=54000 --set monet_daemon=yes
mclient -i -lmal -p54000 < src/modules/mal/Tests/inspect05.mal
additional server output (if any) follows
EOT src/modules/mal/Tests/inspect05.mal
## Comment 12790
Date: 2010-04-18 17:56:02 +0200
From: @mlkersten
I can not reproduce this error. Assuming it has been fixed as a side-effect of all the changes.
## Comment 12791
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2903085 at http://sourceforge.net/support/tracker.php?aid=2903085
| M5: segfault on inspect05 | https://api.github.com/repos/MonetDB/MonetDB/issues/2269/comments | 0 | 2020-11-30T10:34:22Z | 2024-06-28T07:25:33Z | https://github.com/MonetDB/MonetDB/issues/2269 | 753,358,761 | 2,269 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-24 01:17:07 +0100
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2010-05-19 15:43:44 +0200
## Comment 12786
Date: 2009-11-24 13:17:07 +0100
From: @grobian
side effect of quicktest (running all tests in All file through mclient), I found this crash:
stderr of test 'tst272` in directory 'src/mal` itself:
mserver5 --dbfarm=/tmp/tmp.wSFC1a0iC6/server/mal/src_mal/dbfarm --dbname=mTests_src_mal --set mapi_port=54000 --set monet_daemon=yes
warning: please don't forget to set your vault key!
(see /export/scratch/stripe/fabian/monetdb/current/program-i86pc/etc/monetdb5.conf)
mclient -i -lmal -p54000 < src/mal/Tests/tst272.mal
MAPI = monetdb@localhost:54000
ACTION= read_line
QUERY = profiler.cleanup();
ERROR = !Connection terminated
additional server output (if any) follows
Assertion failed: 0, file /export/scratch/mirror/fabian/monetdb/current/common/src/gdk/gdk_bbp.mx, line 1814, function decref
EOT src/mal/Tests/tst272.mal
stdout of test 'tst272` in directory 'src/mal` itself:
mserver5 --dbfarm=/tmp/tmp.wSFC1a0iC6/server/mal/src_mal/dbfarm --dbname=mTests_src_mal --set mapi_port=54000 --set monet_daemon=yes
mclient -i -lmal -p54000 < src/mal/Tests/tst272.mal
-----------------
h t name
int int type
-----------------
[ 1, 15 ]
[ 2, 4 ]
[ 3, nil ]
[ 4, 16 ]
[ 5, 25 ]
[ 6, 36 ]
[ 7, 49 ]
[ 8, 64 ]
[ 9, nil ]
[ nil, nil ]
[ nil, 81 ]
---------------------------------
h t t t name
int int int int type
---------------------------------
[ 1, 15, 15, 15 ]
[ 2, 4, 4, 4 ]
[ 3, nil, nil, nil ]
[ 4, 16, 16, 16 ]
[ 5, 25, 25, 25 ]
[ 6, 36, 36, 36 ]
[ 7, 49, 49, 49 ]
[ 8, 64, 64, 64 ]
[ 9, nil, nil, nil ]
~BeginVariableOutput~
~EndVariableOutput~
additional server output (if any) follows
MonetDB server v5.17.0, based on kernel v1.35.0
Serving database 'mTests_src_mal', using 1 thread
Compiled for x86_64-pc-solaris2.11/64bit with 64bit OIDs dynamically linked
Detected 2.000 GiB (2147020800 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Listening for connection requests on mapi:monetdb://127.0.0.1:54000/
EOT src/mal/Tests/tst272.mal
## Comment 12787
Date: 2009-11-27 13:02:45 +0100
From: @mlkersten
Patch added to mal_profiler. No additional test needed.
## Comment 12788
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2903072 at http://sourceforge.net/support/tracker.php?aid=2903072
## Comment 14049
Date: 2010-05-19 15:43:44 +0200
From: @grobian
I cannot reproduce this particular issue at the moment
| M5/GDK: assertion decref in gdk_bbp.mx | https://api.github.com/repos/MonetDB/MonetDB/issues/2268/comments | 0 | 2020-11-30T10:34:19Z | 2024-06-28T07:25:33Z | https://github.com/MonetDB/MonetDB/issues/2268 | 753,358,720 | 2,268 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-23 09:01:18 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2009-11-29 09:02:26 +0100
## Comment 12783
Date: 2009-11-23 09:01:18 +0100
From: @mlkersten
create table tmp(i int);
copy into tmp from 'file1','file2';
only produces the MAL code for copying file1.
## Comment 12784
Date: 2009-11-29 09:02:26 +0100
From: @njnes
added test copy_multiple_files.SF-2902320.sql
Added the missing code for handling multiple files
## Comment 12785
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2902320 at http://sourceforge.net/support/tracker.php?aid=2902320
| SQL: COPY multiple files | https://api.github.com/repos/MonetDB/MonetDB/issues/2267/comments | 0 | 2020-11-30T10:34:16Z | 2024-06-27T11:42:57Z | https://github.com/MonetDB/MonetDB/issues/2267 | 753,358,679 | 2,267 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-22 10:19:39 +0100
From: @njnes
To: GDK devs <<bugs-common>>
Version: -- development
CC: @mlkersten, sellam, @yzchang
Last updated: 2015-11-11 09:18:07 +0100
## Comment 12781
Date: 2009-11-22 22:19:39 +0100
From: @njnes
Creating a single bug report about out of memory problems. When we run out of memory the exception handling isn't properly taken all the way up to the client session level, resulting in crashes.
## Comment 12782
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2902177 at http://sourceforge.net/support/tracker.php?aid=2902177
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 18147
Date: 2012-11-27 16:26:38 +0100
From: @yzchang
No possible to add a test for this bug
## Comment 21504
Date: 2015-11-11 09:18:07 +0100
From: @mlkersten
No specific test can be created for this issue. Awaiting new reports with hints on where to act properly.
| out of memory crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/2266/comments | 0 | 2020-11-30T10:34:12Z | 2024-06-28T07:25:32Z | https://github.com/MonetDB/MonetDB/issues/2266 | 753,358,641 | 2,266 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-19 11:46:50 +0100
From: Wouter Alink <<alink>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2010-08-30 09:18:27 +0200
## Comment 12775
Date: 2009-11-19 11:46:50 +0100
From: Wouter Alink <<alink>>
When running 2 mclient instances simultaneously, the 1st mclient can run tracelog(), the second cannot (the error message is "SELECT: '(null)' does not return a table").
$ mclient -lsql -p51234 -daap
Welcome to mclient, the MonetDB/SQL interactive terminal
Database: MonetDB v5.16.0, 'aap'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT * FROM tracelog();
0 tuples
sql>
On another prompt:
$ mclient -lsql -p51234 -daap
Welcome to mclient, the MonetDB/SQL interactive terminal
Database: MonetDB v5.16.0, 'aap'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT * FROM tracelog();
SELECT: '(null)' does not return a table
sql>
## Comment 12776
Date: 2009-11-19 16:42:43 +0100
From: Wouter Alink <<alink>>
when running trace using JDBC, multiple connections to the same database do seem to be able to query tracelog(). (if no mclient is running)
however, they are not isolated from each other; work done in one transaction, can be found in a call to tracelog() in another transaction.
## Comment 12777
Date: 2009-11-27 11:42:54 +0100
From: @mlkersten
This report has not been confirmed for initial state. Having multiple clients over the same database scheme and announced the definition of the tracelog function once seems to work as expected.
Where there more processes running, e.g. updating the performance tables?
Tracing the kernel is a global activity. For interpretation of timings this is a prerequisite.
## Comment 12778
Date: 2009-11-27 11:51:35 +0100
From: Wouter Alink <<alink>>
I indeed reported it, without declaring the tracelog() function (as it isn't documented).
would there be any objections to defining the tracelog() function by default? (does it have to be defined for each database, or can it be done once globally?)
I can imagine that this function is not needed for many users, so perhaps the behaviour should stay as is.
If the documentation clearly mentions that the function should first be declared before it can be used, i'm fine with closing this bug.
## Comment 12779
Date: 2009-11-27 11:52:45 +0100
From: Wouter Alink <<alink>>
oops, wrong bug, ignore previous message please.
## Comment 12780
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2900365 at http://sourceforge.net/support/tracker.php?aid=2900365
## Comment 14675
Date: 2010-08-13 14:02:07 +0200
From: @njnes
fixed by adding some more locks
## Comment 14813
Date: 2010-08-30 09:18:27 +0200
From: @sjoerdmullender
The Jun2010-SP2 version has been released.
| SQL: concurrent tracelog() | https://api.github.com/repos/MonetDB/MonetDB/issues/2265/comments | 0 | 2020-11-30T10:34:09Z | 2024-06-27T11:42:55Z | https://github.com/MonetDB/MonetDB/issues/2265 | 753,358,606 | 2,265 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-19 11:29:51 +0100
From: Wouter Alink <<alink>>
To: @mlkersten
Version: -- development
Last updated: 2009-11-19 12:36:49 +0100
## Comment 12771
Date: 2009-11-19 11:29:51 +0100
From: Wouter Alink <<alink>>
The function tracelog() is not defined by default. If the sql query 'create function ... sql.dump_trace;'
(provided in http://www.monetdb.nl/projects/monetdb/SQL/Documentation/TRACE-Statement.html) is first executed then it works fine.
(I added a test SQL:src/test/Tests/trace)
$ monetdb create aap
created database in maintenance mode: aap
$ monetdb start aap
starting database 'aap'... done
$ mclient -lsql -p51234 -daap -umonetdb -Pmonetdb
Welcome to mclient, the MonetDB/SQL interactive terminal
Database: MonetDB v5.16.0, 'aap'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>SELECT * FROM tracelog();
SELECT: no such operator 'tracelog'
$ mserver5 --version
MonetDB server v5.16.0 (64-bit), based on kernel v1.34.0 (64-bit oids)
Copyright (c) 1993-July 2008 CWI
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
Configured for prefix: /ufs/alink/opt/MonetDB-Nov2009
Libraries:
libpcre: 7.8 2008-09-05 (compiled with 7.8)
openssl: OpenSSL 0.9.8g 19 Oct 2007 (compiled with OpenSSL 0.9.8g 19 Oct 2007)
libxml2: 2.7.6 (compiled with 2.7.6)
Compiled by: alink@loki.ins.cwi.nl (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 : ld -IPA -m elf_x86_64
## Comment 12772
Date: 2009-11-19 11:31:41 +0100
From: Wouter Alink <<alink>>
i think this is martin's area ;) re-assiging to martin.
## Comment 12773
Date: 2009-11-19 12:36:49 +0100
From: @mlkersten
Correct. There is no hardcoded definition for this function in the SQL catalog.
It is part of a collection of sql scripts in .../src/sql/*.sql that have to be loaded once for a database.
That's why the definition was also repeated in the documentation
## Comment 12774
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2900358 at http://sourceforge.net/support/tracker.php?aid=2900358
| SQL: tracelog() is undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/2264/comments | 0 | 2020-11-30T10:34:06Z | 2024-06-28T07:25:32Z | https://github.com/MonetDB/MonetDB/issues/2264 | 753,358,565 | 2,264 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-19 11:24:32 +0100
From: Wouter Alink <<alink>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2010-01-21 12:48:41 +0100
## Comment 12768
Date: 2009-11-19 11:24:32 +0100
From: Wouter Alink <<alink>>
Very minor issue: The output of the monetdb utility might be a little bit confusing. The 'last crash' time, seems to be the start time of the previous mserver session that crashed. Because the server crashed a few seconds before I started it again, while it seems to show that there are 13 minutes in between the two sessions. Perhaps the description should be changed to "start time of last session that crashed " or something similar.
$ monetdb status -l aap
aap:
location: /export/scratch0/roberto/wouter/dbfarm-MonetDB-Nov2009/aap
database name: aap
state: running
locked: no
scenarios: mal sql msql
connections: mapi:monetdb://127.0.0.1:51236/
start count: 3
stop count: 0
crash count: 2
current uptime: 10s
average uptime: 0s
maximum uptime: 0s
minimum uptime: 0s
last crash: 2009-11-19 10:47:18
last start: 2009-11-19 11:00:13
average of crashes in the last start attempt: 0
average of crashes in the last 10 start attempts: 0.20
average of crashes in the last 30 start attempts: 0.07
## Comment 12769
Date: 2010-01-21 12:48:40 +0100
From: @grobian
fixed in stable branch
## Comment 12770
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2900355 at http://sourceforge.net/support/tracker.php?aid=2900355
| M5: crash time | https://api.github.com/repos/MonetDB/MonetDB/issues/2263/comments | 0 | 2020-11-30T10:34:03Z | 2024-06-27T11:42:53Z | https://github.com/MonetDB/MonetDB/issues/2263 | 753,358,533 | 2,263 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-17 09:27:26 +0100
From: Axel Belinfante <<axelbel>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
CC: @sjoerdmullender
Last updated: 2010-09-14 14:01:00 +0200
## Comment 12749
Date: 2009-11-17 09:27:26 +0100
From: Axel Belinfante <<axelbel>>
I don't know whether the following really qualifies as bug, or just is a case of 'user error by giving stupid input.
In any case, I would like to bring this to your attention.
When I compile a query for attached module definition with pf (may or aug or pre-nov version), compilation takes 'forever'.
When I replace the clause ecv:to-human($g0, $human_type) by simple $g0
and remove definitions of $human_type and to-human it compiles almost instantly.
It is the huge difference in compilation time that surprises me.
The query I compile is:
import module namespace ecv = "http://www.cs.utwente.nl/~belinfan/ecv" at "/tmp/long-compilation.xq"; ecv:view-from-save("eprints-export-conv-fmt.xml")
where tmp/long-compilation.xq is the attached module.
What the query attempts to do: obtain results from the database, order these on two criteria, and when listing the results, insert human-readable headers.
The human-readable headers are obtained by the to-human mapping from field value (used as ordering criterium) to human-readable string.
At some point I just used if-then-else-if-then-else etc. to do the mapping, but that seemed slower to compile than the approach I took here.
Suggestions for rewriting the query to a fast-compiling one would be considered as a fix too, I guess.
## Comment 12750
Date: 2009-11-17 09:32:15 +0100
From: Axel Belinfante <<axelbel>>
not sure about category or group - chose seemingly most appropriate.
even though I did not change default priority , having some answer for this
(whether fix in code, or guideline for fast compiling query) would be very helpful.
In my application the pf compilation run is triggered from a web-gui - fast compilation
is very important there, and predicatable compilation times maybe even more.
(i.e. it would be nice when all compilations would take the same order of time).
## Comment 12751
Date: 2009-11-18 10:20:05 +0100
From: Jan Rittinger <<jan.rittinger>>
The reason for the 'forever' compile time is that the physical plan space blows up in a heuristic that tries to find good plan orders. I now added a check that avoids generating to many plans.
I checked in the fix in the Nov2009 stable branch. I'm however not sure whether it makes it into the release -- probably not. So please get it from either CVS or nightly-builds.
## Comment 12752
Date: 2009-11-18 11:03:04 +0100
From: @drstmane
I think, adding a test (also) for this one should be done; it should be not only possible, but also easy:
the query that (used to) compile for for than one hour is given, just make a test that calls pf to compile the query, sending the output to, say, /dev/null/ .
If that finishes without error and within the default 1 minute timeout (or less, if desired/required; add a TSTNME.timeout file with a <1 scale factor), the test succeeded and everything is fine; otherwise, the test fails ...
... just an idea to help assessing and monitoring this issue and hence the stability and usability of MonetDB as such ...
... does not apply to this bug report, only; see also my email of last weekend ...
... if there is no time right no to add the test, keep the bug report open to remind us ...
... in fact, I do exactly that ...
## Comment 12753
Date: 2009-11-18 11:30:35 +0100
From: Axel Belinfante <<axelbel>>
I don't want to spoil the fun, but after the fix pf still runs pretty long on the file I just attached
(long-compilation2.xq)
top gives me:
PID USER NI VIRT RES SHR P S %CPU %MEM TIME COMMAND
26940 dbguest 0 7164m 3.7g 172 4 R 27 96.5 14:07 /local/dbguest/Install/MonetDB-XQuery_Nov2009/bin/pf -T /tmp/talt11
I tried to kill it with ^C, without too much success
(and I already started to fear that the machine was hung up on it),
until a little later I saw (I started it as: time /path/to/pf xqueryfile)
Killed
828.295u 39.446s 16:38.94 86.8% 0+0k 0+0io 5pf+0w
Segmentation fault
## Comment 12754
Date: 2009-11-18 12:03:34 +0100
From: @drstmane
Axel,
what about your original long-compilation.xq?
Does that now work fine for you (i.e., with Jan's fix)?
## Comment 12755
Date: 2009-11-18 12:36:00 +0100
From: Axel Belinfante <<axelbel>>
the original long-compilation.xq now finishes in about 10 secs, which is still longer than I would like,
but much shorter than it used to.
regarding time measurements, I may have caused some confusion, in the sense that:
- the original long-compilation.xq definitely took 'too long', but likely I always interruped it
long before 1 hour passed
- the query that prompted me change the bug summmary line to include '> 1 hour' was a
different one, I'm sure that was long-compilation2.xq
long-compilation2.xq might have taken down a machine before the fix
(machine did crash while that pf was running, but we do not know whether that was the cause)
after applying the fix and rerunning the pf on long-compilation2.xq I do notice that
at some point the machine stops being responsive,
only to become responsive again after the segfault -
maybe the segfault saved us from a second machine crash :-)
I wonder whether the memory consumption is what so badly affects responsivity of the machine.
## Comment 12756
Date: 2009-11-18 12:53:34 +0100
From: @drstmane
Just a few general notes:
1)
A user program can at most trigger a machine crash, but never cause it.
If a user program triggers a machine crash (e.g., by using resources (too?) many resources, it's in the end a problem (bug) in the OS (or the hardware) that cannot properly handle (or prevent) such (over-)load properly.
2)
If you kill (via keyboard interrupt ^C or by sending, say, SIGTERM or SIGKILL) a process that uses lots of memory (and possibly virtual memory, i.e., swap), it might indeed take some time until that process is gone and your prompt is back, since the systems needs to clean up that memory (and swap) and possibly swap your shell back into main memory ...
3)
Yes, a process that is using much memory (i.e., close to or more than the machine has physical memory) might (usually will) affect the interactive responsiveness of the machine.
## Comment 12757
Date: 2009-11-18 16:51:28 +0100
From: Jan Rittinger <<jan.rittinger>>
Plan generation with permutations gets you into trouble.
Planning the distinct operator requires a full ordering of the table as we use the order extend in MIL to remove duplicates. To calculate the plans for all possible orders we generate all permutations. (In the first long-compilation example distinct was applied to a table with 7 columns and for the second example distinct operated on 8 columns.)
Now we first eliminate all functionally dependent and constant columns as they do not add any order information. If we still have too many permutations we ignore all orderings (plans) after a magic boundary.
With this changes in place the compile times are (almost) acceptable:
pf -T query-long-compilation.xq
...
overall compilation time: 974ms
pf -T query-long-compilation2.xq
...
overall compilation time: 02s 781ms
## Comment 12758
Date: 2009-11-18 18:34:17 +0100
From: @drstmane
===================================================================
2009/11/18 - stmane: pathfinder/tests/BugTracker/Tests/All,1.146.2.11
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.bat,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.mod1.xq,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.mod2.xq,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.q1.xq.in,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.q2.xq.in,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.sh,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.stable.err,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.stable.out,1.1.2.1
pathfinder/tests/BugTracker/Tests/slow_compilation.SF-2898944.timeout,1.1.2.1
added test (compilation via pf, only) for
ID: 2898944 "pf takes 'forever' (> 1 hour) to compile particular query"
https://sourceforge.net/tracker/?func=detail&aid=2898944&group_id=56967&atid=482468
Seems to work fine, now;
compiling both queries with both `pf -A` & `pf -M`
takes less than 2 secs on my machine with a debug build.
Set timeout to 6 secs.
===================================================================
report can be closed, once nightly testing and Axel confirm the fix.
## Comment 12759
Date: 2009-11-18 19:35:06 +0100
From: @sjoerdmullender
If this fix works out, it will be in the upcoming release. (We had some show stoppers with yesterday's release candidate.)
## Comment 12760
Date: 2009-11-19 10:00:29 +0100
From: @drstmane
Test works fine:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/slow_compilation.SF-2898944.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/slow_compilation.SF-2898944.err.00.html
Axel,
could you please check and report whether Jan's fix also works for you,
and if so, close this bug report?
Thanks!
## Comment 12761
Date: 2009-11-19 14:13:16 +0100
From: Axel Belinfante <<axelbel>>
I have tried the latest fix.
there is a good thing, and there is a bad thing.
the good thing is that for these queries the fix works.
that is really, really great.
the bad thing is that it is easy to add complexity (add more of the same thing),
and again have a relatively slow compilation - although, due to the fix
now compilation does finish.
fact is, those queries are not hand-written, but generated from more high-level user input.
it is easy for the user to make a slight change to the intended presentation of the query results
(add more refined structuring/grouping of the results), which can result in query for which
again compilation time is long.
to give an example:
in long-compilation2.xq I have 3 levels of structure. it compiles in about 3 secs.
file long-compilation3.xq (attached) has 6 levels of structure. it compiles in approx. 37 minutes.
running the compiled query takes iat most a couple of seconds
I tried rewriting the queries.
I could only obtain reduced compilation time (only 2 minutes) by adding additional
(pre=-processed) data to the database.
even then, running the compiled query takes approximately a minute...
(I also tried compiling with -M -- this is fast, but I was unable to run it
MAPI = dbguest@localhost:51012
QUERY = proc_vid.insert("fnC8CAED69_print_4_eprint_xs_element1", 1059825001LL);
...
ERROR = !ERROR: interpret: unknown variable 'proc_vid'.
!ERROR: interpret_params: insert(param 1): evaluation error.
)
I'm not sure you want to close this issue while such 'slight' changes to a query
have such huge effects on compilation time.
## Comment 12762
Date: 2009-11-19 18:04:38 +0100
From: Jan Rittinger <<jan.rittinger>>
Axel,
you hit different problems here. Your original bug caused the planner to take generate millions of plans.
Your latest example however generates a plan that features 5420 operators out of which 660 are joins. Here the join optimization takes a little bit...
What happens if you don't optimize much? -- Try e.g., the following (if you leave out the 'E' letter compilation time will probably halve):
echo 'import module namespace ecv = "http://www.cs.utwente.nl/~belinfan/ecv" at "/tmp/long-compilation3.xq"; ecv:view-from-save("eprints-export-conv-fmt.xml")' | pf -oOIKCG_VG_IS_GYECSVR_DC_GP > foo; Mserver foo
## Comment 12763
Date: 2009-11-19 18:22:46 +0100
From: Axel Belinfante <<axelbel>>
time pf -oOIKCG_VG_IS_GYECSVR_DC_GP /tmp/long-compilation3.req > /tmp/long-compilation3.mil
15.868u 0.472s 0:16.33 100.0% 0+0k 0+0io 0pf+0w
time mclient -lmil -p 51012 /tmp/long-compilation3.mil > /dev/null
0.016u 0.032s 0:03.80 1.0% 0+0k 0+0io 0pf+0w
compilation time is indeed much, much better (though still a bit long)
run time of resulting .mil is kind of ok (even faster would be even better, of course :-)
anything else I could try?
otherwise, I guess I will just use the options you suggested when compiling those generated queries,
and that should do for now.
## Comment 12764
Date: 2009-11-19 21:15:56 +0100
From: Jan Rittinger <<jan.rittinger>>
Alex,
if you want to toy around with the algebraic optimizations (option -o of pf) and its effect on compile and runtime, then feel free to try out the following optimizations:
-oOIKCGP
-oOIKCG_VG_IS_GYSVR_DC_GP
## Comment 12765
Date: 2010-01-21 11:45:04 +0100
From: @sjoerdmullender
What is the status?
## Comment 12766
Date: 2010-04-16 17:16:57 +0200
From: @sjoerdmullender
Can this be closed?
## Comment 12767
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2898944 at http://sourceforge.net/support/tracker.php?aid=2898944
## Comment 14911
Date: 2010-09-14 14:01:00 +0200
From: @sjoerdmullender
Closing since it seems to be fixed and nobody responds to questions.
| pf takes 'forever' (> 1 hour) to compile particular query | https://api.github.com/repos/MonetDB/MonetDB/issues/2262/comments | 0 | 2020-11-30T10:33:59Z | 2024-06-27T11:42:52Z | https://github.com/MonetDB/MonetDB/issues/2262 | 753,358,485 | 2,262 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-16 11:12:01 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-11-16 11:32:30 +0100
## Comment 12746
Date: 2009-11-16 11:12:01 +0100
From: @drstmane
Peter,
could you please have a look at "your" tests in MonetDB4/tests/by_Peter/Tests/ ?
They fail for quite some time, but at least some of the changes might have been intended with your mmap, etc. changes or are at least acceptable:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/tests_by_Peter/trim.out.00.html
fails since 2009.06.29
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/tests_by_Peter/tst_updatestr.out.00.html
fails since 2009.03.03
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/tests_by_Peter/tst_append_readonly.out.00.html
fails since 2009.02.06 on some platforms and since 2009.03.03 on all platforms
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/tests_by_Peter/tst_append_readonly_commit.out.00.html
fails since 2009.02.06 on some platforms and since 2009.03.03 on all platforms
## Comment 12747
Date: 2009-11-16 23:32:30 +0100
From: @peterboncz
Hi Stefan, thanks for bringing this to my attention. fixed
## Comment 12748
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2898378 at http://sourceforge.net/support/tracker.php?aid=2898378
| M4: tests/by_Peter fail | https://api.github.com/repos/MonetDB/MonetDB/issues/2261/comments | 0 | 2020-11-30T10:33:55Z | 2024-06-27T11:42:51Z | https://github.com/MonetDB/MonetDB/issues/2261 | 753,358,443 | 2,261 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-13 11:18:07 +0100
From: Axel Belinfante <<axelbel>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-11-15 03:28:36 +0100
## Comment 12740
Date: 2009-11-13 11:18:07 +0100
From: Axel Belinfante <<axelbel>>
compiling attached query with pf causes it to report:
fatal error: duplicate column `item778' in equi-join
halted in logical.c (PFla_eqjoin), line 690
this is on linux :
Linux ewi865 2.6.16.21-0.8-smp 1 SMP Mon Jul 3 18:25:39 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux
this is with the may-2009 release, as well as with the aug-2009-sp2 release.
## Comment 12741
Date: 2009-11-13 11:22:39 +0100
From: Axel Belinfante <<axelbel>>
(not sure about right category or group; this seems most logical)
## Comment 12742
Date: 2009-11-13 11:53:33 +0100
From: Axel Belinfante <<axelbel>>
one more note: when I submit the equivalent query to mclient -lx it works (produces the expected output)
where equivalent means: replacing the ./ in at "./duplicate-column-issue.xq"
by a full path, eg at "/tmp/duplicate-column-issue.xq";
## Comment 12743
Date: 2009-11-13 12:04:34 +0100
From: @drstmane
Jan,
could you please have a look at this.
As background info:
until Peter disabled this a few day ago in the Nov2009 release candidate branch,
the embedded compiler did automatically switch back to the old MPS version of the compiler once it encounters a module query.
That's why Alex's query appears to work with mclient but fails with pf.
In fact, it works (i.e., produces MIL instead of triggering the reported error) for me also with `pf -M` i.e., forcing pf to use its deprecated MPS back-end ...
## Comment 12744
Date: 2009-11-15 15:28:36 +0100
From: Jan Rittinger <<jan.rittinger>>
Fixed in Nov2009 branch.
A corner case in the rank optimization, triggered the problem.
No test added as any other order of applying the optimization or additional optimization will problem hide the problem.
## Comment 12745
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2897126 at http://sourceforge.net/support/tracker.php?aid=2897126
| pf fatal error: duplicate column in equi-join | https://api.github.com/repos/MonetDB/MonetDB/issues/2260/comments | 0 | 2020-11-30T10:33:52Z | 2024-06-27T11:42:50Z | https://github.com/MonetDB/MonetDB/issues/2260 | 753,358,397 | 2,260 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-12 08:39:01 +0100
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
Duplicates: #2256
Last updated: 2010-05-04 22:04:37 +0200
## Comment 12737
Date: 2009-11-12 20:39:01 +0100
From: @mlkersten
The tests/by_Peter should be inspected and (partially) propagated to M5.
## Comment 12738
Date: 2009-11-12 20:39:54 +0100
From: @mlkersten
double registration
## Comment 12739
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2896804 at http://sourceforge.net/support/tracker.php?aid=2896804
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb5@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 13994
Date: 2010-05-04 21:58:47 +0200
From: @mlkersten
This is a duplicate of bug #2256
## Comment 13996
Date: 2010-05-04 22:04:37 +0200
From: @grobian
"Mark as Duplicate" or RESOLVED -> DUPLICATE => dup number
*** This bug has been marked as a duplicate of bug #2256 ***
| M5: propagation of M4 tests | https://api.github.com/repos/MonetDB/MonetDB/issues/2259/comments | 0 | 2020-11-30T10:33:49Z | 2024-06-28T07:25:32Z | https://github.com/MonetDB/MonetDB/issues/2259 | 753,358,359 | 2,259 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-11 04:41:48 +0100
From: Stephen Benz <<sbenz>>
To: @njnes
Version: -- development
Last updated: 2009-11-11 10:13:15 +0100
## Comment 12733
Date: 2009-11-11 16:41:48 +0100
From: Stephen Benz <<sbenz>>
Attempting to write a sql statement that contains the same field in both an AND clause and an OR clause causes a TypeException to occur.
### Steps to reproduce:
sql>create table "simple" (id int,field1 int, field2 int);
sql>select * from "simple" where field1 = 1 and (field1 = 1 or field2 = 1);
Error seen:
!TypeException:user.s0_1[27]:'algebra.kunion' undefined in: _38:any := algebra.kunion(_24:bat[:oid,:int], _37:bat[:oid,:void])
!TypeException:user.s0_1[29]:'algebra.markT' undefined in: _41:any := algebra.markT(_38:any, _39:oid)
!TypeException:user.s0_1[30]:'bat.reverse' undefined in: _42:any := bat.reverse(_41:any)
!TypeException:user.s0_1[40]:'algebra.leftjoin' undefined in: _58:any := algebra.leftjoin(_42:any, _57:bat[:oid,:int], _59:lng)
!TypeException:user.s0_1[41]:'algebra.leftjoin' undefined in: _60:any := algebra.leftjoin(_42:any, _19:bat[:oid,:int], _59:lng)
!TypeException:user.s0_1[42]:'algebra.leftjoin' undefined in: _61:any := algebra.leftjoin(_42:any, _34:bat[:oid,:int], _59:lng)
!SQLException:SQLengine:Program contains errors
Expected result:
All rows that meet the condition field1 = 1 should be returned, and no rows that *only* meet the condition field2=1 are expected.
## Comment 12734
Date: 2009-11-11 16:47:15 +0100
From: Stephen Benz <<sbenz>>
Note, the following query does run successfully:
sql>select * from "simple" where field1 = 1 and (field2 = 1 or field1 = 1 or field2 = 2);
It appears this only functions when field1 occurs in the middle of the OR clause
## Comment 12735
Date: 2009-11-11 22:13:15 +0100
From: @njnes
added test and_and_or_type_exception.SF-2896012.sql
fixed bug by putting extra NULL projects around the selects which go into the union.
## Comment 12736
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2896012 at http://sourceforge.net/support/tracker.php?aid=2896012
| Filter using same field in OR and AND throws typeexception | https://api.github.com/repos/MonetDB/MonetDB/issues/2258/comments | 0 | 2020-11-30T10:33:45Z | 2024-06-27T11:42:48Z | https://github.com/MonetDB/MonetDB/issues/2258 | 753,358,321 | 2,258 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-11 09:55:20 +0100
From: Alex Bo <<alexbod>>
To: @njnes
Version: -- development
Last updated: 2009-11-15 10:40:42 +0100
## Comment 12729
Date: 2009-11-11 09:55:20 +0100
From: Alex Bo <<alexbod>>
(reproduced on Aug-SP1)
Create this table:
create table "table1" ("customer" varchar(40), "product" varchar(40), "price" double)
insert into "table1" values ('cust1', 'p1', 100)
insert into "table1" values ('cust1', 'p2', 200)
insert into "table1" values ('cust1', 'p3', 150)
insert into "table1" values ('cust2', 'p1', 300)
insert into "table1" values ('cust2', 'p3', 200)
Run this query:
SELECT "customer",
"product",
"sumprice",
(Row_number() OVER(PARTITION BY "customer" ORDER BY "sumprice")) as "rank"
FROM ( SELECT "customer",
"product",
(Sum("price")) AS "sumprice"
FROM "table1"
GROUP BY "customer",
"product") AS "temp"
It returns:
Returns:
Customer product sumprice rank
Cust1 p1 100 1
Cust1 p2 200 2
Cust1 p3 150 3
Cust2 p1 300 1
Cust2 p3 200 2
But it should return:
Customer product sumprice rank
Cust1 p1 100 1
Cust1 p3 150 2
Cust1 p2 200 3
Cust2 p3 200 1
Cust2 p1 200 2
## Comment 12730
Date: 2009-11-12 08:42:00 +0100
From: @njnes
added test to orderby_with_row_number.SF-2895791.sql
## Comment 12731
Date: 2009-11-15 22:40:42 +0100
From: @njnes
fixed by correctly ordering (and projecting back) the to be ranked (and ranked) column
## Comment 12732
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2895791 at http://sourceforge.net/support/tracker.php?aid=2895791
| ORDER BY with Row_number() return wrong results | https://api.github.com/repos/MonetDB/MonetDB/issues/2257/comments | 0 | 2020-11-30T10:33:42Z | 2024-06-27T11:42:47Z | https://github.com/MonetDB/MonetDB/issues/2257 | 753,358,271 | 2,257 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-10 07:53:49 +0100
From: @mlkersten
To: MonetDB5 devs <<bugs-monetdb5>>
Version: -- development
Last updated: 2010-05-04 22:04:37 +0200
## Comment 12727
Date: 2009-11-10 19:53:49 +0100
From: @mlkersten
The tests/by_Peter should be inspected and (partially) propagated to M5.
## Comment 12728
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2895396 at http://sourceforge.net/support/tracker.php?aid=2895396
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb5@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
## Comment 13993
Date: 2010-05-04 21:57:52 +0200
From: @mlkersten
The collection of tests are more or less programmed mini-applications, which
certainly should not be cast into MAL program. Given the stability of the GDK
on these tests (and with M5 still being tested) this propagation is declared void.
## Comment 13997
Date: 2010-05-04 22:04:37 +0200
From: @grobian
*** Bug #2259 has been marked as a duplicate of this bug. ***
| M5: propagation of M4 tests | https://api.github.com/repos/MonetDB/MonetDB/issues/2256/comments | 0 | 2020-11-30T10:33:38Z | 2024-06-28T07:25:31Z | https://github.com/MonetDB/MonetDB/issues/2256 | 753,358,223 | 2,256 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-10 05:02:47 +0100
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2009-11-16 12:40:52 +0100
## Comment 12722
Date: 2009-11-10 17:02:47 +0100
From: @grobian
(pegasus) fabian% debug_five
GNU gdb (Gentoo 7.0 p1) 7.0
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-pc-solaris2.11".
For bug reporting instructions, please see:
<http://bugs.gentoo.org/>...
Reading symbols from /export/scratch/stripe/fabian/monetdb/Nov2009/program-i86pc/bin/mserver5...done.
(gdb) r
Starting program: /export/scratch/stripe/fabian/monetdb/Nov2009/program-i86pc/bin/mserver5
[Thread debugging using libthread_db enabled]
[New Thread 1 (LWP 1)]
[New LWP 2 ]
MonetDB server v5.16.0, based on kernel v1.34.0
Serving database 'demo', using 1 thread
Compiled for x86_64-pc-solaris2.11/64bit with 64bit OIDs dynamically linked
Detected 2.000 GiB (2147020800 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /export/scratch/stripe/fabian/monetdb/Nov2009/program-i86pc/etc/monetdb5.conf)
[New LWP 3 ]
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>[New LWP 4 ]
[New Thread 4 (LWP 4)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4 (LWP 4)]
0xfffffd5de3218b82 in varGetProp (mb=0x16c01b8, var=0, prop=10)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_instruction.mx:3057
3057 for(i=0; i<v->propc; i++){
(gdb) p v
$1 = (VarPtr) 0x0
(gdb) q
A debugging session is active.
Inferior 1 [process 6277 ] will be killed.
Quit anyway? (y or n) y
(pegasus) fabian%
(pegasus:src/mal/Tests) fabian% $INSTALL_DIR/bin/mclient -lmal -i < tst019.mal
MAPI = monetdb@localhost:50000
QUERY = end welcome;
ERROR = !TypeException:user.welcome[3]:type mismatch void := str
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY =
ERROR = !Connection terminated
## Comment 12723
Date: 2009-11-16 10:56:42 +0100
From: @grobian
you have to run with -i flag (interactive) to trigger the bug, if you do it at once it doesn't crash indeed.
## Comment 12724
Date: 2009-11-16 10:57:31 +0100
From: @grobian
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 6 (LWP 6)]
0xfffffd5dd2c18b82 in varGetProp (mb=0x18c29a8, var=0, prop=10)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_instruction.mx:3057
3057 for(i=0; i<v->propc; i++){
(gdb) bt
0 0xfffffd5dd2c18b82 in varGetProp (mb=0x18c29a8, var=0, prop=10)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_instruction.mx:3057
1 0xfffffd5dc4a0a001 in MALoptimizer (c=0x6061d8)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/optimizer/opt_support.mx:701
2 0xfffffd5dd2c63066 in runPhase (c=0x6061d8, phase=2)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_scenario.mx:602
3 0xfffffd5dd2c6318f in runScenarioBody (c=0x6061d8)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_scenario.mx:641
4 0xfffffd5dd2c63387 in runScenario (c=0x6061d8)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_scenario.mx:672
5 0xfffffd5dd2c1f9a5 in MSserveClient (dummy=0x6061d8)
at /export/scratch/mirror/fabian/monetdb/Nov2009/five/src/mal/mal_session.mx:501
6 0xfffffd7fff1fae75 in _thrp_setup () from /lib/64/libc.so.1
7 0xfffffd7fff1fb130 in ?? () from /lib/64/libc.so.1
8 0x0000000000000000 in ?? ()
## Comment 12725
Date: 2009-11-16 12:40:51 +0100
From: @mlkersten
Obvious dereference through NULL.
No additional test needed.
## Comment 12726
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2895290 at http://sourceforge.net/support/tracker.php?aid=2895290
| M5: segfault for tst019 when run with mclient | https://api.github.com/repos/MonetDB/MonetDB/issues/2255/comments | 0 | 2020-11-30T10:33:34Z | 2024-06-28T07:25:31Z | https://github.com/MonetDB/MonetDB/issues/2255 | 753,358,180 | 2,255 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-10 01:13:35 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2009-11-10 04:41:24 +0100
## Comment 12719
Date: 2009-11-10 01:13:35 +0100
From: @drstmane
With "@include", Mx does not write any "line directives into the (C-) output file.
Consequently, tools like debuggers (e.g., gdb) or Coverity do point to incorrect source code lines for all .mx files that use @include (e.g., most of the C code of the M5 back-end).
A simple example:
========
$ cat x.mx
@f x
@c
x3
x4
@include y.mx
x6
x7
@include z.mx
x9
x10
@:zf@
x12
========
$ cat y.mx
y1
y2
========
$ cat z.mx
@= zf
z2
z3
@c
========
$ Mx -c x.mx
x.mx: ./x.c - not modified
========
The incorrect output
--------
$ cat x.c
line 3 "x.mx"
x3
x4
y1
y2
x6
x7
line 10 "x.mx"
x9
x10
line 10 "x.mx"
z2
z3
line 12 "x.mx"
x12
========
Diff between incorrect (left) and correct/expected (right) output.
--------
$ diff -y -W30 x.c x.c.expected
line 3 "x.mx line 3 "x.mx
x3 x3
x4 x4
> line 1 "y.mx
y1 y1
y2 y2
> line 6 "x.mx
x6 x6
x7 x7
line 10 "x.m | line 9 "x.mx
x9 x9
x10 x10
line 10 "x.m | line 2 "z.mx
z2 z2
z3 z3
line 12 "x.m | line 11 "x.m
x12 x12
========
I tried to fix this, but turned out not to be familiar enough with the Mx code to do it "quickly".
Hence, this report to document the status until I (or someone else) manages to fix this.
## Comment 12720
Date: 2009-11-10 16:41:17 +0100
From: @drstmane
Given the code base of Mx and the way it handles @include commands (very differently than all other @-commands), I'm more than satisfied with Sjoerd's fix:
===================================================================
2009/11/10 - sjoerd: buildtools/Mx/Def.c,1.9.8.1 buildtools/Mx/Io.c,1.11.8.2
buildtools/Mx/Mx.c,1.10.8.1 buildtools/Mx/MxFcnDef.h,1.8.8.1
Deal better with @include.
To get the best results, an included file should start with a "block" (@-command), and after the @include should also come a new "block" (@ command).
===================================================================
## Comment 12721
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2894927 at http://sourceforge.net/support/tracker.php?aid=2894927
| Mx: @include does not write any "#line" directives | https://api.github.com/repos/MonetDB/MonetDB/issues/2254/comments | 0 | 2020-11-30T10:33:31Z | 2024-06-27T11:42:44Z | https://github.com/MonetDB/MonetDB/issues/2254 | 753,358,147 | 2,254 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-09 02:58:11 +0100
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2009-11-09 03:31:04 +0100
## Comment 12716
Date: 2009-11-09 14:58:11 +0100
From: @swingbit
In http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/Document-Management-Functions.html
pf:delete-doc ($name as xs:string)
should be
pf:del-doc ($name as xs:string)
## Comment 12717
Date: 2009-11-09 15:30:56 +0100
From: @sjoerdmullender
Fixed in CVS. This will be on the web site after it is regenerated (whenever that will be ;-) ).
## Comment 12718
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2894560 at http://sourceforge.net/support/tracker.php?aid=2894560
| pf:delete-doc is pf:del-doc | https://api.github.com/repos/MonetDB/MonetDB/issues/2253/comments | 0 | 2020-11-30T10:33:28Z | 2024-06-27T11:42:43Z | https://github.com/MonetDB/MonetDB/issues/2253 | 753,358,100 | 2,253 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-08 03:19:16 +0100
From: @drstmane
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-11-14 10:24:09 +0100
## Comment 12709
Date: 2009-11-08 15:19:16 +0100
From: @drstmane
Since late August / early September, the perl_dbi (and possibly more yet undiscovered) tests fail due to a change in the error message formatting (or even "protocol"?), i.e., the leading '!' seems to have been removed (at least in some cases), possibly only in MAPI or some client interface?
Cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/tests_mapi_examples_C/perl_dbi.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora10/tests_mapi/perl_dbi.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/perl_dbi.out.00.html
I could not easily find the related checkin(s), but maybe some recalls what happened?
In case these changes (and their effects/consequences) are intended, we should approve all test results that are affected according.
In case these changes (and/or their effects/consequences) are not intended, we should refine the changes.
## Comment 12710
Date: 2009-11-08 15:22:28 +0100
From: @grobian
it's only libmapi that no longer returns the leading bangs, but I'm confused why perl is affected by that, is it swig generated or something?
## Comment 12711
Date: 2009-11-08 15:24:54 +0100
From: @drstmane
yes, we only have swig-generated perl so far ...
## Comment 12712
Date: 2009-11-08 15:29:13 +0100
From: @grobian
ah...
then we can simply approve this
## Comment 12713
Date: 2009-11-09 09:26:46 +0100
From: @drstmane
I approved the output for the perl_dbi tests --- we'll need to check, whether there are more tests that need to have their new output w/o "!" approved ...
## Comment 12714
Date: 2009-11-14 22:24:09 +0100
From: @drstmane
Except from systems where perl DBI is not available, these tests work fine, again.
Closing.
## Comment 12715
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2894150 at http://sourceforge.net/support/tracker.php?aid=2894150
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.
| test fail due to error message format/protocol changes | https://api.github.com/repos/MonetDB/MonetDB/issues/2252/comments | 0 | 2020-11-30T10:33:24Z | 2024-06-27T11:42:42Z | https://github.com/MonetDB/MonetDB/issues/2252 | 753,358,046 | 2,252 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 05:37:59 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2009-11-14 10:22:27 +0100
## Comment 12701
Date: 2009-11-07 17:37:59 +0100
From: @drstmane
[running out of time, for now; hence, a cumulative report to document the remaining once]
in addition to the earlier individually reported SQL tests, also the following SQL tests fail with Nov2009 while they work(ed) fine with Aug2009:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/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-Fedora10/src_test_BugTracker-2009/function_call_not_handled.SF-2864179.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Connections/connections.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Connections/connections.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_bugs/insert_update_arith-bug-sf-900206.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_bugs/insert_update_arith-bug-sf-900206.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_copy/load_incorrect_line_nr.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Gentoo2.0.1/src_test_mapi/perl_dbi.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/check0.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/check1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/check2.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/check3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/temp3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/drop3.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/check4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/check5.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/select1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_leaks/select2.out.00.html
## Comment 12702
Date: 2009-11-10 09:57:11 +0100
From: @drstmane
Update:
Niels approved the new output for all tests in sql/test/leaks/Tests/
Fabian and I approved the new output for sql/src/test/mapi/Tests/.*perl_dbi (cf. https://sourceforge.net/tracker/index.php?func=detail&aid=2894150&group_id=56967&atid=482468)
The following tests appear to be fixed, probably due to Niels' recent checkins:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64
.64.d.1-Fedora10/src_test_bugs/insert_update_arith-bug-sf-900206.err.00.htm
lhttp://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64
.64.d.1-Fedora10/src_test_bugs/insert_update_arith-bug-sf-900206.out.00.htm
l
Martin approved the new output for http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugDay_2005-11-09_2.9.3/hang_on_copy_into.SF-1100504.err.00.html
The remaining tests still fail:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/function_call_not_handled.SF-2864179.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Connections/connections.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Connections/connections.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_copy/load_incorrect_line_nr.err.00.html
## Comment 12703
Date: 2009-11-10 10:00:50 +0100
From: @drstmane
Update 2:
After checkins on Sunday Nov 8 & Monday Nov 9, the following tests fail:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_odbc_samples/odbcsample1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/parallel_bulk-load.SF-2771052.test.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/parallel_bulk-load.SF-2771052.test.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_dbapi.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_jdbc_tests/Test_Creplysize.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_jdbc_tests/Test_Creplysize.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_VOC/VOC.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_test_monetdb_sql_dbapi20.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_test_monetdb_sql_capabilities.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/explain.SF-1739353.out.00.html
## Comment 12704
Date: 2009-11-10 14:28:09 +0100
From: @drstmane
Update 3:
Fixed
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_odbc_samples/odbcsample1.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_dbapi.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_test_monetdb_sql_dbapi20.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_test_monetdb_sql_capabilities.err.00.html
by undoing
===================================================================
2009/11/08 - mlkersten: sql/src/backends/monet5/sql_result.mx,1.127.2.2
Handling og Coverty complaints.
===================================================================
Fixing Coverity-detected problems must not invalidate code correctness.
## Comment 12705
Date: 2009-11-10 15:29:58 +0100
From: @drstmane
Update 3a:
undoing
===================================================================
2009/11/08 - mlkersten: sql/src/backends/monet5/sql_result.mx,1.127.2.2
Handling og Coverty complaints.
===================================================================
also fixed
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_jdbc_tests/Test_Creplysize.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_jdbc_tests/Test_Creplysize.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_VOC/VOC.out.00.html
## Comment 12706
Date: 2009-11-10 20:24:04 +0100
From: @drstmane
Update 3b:
fixed
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/explain.SF-1739353.out.00.html
by approving the new output
## Comment 12707
Date: 2009-11-14 22:22:27 +0100
From: @drstmane
In general, all tests work fine, again.
Some system-specific issues need to be analyzed and solved separately.
Closing.
## Comment 12708
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893878 at http://sourceforge.net/support/tracker.php?aid=2893878
| SQL: more tests fail with Nov2009 that worked with Aug2009 | https://api.github.com/repos/MonetDB/MonetDB/issues/2251/comments | 0 | 2020-11-30T10:33:21Z | 2024-06-27T11:42:41Z | https://github.com/MonetDB/MonetDB/issues/2251 | 753,358,004 | 2,251 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 05:19:26 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-11-18 10:43:47 +0100
## Comment 12688
Date: 2009-11-07 17:19:26 +0100
From: @drstmane
The following 82 tests work(ed) fine with the Aug2009 branch,
but appear to fail with the Aug2009 branch,
and hence most probaly also with the Nov2009 branch
(which is currently even more instable wrt. testing for yet undiscovered reasons):
benchmarks/MBench/qa05
benchmarks/MBench/
benchmarks/XBench/DC/MD/q19
benchmarks/XBench/DC/MD/
modules/pftijah/procs
modules/pftijah/colltest1
modules/pftijah/colltest2
modules/pftijah/
runtime/xrpc/admin/add_del_doc_noxrpc
runtime/xrpc/admin/backup_restore_noxrpc
runtime/xrpc/admin/
tests/BugTracker/treat_as.SF-1586454
tests/BugTracker/insert_multiple.SF-1590580
tests/BugTracker/inserting_multiple_elements.SF-1590583
tests/BugTracker/insert_into_transient.SF-1626208
tests/BugTracker/clear_attrs_on_delete.SF-1612739
tests/BugTracker/clear_attrs_on_delete.SF-1612739-b
tests/BugTracker/clear_attrs_on_delete.SF-1612739-c
tests/BugTracker/corrupt_after_update.SF-1706640
tests/BugTracker/accessing_renamed_inserted_deleted_node.SF-1718622-1718635-1718709
tests/BugTracker/insert_large_doc.SF-1726954
tests/BugTracker/replace-corrupts.SF-1758902
tests/BugTracker/swizzle-bug.SF-1760811
tests/BugTracker/swizzle-http://sourceforge.net/support/tracker.php?aid=2.SF-1763495
tests/BugTracker/insert_attribute_gives_ERROR_in_merged_union.SF-1763575
tests/BugTracker/immune_for_updates.SF-1766259
tests/BugTracker/repeated-insert.SF-1814911
tests/BugTracker/insert-new-page.SF-1854215
tests/BugTracker/immune_for_updates.SF-1981852
tests/BugTracker/hang_non_existing_doc.SF-1911209
tests/BugTracker/function_parameter_without_type.SF-1898518
tests/BugTracker/copybug.SF-2642003
tests/BugTracker/update-with-timing.SF-2852928
tests/BugTracker/compilation_error.SF-2860574_1
tests/BugTracker/compilation_error.SF-2860574_2
tests/BugsViaSourgeforce/invisible_error_messages.SF-1409122
tests/BugsViaSourgeforce/
tests/StandOff/update/basic_insert
tests/StandOff/update/basic_test
tests/StandOff/update/
tests/Update/setattr-1
tests/Update/insert-1
tests/Update/insert-2
tests/Update/symm
tests/Update/replacevaluetest
tests/Update/replacevaluetest2
tests/Update/update
tests/Update/illegal-insert
tests/Update/illegal-delete
tests/Update/insert_test_order
tests/Update/insert_test_order_seq
tests/Update/replacenode-corruption.SF-2153245
tests/W3C_use_cases/XQUF/AddressBook/Q1x
tests/W3C_use_cases/XQUF/AddressBook/check_docs
tests/W3C_use_cases/XQUF/AddressBook/
tests/W3C_use_cases/XQUF/Parts/Q1
tests/W3C_use_cases/XQUF/Parts/Q2
tests/W3C_use_cases/XQUF/Parts/Q3a1
tests/W3C_use_cases/XQUF/Parts/Q3a2
tests/W3C_use_cases/XQUF/Parts/Q4a
tests/W3C_use_cases/XQUF/Parts/Q4ax
tests/W3C_use_cases/XQUF/Parts/Q4b
tests/W3C_use_cases/XQUF/Parts/Q4bx
tests/W3C_use_cases/XQUF/Parts/Q4c
tests/W3C_use_cases/XQUF/Parts/Q4cx
tests/W3C_use_cases/XQUF/Parts/Q6
tests/W3C_use_cases/XQUF/Parts/Q6x
tests/W3C_use_cases/XQUF/Parts/
tests/W3C_use_cases/XQUF/R/Q1
tests/W3C_use_cases/XQUF/R/Q2
tests/W3C_use_cases/XQUF/R/Q3
tests/W3C_use_cases/XQUF/R/Q4
tests/W3C_use_cases/XQUF/R/Q4x
tests/W3C_use_cases/XQUF/R/Q5b
tests/W3C_use_cases/XQUF/R/Q6a
tests/W3C_use_cases/XQUF/R/Q6b
tests/W3C_use_cases/XQUF/R/Q7
tests/W3C_use_cases/XQUF/R/Q7x
tests/W3C_use_cases/XQUF/R/Q8
tests/W3C_use_cases/XQUF/R/Q9
tests/XQuery/is-before4
tests/XQuery/union
## Comment 12689
Date: 2009-11-08 16:50:24 +0100
From: @drstmane
For completeness:
I checked this on my 64-bit Fedora 10 Linux desktop, using a "testing" build of MonetDB, i.e., configured with --disbale-debug --enable-optimize --enable-assert .
I ran Mtest.py (more precisely make check, respectively RunMtest in the build directory) seperately for the Aug2009 and the Aug2009_NFI brach (builds) of pathfinder, collected the console output in files, and run diff over those (as well as over the times.sql files that Mtest.py creates in its <TSTTRGBASE> directory.
## Comment 12690
Date: 2009-11-08 18:13:06 +0100
From: @drstmane
The same test that fail with Aug2009_NFI, while working with Aug2009, indeed also fail with Nov2009.
## Comment 12691
Date: 2009-11-11 11:45:34 +0100
From: @peterboncz
Thanks. I looked into this and fixed a problem with XQuery updates that indeed was present. This will reduce the amount of problems, removing (almost) all of those tests that are XQuery updates from the list.
The update bug was caused by a later modification that succeeded my own check of the testweb that I performed before checking in the code. At that time, already, I found it very hard to work with the test web. Note, this is not a complaint to anyone in particular. However a matter of fact. Simply too many tests fail, such that one is forced to spend an hour just to compare the state of the testweb before and after a check-in, to detect which of the tests that fail were actually already failing before the check-in. Let alone analyze what is happening.
my suggestons are as follows:
(1) approve output:
- tests/BugTracker/empty_file.SF-2017862: SunOS specific version only!!
- tests/BugTracker/XML_document_cache_broken.SF-1414720
- tests/W3C_use_cases/XQ/NS/* (or remove tests!)
- tests/XQuery/{div.is-before4,union}
- tests/BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516
- tests/BugDay_2005-12-19_0.9.3/shred_doc_with_space.SF-1211372: windows only
- tests/clients/php_monetdb
- runtime/procs/approve
- modules/pftijah/{load,sigs,procs}
- tests/BugsViaSourgeforce/{invisible_error_messages.SF-1409122,ID.1766173}
(2) remove or disable the following tests, which seem incorrect or outdated:
- tests/BugTracker/xs_untypedAtomic.SF-1509806.mps
- tests/BugTracker/Zombie_document.SF-2009556
- tests/BugTracker/function_parameter_without_type.SF-1898518
- tests/BugTracker/fn-root_fn-id_on_attribute_nodes.SF-1
- tests/BugTracker/975028,non-existing_collection.SF-1991726
- tests/BugTracker/port_busy.SF-1809586
- tests/BugTracker/collection_management
- tests/BugDay_2005-12-19_0.9.3/multiple_servers_2.SF-1385152
- runtime/smack
- benchmarks/mbench/{qa02,qa06} are now only run for Darwin9.8.0 G.32.32.d.1 -- should also set NOT_ALGEBRA for this platform
(3) ask Jennie to look at the following tests in runtime/xrpc/admin/:
- add_del_doc_norpc: approve?
- backup_restore_xrpc: empty, check this pls??
(4) ask Jan Flokstra to look at the following tests in modules/pftijah/:
- coltest1 hang
- test_lms-or: order
- test_lms_rmoverlap, test_select_start*: empty
(5) adapt or disable these test scripts to work on windows:
- tests/BugDay_2005-12-19_0.9.3/file_locked_after_shredding.SF-1238352 (windows6 only) -
- tests/BugDay_2005-12-19_0.9.3/shredding_on_the_fly.SF-1377006: idem
- tests/BugTracker/predicate_selects_too_few_nodes.SF-1636588 - windows fails to parse, because of Mtest substitution failure (for $v becomes for 4)
(6) ignore output of tests (possibly for certain platforms only), as these are system limits related (too deep recursion):
- tests/BugTracker/crash_on_concatenated_query.SF-1730547 - for all systems
- tests/BugTracker/server-side_compilation_crash.SF-1607210 - for all systems
- tests/BugsViaSourgeforce/ID.1015172{a,b,c}: timeout on windows5 (windows6 works)
- tests/XQuery/step_attr_nametest: Darwin9.8.0 G.32.32.d too deep recursion,
- tests/XQuery/typeswitch3 - too deep recursion on various systems..
- tests/BugDay_2005-11-09_0.9.3/xquery_crashtest.SF-1207048: pf recursion check not triggered on Fedora10 G.32.32.d.1
what will be left, then
=======================
The only problems that will be left after following the above are in fact problems that occur only on a single system.
Rather than indicating a platform deficiency, however, it is still very likely that these differences indicate the
precense of a bug, that is only triggered under certain circumstances that happen to hold on that platform.
so these are interesting to look at; all of them were already present in the last Stable
Fedora10.G.64.64.d.0 - merge_union2: non dense head
- tests/XQuery/merge_union2
Fedora10 G.64.64.d.0 - crash
- tests/XQuery/step_attribute8,
Fedora10 I.64.64.d.1: crash
- tests/XQuery/orderby6
Fedora10 G.64.64.s.1 - crash
- tests/XQuery/step_descendant-or-self3
Fedora10.G.32.32.d.1 -- segmentation fault
- xbench/tc/md/q10
- tests/W3C_use_cases/XQ/XMP/Q07
windows - !ERROR: couldn't read name (1000000152_qn_uri) 1
- tests/BugTracker/32_docs.SF-1730617:
sunos5 g32.32.d.1 - segmentation fault
- mbench/{qs28,31}
- tests/XQuery/{step_duplicates,transient_upward_steps}
- benchmarks/XPathMark/{Q27,28}
- benchmarks/XPath/q13
- benchmarks/XMark/q04
- tests/XQuery/step_attr_nametest (also on Darwin9.8.0 G.32.32.d.1)
sunos5 g32.32.d.1 - 4 times inserted nil due to errors at tuples 0, 1, 2, 3
- tests/BugTracker/child-steps-and-replace.SF-2716723:
Debian4.0 G.32.32.d.1 - !fatal error: columns referenced in trace message operator not found
- tests/BugTracker/fn-trace.SF-2805513 (also Gentoo2.0.1 G.64.64.d.1)
## Comment 12692
Date: 2009-11-15 13:57:58 +0100
From: @drstmane
below the details what I did so far:
> - tests/BugTracker/empty_file.SF-2017862: SunOS specific version only!!
approved.
> - tests/BugTracker/XML_document_cache_broken.SF-1414720
approved.
> - tests/W3C_use_cases/XQ/NS/* (or remove tests!)
disabled.
> - tests/XQuery/{div.is-before4,union}
div:
approved MIL error messages iso. XQuery error message
is-before4, union:
nothing, as I'm not sure, whether the new output is correct.
Since the NFI change were propagated to the Nov2009 branch on Oct 7,
these tests show again the output as it was before
===================================================================
2009/05/20 - tsheyar:
pathfinder/tests/XQuery/Tests/is-before4.stable.out,1.5.30.1
pathfinder/tests/XQuery/Tests/union.stable.out,1.6.12.1
-- Make the error message for missing documents more informative:
Include the document name in the error message.
-- Adjust new error messages in the testweb.
-- Adjust stable output (for tests with a modified inter-document order).
-- Fix/Extend a cross product rewrite (for unreferenced inputs).
-- Simplify the 'missing document' error message in the algebra
for constant document names (which is the default).
===================================================================
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_XQuery/is-before4.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_XQuery/union.out.00.html
Peter and/or Jan R., could you please comment?
> - tests/BugDay_2005-12-19_0.9.3/attribute_after_non-attribute_content.SF-1351516
disabled.
> - tests/BugDay_2005-12-19_0.9.3/shred_doc_with_space.SF-1211372: windows only
minor --- either approve or change access rights on Windows machine:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/Int.64.32.d.1-Windows6.0/tests_BugDay_2005-12-19_0.9.3/shred_doc_with_space.SF-1211372.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/Int.64.64.d.1-Windows6.0/tests_BugDay_2005-12-19_0.9.3/shred_doc_with_space.SF-1211372.out.00.html
> - tests/clients/php_monetdb
fixed.
> - runtime/procs/approve
approved.
> - modules/pftijah/{load,sigs,procs}
approved.
> - tests/BugsViaSourgeforce/{invisible_error_messages.SF-1409122,ID.1766173}
approved.
> (2) remove or disable the following tests, which seem incorrect or outdated:
> - tests/BugTracker/xs_untypedAtomic.SF-1509806.mps
disabled.
> - tests/BugTracker/Zombie_document.SF-2009556
Nothing yet; we get a timeout:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Zombie_document.SF-2009556.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/Zombie_document.SF-2009556.err.00.html
> - tests/BugTracker/function_parameter_without_type.SF-1898518
approved.
> - tests/BugTracker/fn-root_fn-id_on_attribute_nodes.SF-1
disabled.
> - tests/BugTracker/975028,non-existing_collection.SF-1991726
approved.
> - tests/BugTracker/port_busy.SF-1809586
Nothing, yet; output might actually be OK / as expected:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/port_busy.SF-1809586.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/port_busy.SF-1809586.err.00.html
> - tests/BugTracker/collection_management
Nothing, yet; need to understand what's (supposed to be) going on:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/collection_management.SF-1726599.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_BugTracker/collection_management.SF-1726599.err.00.html
> - tests/BugDay_2005-12-19_0.9.3/multiple_servers_2.SF-1385152
fixed.
> - runtime/smack
Nothing, yet; smack00 test works fine for MIL, MAL, SQL, but never worked
(timout: hangs "forever") for XQuery
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/runtime/smack00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/runtime/smack00.err.00.html
> - benchmarks/mbench/{qa02,qa06} are now only run for Darwin9.8.0 G.32.32.d.1
> -- should also set NOT_ALGEBRA for this platform
these are (and have been) skipped with Algebra on all platforms.
> (3) ask Jennie to look at the following tests in runtime/xrpc/admin/:
> - add_del_doc_norpc: approve?
> - backup_restore_xrpc: empty, check this pls??
Since 12.11., these now fail with
ERROR = !module import: error loading module from http://$HOST:47966/admin/admin.xq
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/runtime_xrpc_admin/add_del_doc_noxrpc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/runtime_xrpc_admin/backup_restore_noxrpc.err.00.html
> (4) ask Jan Flokstra to look at the following tests in modules/pftijah/:
> - coltest1 hang
> - test_lms-or: order
> - test_lms_rmoverlap, test_select_start*: empty
fixed by Sjoerd's backport of Hennigs fixes from the head to the Nov2009 branch
> (5) adapt or disable these test scripts to work on windows:
> - tests/BugDay_2005-12-19_0.9.3/file_locked_after_shredding.SF-1238352
> (windows6 only) -
> - tests/BugDay_2005-12-19_0.9.3/shredding_on_the_fly.SF-1377006: idem
> - tests/BugTracker/predicate_selects_too_few_nodes.SF-1636588 - windows fails
> to parse, because of Mtest substitution failure (for $v becomes for 4)
fixed by Sjoerd.
> (6) ignore output of tests (possibly for certain platforms only), as these are
> system limits related (too deep recursion):
> - tests/BugTracker/crash_on_concatenated_query.SF-1730547 - for all systems
> - tests/BugTracker/server-side_compilation_crash.SF-1607210 - for all systems
> - tests/BugsViaSourgeforce/ID.1015172{a,b,c}: timeout on windows5 (windows6
> works)
> - tests/XQuery/step_attr_nametest: Darwin9.8.0 G.32.32.d too deep recursion,
> - tests/XQuery/typeswitch3 - too deep recursion on various systems..
> - tests/BugDay_2005-11-09_0.9.3/xquery_crashtest.SF-1207048: pf recursion
> check not triggered on Fedora10 G.32.32.d.1
to be done ...
didn't get further than here, so far ...
Stefan
## Comment 12693
Date: 2009-11-16 15:28:56 +0100
From: @drstmane
Peter,
the two "crucial" problems remaining (which both started on the Nov2009 branch after propagations of NFI changes from the Aug2009_NFI branch to the Nov2009 branch) are
timeout in
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/benchmarks_MBench/qa05.err.00.html
(since 2009.10.09)
missing updates in
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora10/tests_Update/update.out.00.html
(since 2009.10.08)
They might actually be missing, because the query parts of the update queries involving an attribute predicate yield an empty result.
The missing updates are
for $elem in $testdoc/document/element[@attribute = 50]
return do rename exactly-one($elem) into "Element"
for $elem in $testdoc/document/element[@attribute = 10]
return (do insert <a/> as first into exactly-one($elem) treat as element(),
do insert <b/> as first into exactly-one($elem) treat as element())
for $elem in $testdoc/document/element[@attribute = 20]
return (do insert <a/> as last into exactly-one($elem) treat as element(),
do insert <b/> as last into exactly-one($elem) treat as element())
for $elem in $testdoc/document/element[@attribute = 30]
return (do insert <a/> before exactly-one($elem),
do insert <b/> before exactly-one($elem))
for $elem in $testdoc/document/element[@attribute = 40]
return (do insert <a/> after exactly-one($elem),
do insert <b/> after exactly-one($elem))
## Comment 12694
Date: 2009-11-16 15:42:59 +0100
From: @sjoerdmullender
This is a show stopper.
## Comment 12695
Date: 2009-11-16 18:42:39 +0100
From: Jan Rittinger <<jan.rittinger>>
In MBench/qa05 Peter's heuristic rewrite leads to an (unnecessary) cross product. (For all eNest nodes it applies pf:attribute.) I guess that might be the problem.
## Comment 12696
Date: 2009-11-17 00:32:01 +0100
From: @peterboncz
both problems are fixed now
I did spot in tests/Update/insert_test_order_seq
another instance of differences accross all platforms.
The test is a little vauge, inserting a sequence of values; I am not sure what the XQUF semantics says about this. Is the order implementation-dependent? This this order might also be ok and the test could be approved.
## Comment 12697
Date: 2009-11-17 10:05:23 +0100
From: @drstmane
Thanks, Peter!
Your checkins were "too late" for last night's (this morning's) testing,
but local testing shows pathfinder/benchmarks/MBench/Tests/qa05.* and pathfinder/tests/Update/Tests/update.* working fine, again.
I already
Can be closed once confirmed by nightly testing.
(For now, system-specific problems are also documented in the TestWeb, and should be handled later; they're not considered crucial for the upcoming release.)
## Comment 12698
Date: 2009-11-17 10:08:36 +0100
From: @drstmane
forgot to finish:
"I already" ...
... approved ALG-specific output of the insert-order test on Lefteris' advice and closed the bug report:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1964365&group_id=56967
## Comment 12699
Date: 2009-11-18 10:43:47 +0100
From: @drstmane
confirmed.
closing.
## Comment 12700
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893875 at http://sourceforge.net/support/tracker.php?aid=2893875
| PF: 82 tests fail on Auf2009_NFI/Nov2009 but work on Aug2009 | https://api.github.com/repos/MonetDB/MonetDB/issues/2250/comments | 0 | 2020-11-30T10:30:20Z | 2024-06-27T11:42:40Z | https://github.com/MonetDB/MonetDB/issues/2250 | 753,355,819 | 2,250 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 04:29:07 +0100
From: @drstmane
To: Arjen de Rijke <<arjen.de.rijke>>
Version: -- development
Last updated: 2009-11-17 09:38:54 +0100
## Comment 12679
Date: 2009-11-07 16:29:07 +0100
From: @drstmane
Arjen, could you please check, whether the stable output is indeed correct?
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Via-m/media_s14.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Via-m/media_s16.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Via-m/media_s18.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Via-m/media_s19.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Via-m/file_s10.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_Via-m/file_s18.out.00.html
## Comment 12680
Date: 2009-11-14 10:26:36 +0100
From: @drstmane
The first 5 of the reported 6 tests seem to fail again (or still) with nightly Stable testing.
A small analysis reveals, that they fail only with assertions disabled (as with nightly Stable testing and in the "production" release), but work fine with assertions enabled.
The "failure" (i.e., difference) seems to be that with assertion enabled, the default value of a non-initialized variable is -606348325, while with assertions disabled, either the value is 0, or a failing function unexpectedly triggers an 0-assignment of its return value to that variable.
In case it's the former (i.e., different default value for non-initialized variables), and the SQL standard does not specify the default value of a non-initialized variable, I'd propose to make these tests deterministic by initializing the respective variable to a value that the function cannot return, and approve the stable output accordingly.
## Comment 12681
Date: 2009-11-16 09:49:07 +0100
From: @arjenderijke
The stable output is what i now expect it to be, whether it is correct is still debated. I already approved the stable output of these tests in the Nov2009 branch, my suggestion is to do the same for the stable branch. Than we can continue the discussion after the release. That has become more complicated now it appears that assertions are involved.
## Comment 12682
Date: 2009-11-16 09:59:19 +0100
From: @drstmane
FYI:
The Nov2009 branch is (used as / referred to as) the "Stable" branch.
## Comment 12683
Date: 2009-11-16 10:07:36 +0100
From: @drstmane
Since the purpose of these tests is not to test the default value of non-initialized variables, I see no reason not to simply make them deterministic in any case by explicitly initializing the variables.
If the default value of non-initialized variables is indeed an issue, I propose to add a separate test for that, e.g., as simple as
declare MyVar integer;
select MyVar;
## Comment 12684
Date: 2009-11-16 10:54:45 +0100
From: @arjenderijke
I did not known/realize that the Nov2009 already was the stable branch. The default value of non-initialized is a point for discussion, but for now we can make the tests deterministic. I will change the tests accordingly.
## Comment 12685
Date: 2009-11-16 21:42:41 +0100
From: @drstmane
I initialized non-initialized (integer) variables to -1234567890.
Report can be closed once nightly testing confirms the fix.
## Comment 12686
Date: 2009-11-17 09:38:39 +0100
From: @drstmane
Ok.
Closing.
## Comment 12687
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893859 at http://sourceforge.net/support/tracker.php?aid=2893859
| SQL: various VIA-M tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/2249/comments | 0 | 2020-11-30T10:30:17Z | 2024-06-27T11:42:39Z | https://github.com/MonetDB/MonetDB/issues/2249 | 753,355,787 | 2,249 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 03:56:57 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-11-10 09:49:05 +0100
## Comment 12676
Date: 2009-11-07 15:56:57 +0100
From: @drstmane
test sql/src/test/BugTracker-2009/Tests/set_history_and_drop_table.SF-2607045 fails as follows since 2009/10/26, i.e., after checkins on 2009/10/25 on the Nov2009 branch:
QUERY = set history='true';
select id from tables where id > 0;
create table t1 (id int);
drop table t1;
ERROR = !Variable history unknown
Has the hstoriy variable been removed?
I can't derive this from the cvs logs:
===================================================================
2009/10/25 - mlkersten: MonetDB5/src/mal/mal_instruction.mx,1.397.2.2
MonetDB5/src/mal/mal_interpreter.mx,1.319.2.2
MonetDB5/src/mal/mal_profiler.mx,1.132.4.3
MonetDB5/src/mal/mal_recycle.mx,1.196.2.1
MonetDB5/src/mal/mal_utils.mx,1.19.4.1
MonetDB5/src/mal/Tests/tst009.mal,1.3.24.1
MonetDB5/src/mal/Tests/tst274.mal,1.6.20.1
MonetDB5/src/mal/Tests/tst274.stable.out.oid64,1.9.8.1
MonetDB5/src/modules/mal/language.mx,1.86.6.1
MonetDB5/src/modules/mal/profiler.mx,1.63.6.3
MonetDB5/src/modules/mal/recycle.mx,1.66.2.1
MonetDB5/src/modules/mal/trader.mx,1.6.2.1
MonetDB5/src/tools/stethoscope.mx,1.38.4.1
More fixes to the performance profiler. The number of properties maintained
for off-line inspection has been increased. The naming of the properties
has been made more precise, avoiding combos.
===================================================================
2009/10/25 - mlkersten: sql/src/backends/monet5/sql_scenario.mx,1.356.2.5
Introduce the trace global variable. Allow for keeping the result of
a traced call for querying as if it was a SQL table.[todo]
===================================================================
2009/10/25 - mlkersten: MonetDB5/src/mal/mal_profiler.mx,1.132.4.4
And make the profile information accessible from SQL.
===================================================================
2009/10/25 - mlkersten: sql/src/backends/monet5/sql.mx,1.358.2.6
sql/src/backends/monet5/sql_scenario.mx,1.356.2.6
Make the profile information accessible for inspection using SQL.
===================================================================
## Comment 12677
Date: 2009-11-10 09:49:03 +0100
From: @drstmane
fixed by
===================================================================
2009/11/08 - nielsnes: sql/src/backends/monet5/sql_scenario.mx,1.356.2.13
there are 9 global variables now
===================================================================
closing.
## Comment 12678
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893846 at http://sourceforge.net/support/tracker.php?aid=2893846
| SQL: set_history_and_drop_table.SF-2607045 fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2248/comments | 0 | 2020-11-30T10:30:14Z | 2024-06-27T11:42:38Z | https://github.com/MonetDB/MonetDB/issues/2248 | 753,355,750 | 2,248 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 02:47:10 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-11-15 05:02:18 +0100
## Comment 12668
Date: 2009-11-07 14:47:10 +0100
From: @drstmane
cf.;
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_backends_monet5/optimizers.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_backends_monet5/optimizers.err.00.html
## Comment 12669
Date: 2009-11-07 15:47:24 +0100
From: @mlkersten
The accumulator optimizer is running for several weeks.
This test output can be approved unless at the latest moment we drop this optimizer from the default pipeline.
## Comment 12670
Date: 2009-11-07 16:45:49 +0100
From: @drstmane
Are the extra/new error messages also related to the accumulator optimizer?
Or due to different / strikter checking of the optimizer pipeline?
Are the errors correct and as expected?
If so, we could approve at least those (unless they are due to change, too).
## Comment 12671
Date: 2009-11-07 17:21:22 +0100
From: @mlkersten
The new optimizer validator indeed generates error messages. This file can be approved upon release.
## Comment 12672
Date: 2009-11-09 14:53:57 +0100
From: @drstmane
After Niels disabled the accumulator optimizer
(cf.,
2009/11/09 - nielsnes: MonetDB5/conf/monetdb5.conf.in,1.67.2.7
stricter checkin of view or parent of view in batcalc accumulator code.
Still this is not enough because of concurrency, therefor we switch of
the accumulator optimizer (again)
)
I approved the stable out and stable err to the best of my knowledge as follows
===================================================================
2009/11/09 - stmane:
sql/src/backends/monet5/Tests/optimizers.stable.out,1.10.4.1
approved stable output according to
"
2009/09/04 - mlkersten: MonetDB5/conf/monetdb5.conf.in,1.62
Add the minimal plan for testing its behavior.
Add the replication plan for the near future.
"
i.e., the cluster optimizer was removed from the default optimizer pipeline
===================================================================
2009/11/09 - stmane:
sql/src/backends/monet5/Tests/optimizers.stable.err,1.5.4.1
approved stable error output as I would expect it given the test
===================================================================
We need to monitor nightly testing results to see whether this is OK, or not ...
## Comment 12673
Date: 2009-11-10 09:43:29 +0100
From: @drstmane
For the records:
The fact that the query quotes/echos in error messages in optimizers.stable.err are "off by one" has been accepted and approved by
===================================================================
2009/11/09 - mlkersten:
sql/src/backends/monet5/Tests/optimizers.stable.err,1.5.4.2
Approve after resetting the accumulator pipeline.
===================================================================
## Comment 12674
Date: 2009-11-15 17:02:18 +0100
From: @mlkersten
When you set the SQL optimizer variable, then only at the next instruction it became active and was checked. Included an explicit test when the variable is assigned a new value. Thereby immediately
reporting on the error. [checkin follow]
Closing the report.
## Comment 12675
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893823 at http://sourceforge.net/support/tracker.php?aid=2893823
| SQL: src/backends/monet5/Tests/optimizers.sql fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2247/comments | 0 | 2020-11-30T10:30:10Z | 2024-06-28T07:25:30Z | https://github.com/MonetDB/MonetDB/issues/2247 | 753,355,713 | 2,247 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 02:42:03 +0100
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2009-11-10 09:45:51 +0100
## Comment 12665
Date: 2009-11-07 14:42:03 +0100
From: @drstmane
The test now produces
ERROR = !MALException:batcalc.CMDbataccumMOD:Illegal argument Requires bats of identical size
History:
Aug2009 branch:
- worked fine all of Oct 2009
Nov2009 branch:
- work fine til 2009/10/18
- (no testing 2009/10/19 - 2009/10/21)
- FAILED 2009/10/22 & 23
- worked fine 2009/10/24
- FAILS since 2009/10/25
details:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test/median_stdev.err.00.html
## Comment 12666
Date: 2009-11-10 09:45:51 +0100
From: @drstmane
This appears to work fine, again,
probably due to Niels' recent checkins.
Closing.
## Comment 12667
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893821 at http://sourceforge.net/support/tracker.php?aid=2893821
| SQL: src/test//Tests/median_stdev.sql fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2246/comments | 0 | 2020-11-30T10:30:07Z | 2024-06-27T11:42:36Z | https://github.com/MonetDB/MonetDB/issues/2246 | 753,355,677 | 2,246 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-07 02:28:12 +0100
From: @drstmane
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-11-12 10:38:30 +0100
## Comment 12661
Date: 2009-11-07 14:28:12 +0100
From: @drstmane
Tests pathfinder/tests/XRpc/Tests/xrpcConvert.xq.in & pathfinder/tests/XRpc/Tests/xrpcConvert2.xq fail on Debian & Fedora, only, with the Nov2009 branch since 2009/10/08, i.e., after checkins of 2009/10/07, (now) triggering a segfault
cf. e.g.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.32.32.d.1-Debian4.0/tests_XRpc/xrpcConvert.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.64.32.d.1-Fedora10/tests_XRpc/xrpcConvert.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.32.32.d.1-Debian4.0/tests_XRpc/xrpcConvert2.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.64.32.d.1-Fedora10/tests_XRpc/xrpcConvert2.err.00.html
(See also
ID: 1893448 "PF: xrpcConvert2 fails on Windows"
https://sourceforge.net/tracker/?func=detail&aid=1893448&group_id=56967&atid=482468
)
## Comment 12662
Date: 2009-11-07 14:32:31 +0100
From: @drstmane
Since there were no (relevant) checkins on the Nov2009 branch on 2009/10/07, and the problem does not occur on the Aug2009 branch, I suspect that it might be related to the (initial) changes on the Aug2009_NFI branch that were propagated to the Nov2009 branch on 2009/10/07.
## Comment 12663
Date: 2009-11-12 10:38:30 +0100
From: @peterboncz
fixed yesterday in Nov2009. This was an old bug.. not introduced at the NFI change at all.
## Comment 12664
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893815 at http://sourceforge.net/support/tracker.php?aid=2893815
| PF: xrpcConvert tests segfault since 2009/10/08 | https://api.github.com/repos/MonetDB/MonetDB/issues/2245/comments | 0 | 2020-11-30T10:30:04Z | 2024-06-27T11:42:36Z | https://github.com/MonetDB/MonetDB/issues/2245 | 753,355,627 | 2,245 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-06 08:06:19 +0100
From: Guillaume Theoret <<smokinn>>
To: @njnes
Version: -- development
Last updated: 2009-11-11 06:12:36 +0100
## Comment 12658
Date: 2009-11-06 20:06:19 +0100
From: Guillaume Theoret <<smokinn>>
MonetDB seems to evaluate both branches of a CASE regardless of whether the branch will be taken or not:
sql>SELECT
more>CASE SUM(payout_units_cpc)
more>WHEN 0 THEN 0
more>ELSE 1
more>END AS avg_cost_cpc
more>FROM daily.stats_2009_week_31;
SELECT
+--------------+
| avg_cost_cpc |
+==============+
| 0 |
+--------------+
1 tuple
Timer 27.990 msec 1 rows
sql>SELECT
more>CASE SUM(payout_units_cpc)
more>WHEN 0 THEN 0
more>ELSE cast(SUM(payout_units_cpc * payout_cpc) as numeric(12,4)) / SUM(payout_units_cpc)
more>END AS avg_cost_cpc
more>FROM daily.stats_2009_week_31;
!MALException:calc./:Illegal argument Division by zero
0 tuples
Timer 16.415 msec 0 rows
## Comment 12659
Date: 2009-11-11 18:12:31 +0100
From: @njnes
added test to src/BugTracker-2009/case_evaluates_all_branches.SF-2893484.sql
Fixed by rel_case_fixup optimizer
## Comment 12660
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893484 at http://sourceforge.net/support/tracker.php?aid=2893484
| All CASE branches are evaluated | https://api.github.com/repos/MonetDB/MonetDB/issues/2244/comments | 0 | 2020-11-30T10:30:00Z | 2024-06-27T11:42:35Z | https://github.com/MonetDB/MonetDB/issues/2244 | 753,355,577 | 2,244 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-06 05:49:35 +0100
From: Wouter Alink <<alink>>
To: @mlkersten
Version: -- development
Last updated: 2009-11-06 08:00:16 +0100
## Comment 12654
Date: 2009-11-06 17:49:35 +0100
From: Wouter Alink <<alink>>
from:
http://www.monetdb.nl/projects/monetdb/SQL/Documentation/TRACE-Statement.html
I would assume the following should not fail (on either Aug2009 or Nov2009 version):
$ mclient -lsql -daap
sql>set trace='show,pc,ticks';
!Variable trace unknown
0 tuples
sql>
Also, tracelog() is an undefined function. I assume some library needs to be loaded, but I cannot figure out which one.
## Comment 12655
Date: 2009-11-06 18:46:35 +0100
From: @mlkersten
Not confirm on Nov 2009 release.
The function can be cut/paste from the documentation page into the sql client
MonetDB server v5.16.0, based on kernel v1.34.0
Serving database 'demo', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Detected 7.753 GiB (8324386816 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /ufs/mk/candidate//Linux/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.34.0 loaded
>select trace;
&1 0 1 1 1
% . table_name
% single_value name
% varchar type
% 15 length
[ "show,ticks,stmt" ]
>set trace='show,ticks';
>select trace;
&1 0 1 1 1
% . table_name
% single_value name
% varchar type
% 10 length
[ "show,ticks" ]
>
## Comment 12656
Date: 2009-11-06 20:00:16 +0100
From: Wouter Alink <<alink>>
I messed up versions, indeed on Nov2009 it is not reproducible.
However, the website should have been documenting the Aug2009 release (as it is the latest released build).
Closing bug as it will be obsolete soon.
## Comment 12657
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893416 at http://sourceforge.net/support/tracker.php?aid=2893416
| SQL: trace documentation incomplete | https://api.github.com/repos/MonetDB/MonetDB/issues/2243/comments | 0 | 2020-11-30T10:29:56Z | 2024-06-28T13:21:53Z | https://github.com/MonetDB/MonetDB/issues/2243 | 753,355,532 | 2,243 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-06 01:44:19 +0100
From: Wouter Alink <<alink>>
To: @mlkersten
Version: -- development
Last updated: 2009-11-11 08:14:22 +0100
## Comment 12650
Date: 2009-11-06 13:44:19 +0100
From: Wouter Alink <<alink>>
Nov2009
I think it can be reproduced by first running a query prefixed with TRACE.
Even after restarting the mserver5 instance it segfaults on the first query executed (without TRACE prefix).
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fcbad3fc950 (LWP 12773)]
0x00007fcbb00ac299 in QOTupdateStatistics (nme=0x7fcbb00b9322 "inline", actions=0, val=2) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/optimizer/opt_statistics.mx:159
159 lp = (lng*) BUNtail(bi,p);
(gdb) bt
0 0x00007fcbb00ac299 in QOTupdateStatistics (nme=0x7fcbb00b9322 "inline", actions=0, val=2) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/optimizer/opt_statistics.mx:159
1 0x00007fcbb00a668c in OPTinline (cntxt=0x604c70, mb=0x2c711f8, stk=0x0, p=0x2c71a28) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/optimizer/opt_inline.mx:222
2 0x00007fcbb008902b in optimizeMALBlock (cntxt=0x604c70, mb=0x2c711f8) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/optimizer/opt_support.mx:671
3 0x00007fcbadc700da in addQueryToCache (c=0x604c70) at /export/scratch0/roberto/wouter/workspace/MonetDB/sql/src/backends/monet5/sql_optimizer.mx:623
4 0x00007fcbadc6e424 in backend_dumpproc (be=0x2c70b68, c=0x604c70, cq=0x2c71018, s=0x2c70e38) at /export/scratch0/roberto/wouter/workspace/MonetDB/sql/src/backends/monet5/sql_gencode.mx:1968
5 0x00007fcbadc6541b in SQLparser (c=0x604c70) at /export/scratch0/roberto/wouter/workspace/MonetDB/sql/src/backends/monet5/sql_scenario.mx:1065
6 0x00007fcbc2a6f32d in runPhase (c=0x604c70, phase=1) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_scenario.mx:602
7 0x00007fcbc2a6f424 in runScenarioBody (c=0x604c70) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_scenario.mx:638
8 0x00007fcbc2a6f651 in runScenario (c=0x604c70) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_scenario.mx:672
9 0x00007fcbc2a29f8d in MSserveClient (dummy=0x604c70) at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_session.mx:496
10 0x00000036f06073da in start_thread () from /lib64/libpthread.so.0
11 0x00000036efae62bd in clone () from /lib64/libc.so.6
(gdb) l
## Comment 12651
Date: 2009-11-06 13:49:33 +0100
From: Wouter Alink <<alink>>
additional info: it only happens when multiple queries are tried to be spawned at the same time
## Comment 12652
Date: 2009-11-06 19:23:13 +0100
From: @mlkersten
Thanks. The optimizer statistics tables were global and not protected.
## Comment 12653
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2893247 at http://sourceforge.net/support/tracker.php?aid=2893247
| SQL: QOTupdateStatistics segfaults | https://api.github.com/repos/MonetDB/MonetDB/issues/2242/comments | 0 | 2020-11-30T10:29:52Z | 2024-06-28T13:21:52Z | https://github.com/MonetDB/MonetDB/issues/2242 | 753,355,483 | 2,242 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-05 12:56:32 +0100
From: Wouter Alink <<alink>>
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2009-11-15 04:44:57 +0100
## Comment 12645
Date: 2009-11-05 12:56:32 +0100
From: Wouter Alink <<alink>>
Version: Yesterday's Nov2009 cvs.
similar to [http://sourceforge.net/support/tracker.php?aid=2890035]
When running 20 simultaneous jdbc connections, the mserver5 crashes (after a while) with the error below. If running the same amount of queries through 10 jdbc connections, the mserver5 instance does not crash.
$ ~/opt/MonetDB-stable/bin/mserver5 --dbinit="include sql;" --set mapi_port=50259 --dbfarm=/export/scratch0/roberto/wouter/dbfarm/ --dbname=db1
MonetDB server v5.14.3, based on kernel v1.32.3
Serving database 'db1', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /home/alink/opt/MonetDB-stable/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50259/
MonetDB/SQL module v2.32.3 loaded
>mserver5: /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB/src/gdk/gdk_bbp.mx:1759: incref: Assertion `BBP[(((int)(i))>0?((int)(i)):-((int)(i)))].refs+BBP[(((int)(i))>0?((int)(i)):-((int)(i)))].lrefs || BBP[(((int)(i))>0?((int)(i)):-((int)(i)))].status&16' failed.
Aborted
## Comment 12646
Date: 2009-11-06 10:30:21 +0100
From: Wouter Alink <<alink>>
(gdb) bt
0 0x00000036efa32f05 in raise () from /lib64/libc.so.6
1 0x00000036efa34a73 in abort () from /lib64/libc.so.6
2 0x00000036efa2bef9 in __assert_fail () from /lib64/libc.so.6
3 0x00007f2c0a0d0dc1 in incref (i=1477, logical=1, lock=0)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB/src/gdk/gdk_bbp.mx:1759
4 0x00007f2c0a0d1962 in decref (i=1477, logical=1, releaseShare=0)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB/src/gdk/gdk_bbp.mx:1837
5 0x00007f2c0a0d1163 in BBPdecref (i=1477, logical=1)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB/src/gdk/gdk_bbp.mx:1873
6 0x00007f2c0aa34e1e in runMALsequence (cntxt=0x607580, mb=0x46a44a8, startpc=1, stoppc=0,
stk=0x488f998, env=0x0, pcicaller=0x0)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_interpreter.mx:1590
7 0x00007f2c0aa2d07b in callMAL (cntxt=0x607580, mb=0x46a44a8, env=0x7f2bb38a3da8,
argv=0x7f2bb38a3df0, debug=0 '\0')
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_interpreter.mx:400
8 0x00007f2bf5c66a52 in SQLexecutePrepared (c=0x607580, be=0x44b3198, q=0x47bfde8)
at /export/scratch0/roberto/wouter/workspace/MonetDB/sql/src/backends/monet5/sql_scenario.mx:1206
9 0x00007f2bf5c66cc1 in SQLengineIntern (c=0x607580, be=0x44b3198)
at /export/scratch0/roberto/wouter/workspace/MonetDB/sql/src/backends/monet5/sql_scenario.mx:1259
10 0x00007f2bf5c6718b in SQLengine (c=0x607580)
at /export/scratch0/roberto/wouter/workspace/MonetDB/sql/src/backends/monet5/sql_scenario.mx:1369
11 0x00007f2c0aa7032d in runPhase (c=0x607580, phase=4)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_scenario.mx:602
12 0x00007f2c0aa704ba in runScenarioBody (c=0x607580)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_scenario.mx:647
13 0x00007f2c0aa70651 in runScenario (c=0x607580)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_scenario.mx:672
14 0x00007f2c0aa2af8d in MSserveClient (dummy=0x607580)
at /export/scratch0/roberto/wouter/workspace/MonetDB/MonetDB5/src/mal/mal_session.mx:496
15 0x00000036f06073da in start_thread () from /lib64/libpthread.so.0
16 0x00000036efae62bd in clone () from /lib64/libc.so.6
(gdb)
## Comment 12647
Date: 2009-11-06 15:33:51 +0100
From: Wouter Alink <<alink>>
additional info: also happens when starting server with "--set gdk_nr_threads=1" option
## Comment 12648
Date: 2009-11-15 16:44:56 +0100
From: Wouter Alink <<alink>>
as the someone might have noticed... I messed up versions. The mserver5 in the bug-report says '5.14', which is the Aug2009 release. I cannot reproduce this one with the actual Nov2009 branch.
Closing without bugreport, as it is difficult to reproduce the circumstances (database itself is too large for actual inclusion in the testweb).
## Comment 12649
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2892548 at http://sourceforge.net/support/tracker.php?aid=2892548
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: concurrency triggers gdk assertion | https://api.github.com/repos/MonetDB/MonetDB/issues/2241/comments | 0 | 2020-11-30T10:29:49Z | 2024-06-28T13:21:51Z | https://github.com/MonetDB/MonetDB/issues/2241 | 753,355,450 | 2,241 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-05 12:31:10 +0100
From: Wouter Alink <<alink>>
To: @njnes
Version: -- development
Last updated: 2009-11-15 04:40:13 +0100
## Comment 12641
Date: 2009-11-05 12:31:10 +0100
From: Wouter Alink <<alink>>
Yesterday I switched to Nov2009 (cvs, 11:00h)
Not sure whether it is reproducable, but the following steps caused mserver5 to segfault:
- started a new instance of 'mserver5 --dbinit="include sql;"'
- loaded a SQL dump using mclient (on loki, dump size was 70GB)
$ mclient -lsql -ddb1 dump.sql
this took little over 2 hours
- waited +- 7 hours (so I guess all logs have been flushed)
- connected to the database using JDBC and queried the data
- mserver5 crashed (almost) immediately reporting "Segmentation fault" (no query result had yet been returned)
I restarted the database, and from then on no crashes have occurred.
Note that performing the same scenario on a smaller dump didn't crash mserver5.
I will try to reproduce this issue tonight (and attach a debugger :)
## Comment 12642
Date: 2009-11-06 10:28:51 +0100
From: Wouter Alink <<alink>>
Could not reproduce this last night. I will try to reproduce it once more. For the time being marking it as invalid.
## Comment 12643
Date: 2009-11-15 16:40:13 +0100
From: Wouter Alink <<alink>>
I still get the occasional Segmentation Fault when pressing Ctrl-C on the mserver5 prompt when it is still busy computing a result, but I cannot reproduce the above problem. I will file a new bug if the Segmentation Fault can be reproduced properly.
Closing bug without test, as I couldn't reproduce the exact bug again.
## Comment 12644
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2892536 at http://sourceforge.net/support/tracker.php?aid=2892536
| SQL: crash after restore | https://api.github.com/repos/MonetDB/MonetDB/issues/2240/comments | 0 | 2020-11-30T10:29:45Z | 2024-06-28T13:21:50Z | https://github.com/MonetDB/MonetDB/issues/2240 | 753,355,411 | 2,240 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-05 09:04:50 +0100
From: @skinkie
To: @njnes
Version: -- development
CC: bugs-sql, duc, @hannesmuehleisen
Last updated: 2013-10-08 11:31:33 +0200
## Comment 12638
Date: 2009-11-05 09:04:50 +0100
From: @skinkie
Dataset;
http://mirror.openstreetmap.nl/knmi/KNMI.sql
Query;
select epoch(cast(date as timestamp)) * 1000, ((CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END) + (CASE WHEN station136 is NULL THEN 0 ELSE station136 END)) from rivm_co WHERE date BETWEEN '2009-1-1' AND '2009-7-1' limit 3;
[yes this was a query generator bug]
Results:
+--------------------+-------------------+
| sql_mul_epoch_date | isnull_station136 |
+====================+===================+
| 1230768000000 | -16352 |
| 1230771600000 | -26240 |
| 1230775200000 | -26688 |
+--------------------+-------------------+
Bad results above; see below:
sql>select min(station136) from rivm_co WHERE date BETWEEN '2009-1-1' AND '2009-7-1' limit 3;
+--------------+
| single_value |
+==============+
| 84 |
+--------------+
1 tuple
## Comment 12639
Date: 2009-11-22 22:02:23 +0100
From: @njnes
seems to work now. Could we create a small example?
## Comment 12640
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2892439 at http://sourceforge.net/support/tracker.php?aid=2892439
## Comment 16482
Date: 2011-10-27 14:47:09 +0200
From: @sjoerdmullender
Changeset [444ccffd7751](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=444ccffd7751) 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=444ccffd7751](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=444ccffd7751)
Changeset description:
Added test for bug #2239.
## Comment 16483
Date: 2011-10-27 14:47:59 +0200
From: @sjoerdmullender
(In reply to comment 1)
> seems to work now. Could we create a small example?
It doesn't work, and we now have a test.
## Comment 19256
Date: 2013-10-08 11:31:33 +0200
From: @hannesmuehleisen
Test case succeeds on Feb2013 build.
| Overflow using CASE | https://api.github.com/repos/MonetDB/MonetDB/issues/2239/comments | 0 | 2020-11-30T10:29:42Z | 2024-06-27T11:42:29Z | https://github.com/MonetDB/MonetDB/issues/2239 | 753,355,368 | 2,239 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-04 08:48:59 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-11-04 10:15:35 +0100
## Comment 12633
Date: 2009-11-04 08:48:59 +0100
From: @drstmane
After yesterday''s (Tue Nov 3 2009) checkins, M5/MAL's io.print() yields no output anymore:
$ mserver5
MonetDB server v5.16.0, based on kernel v1.34.0
Serving database 'demo', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Detected 7.753 GiB (8324386816 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Candidate/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>io.print(1);
>
$ mclient -lmal
Welcome to mclient, the MonetDB interactive terminal
Type \q to quit, \? for a list of available commands
mal>io.print(1);
mal>
## Comment 12634
Date: 2009-11-04 09:56:42 +0100
From: @mlkersten
Sorry working on it.
## Comment 12635
Date: 2009-11-04 10:12:21 +0100
From: @sjoerdmullender
Found it: it's your change to opt_support.mx where you removed the variable qot. By doing so, you changed the condition of the do/while loop. It used to be that the loop was never executed more than once since qot was always 0. Now the loop can execute multiple times since the qot was removed from the conditional.
## Comment 12636
Date: 2009-11-04 10:15:35 +0100
From: @mlkersten
Mtest runs again on M5 and M5/SQL
## Comment 12637
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2891718 at http://sourceforge.net/support/tracker.php?aid=2891718
| M5/MAL: io.print() yields no output | https://api.github.com/repos/MonetDB/MonetDB/issues/2238/comments | 0 | 2020-11-30T10:29:39Z | 2024-06-28T13:21:50Z | https://github.com/MonetDB/MonetDB/issues/2238 | 753,355,332 | 2,238 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-03 11:36:54 +0100
From: Wouter Alink <<alink>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-11-15 05:46:38 +0100
## Comment 12628
Date: 2009-11-03 11:36:54 +0100
From: Wouter Alink <<alink>>
I have two mserver5 instances running (manually started, not using merovingian):
- one instance on port 50000, dbname "x1"
- one instance on port 50001, dbname "x2"
They both use the same dbfarm root-folder.
If I connect (using JDBC) to:
localhost:50001/x1
This is: connecting to the port of db "x2" and the name of db "x1", then it will connect me to the x1 database.
To me this is counterintuitive. I would have expected an error, something like "this database is not served by this mserver instance", or "cannot connect".
(using Aug2009 branch, but from Fabian I understood it is currently happening in all versions)
## Comment 12629
Date: 2009-11-03 11:41:26 +0100
From: @grobian
this is a feature of mserver5 predating merovingian that can be removed again
## Comment 12630
Date: 2009-11-15 16:37:05 +0100
From: Wouter Alink <<alink>>
Fabian, should this become a feature request? (or should I add a test for this one?)
## Comment 12631
Date: 2009-11-15 17:46:38 +0100
From: @grobian
I just removed the feature from the CVS Current branch.
## Comment 12632
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2891191 at http://sourceforge.net/support/tracker.php?aid=2891191
| unconscious redirect | https://api.github.com/repos/MonetDB/MonetDB/issues/2237/comments | 0 | 2020-11-30T10:29:35Z | 2024-06-27T11:42:27Z | https://github.com/MonetDB/MonetDB/issues/2237 | 753,355,286 | 2,237 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-02 09:08:54 +0100
From: david85 <<david852>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-11-03 02:16:04 +0100
## Comment 12623
Date: 2009-11-02 21:08:54 +0100
From: david85 <<david852>>
Hello,
I encountered an error when executing my queries at this method.
Using: "Aug2009-SP1" driver / monetdb-1.13-jdbc.jar
and jdk 1.6.0_14/jre
and Eclipse Version: 3.4.2
OS: Windows Vista 64 Bit w. newest updates
My Query Structure:
"INSERT INTO tableName VALUES(...), VALUES(...), VALUES(...), ..."
I used the simple statement.execute command to execute that query, however I encountered an
IndexOutOfBoundsException.
I traced it down to the following line:
return(soh.subSequence(0, cnt).toString());
where cnt = 2 and soh.Remaining() = 2;
I downloaded "Aug2009-SP1" source code / MonetDB-java-1.32.2.zip and modified the method
as follows:
The original code is:
pos++;
if (!soh.hasRemaining()) throw
new MCLParseException("unexpected end of string", soh.position() - 1);
int cnt = 0;
soh.mark();
while (soh.hasRemaining() && soh.get() != ' ') {
cnt++;
}
soh.reset();
return(soh.subSequence(0, cnt).toString());
My version is:
pos++;
if (!soh.hasRemaining()) throw
new MCLParseException("unexpected end of string", soh.position() - 1);
int cnt = 0;
String subSequence = "";
while (soh.hasRemaining()) {
char read = soh.get();
if(read == ' ')
break;
subSequence += read;
cnt++;
}
return subSequence;
And the error was gone.
I thought I should report this although I don't know whether it's relevant or even my own fault that
I got that error. I also found an entry regarding this error, but I don't know whether it has been removed
or reported yet.
Best Regards,
David
## Comment 12624
Date: 2009-11-02 21:22:25 +0100
From: @grobian
hi David,
This issue should have been fixed already in the JDBC driver from the Aug2009-SP2 release. You can find it in the monetdb-1.14-jdbc.jar driver. Can you try if that one fixes the issue for you too?
## Comment 12625
Date: 2009-11-02 21:57:18 +0100
From: david85 <<david852>>
Hello,
Yes of course, I will try it with the new driver, but since I'm currently running something that can't be stopped I'll post the result tomorrow if that's ok.
Best Regards,
David
## Comment 12626
Date: 2009-11-03 14:16:04 +0100
From: david85 <<david852>>
Hello,
ok now I tested it again and it seems to working properly now :).
Thanks and Best Regards,
David
## Comment 12627
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2890914 at http://sourceforge.net/support/tracker.php?aid=2890914
| StartOfHeaderParser.java#getNextAsString() Err: IndexOutOfB | https://api.github.com/repos/MonetDB/MonetDB/issues/2236/comments | 0 | 2020-11-30T10:29:32Z | 2024-06-28T13:21:49Z | https://github.com/MonetDB/MonetDB/issues/2236 | 753,355,238 | 2,236 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-11-02 02:45:39 +0100
From: @drstmane
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-11-03 04:07:05 +0100
## Comment 12618
Date: 2009-11-02 14:45:39 +0100
From: @drstmane
The new pma.mx module fils to compile on various platform with, a.o.,
MonetDB5/src/modules/mal/pma.mx:866: warning: dereferencing type-punned pointer will break strict-aliasing rules
MonetDB5/src/modules/mal/pma.mx:867: warning: dereferencing type-punned pointer will break strict-aliasing rules
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.32.32.d.1-Darwin9.8.0/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.64.64.d.1-Darwin9.8.0/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.32.32.d.1-Debian4.0/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.64.64.d.1-Gentoo2.0.1/make.out.html
MonetDB5/src/modules/mal/pma.mx(387): error 593: parameter "dummy" was set but never used
PMAdel_bte(void *dummy, bat *bid, oid *pos) {
^
MonetDB5/src/modules/mal/pma.mx(852): error 593: parameter "dummy" was set but never used
PMAtestins_bte(void *dummy, bat *bid, int *num) {
^
MonetDB5/src/modules/mal/pma.mx(856): error 593: variable "base" was set but never used
bte *base;
^
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.64.32.d.1-Fedora10/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.64.64.d.1-Fedora10/make.out.html
.\..\..\..\..\src\modules\mal\pma.mx(138): error: a function declared "dllimport" may not be defined
PMAnew(bat *res, int *tpe, int *sz) {
^
.\..\..\..\..\src\modules\mal\pma.mx(167): error: a function declared "dllimport" may not be defined
PMAins_bte(oid *pos_res, bat *bid, oid *pos, bte *val) {
^
.\..\..\..\..\src\modules\mal\pma.mx(387): error: a function declared "dllimport" may not be defined
PMAdel_bte(void *dummy, bat *bid, oid *pos) {
^
.\..\..\..\..\src\modules\mal\pma.mx(489): error: a function declared "dllimport" may not be defined
PMAbulkdel_bte(void *dummy, bat *bid, oid *lo, oid *hi) {
^
.\..\..\..\..\src\modules\mal\pma.mx(612): error: a function declared "dllimport" may not be defined
PMAfnd_bte(oid *lo_res, oid *hi_res, bat *bid, oid *lo, oid *hi, bte *val) {
^
.\..\..\..\..\src\modules\mal\pma.mx(702): error: a function declared "dllimport" may not be defined
PMAbulkins_bte(oid *pos_res, bat *bid, oid *pos, bat *ibid) {
^
.\..\..\..\..\src\modules\mal\pma.mx(852): error: a function declared "dllimport" may not be defined
PMAtestins_bte(void *dummy, bat *bid, int *num) {
^
.\..\..\..\..\src\modules\mal\pma.mx(873): error: a function declared "dllimport" may not be defined
PMAtestdel_bte(void *dummy, bat *bid) {
^
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.32.32.d.1-Windows5.1/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.64.32.d.1-Windows6.0/make.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Int.64.64.d.1-Windows6.0/make.out.html
## Comment 12619
Date: 2009-11-02 15:01:12 +0100
From: @drstmane
I just fixed the last two problems with icc and on Windows.
See my respective checkins and/or
`cvs diff -r1.{1,2} src/modules/mal/pma.mx`
`cvs diff -r1.{2,3} src/modules/mal/pma.mx`
for details.
The first problem "warning: dereferencing type-punned pointer will break strict-aliasing rules" is still open.
## Comment 12620
Date: 2009-11-02 18:00:03 +0100
From: @drstmane
After some defensive code clean-up
(see
`cvs log -r1.3::1.6 src/modules/mal/pma.mx`
and
`cvs diff -r1.{3,6} src/modules/mal/pma.mx`
for details),
I hopefully also fixed the "dereferencing type-punned pointer will break strict-aliasing rules" problem;
see
`cvs diff -r1.{6,7} src/modules/mal/pma.mx`
for details.
Report can be closed once nightly testing has confirmed the fixes.
## Comment 12621
Date: 2009-11-03 16:07:04 +0100
From: @drstmane
With my yesterday's fixes, pma.mx now seems to compile fine.
Closing.
## Comment 12622
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2890702 at http://sourceforge.net/support/tracker.php?aid=2890702
| M5: pma.mx fails to compile on various platforms | https://api.github.com/repos/MonetDB/MonetDB/issues/2235/comments | 0 | 2020-11-30T10:29:29Z | 2024-06-27T11:42:25Z | https://github.com/MonetDB/MonetDB/issues/2235 | 753,355,200 | 2,235 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-31 07:21:10 +0100
From: Wouter Alink <<alink>>
To: @mlkersten
Version: -- development
Last updated: 2009-11-05 12:58:00 +0100
## Comment 12613
Date: 2009-10-31 19:21:10 +0100
From: Wouter Alink <<alink>>
The following happens: (I think on a two weeks old cvs version of Aug2009 branch)
Firing queries at MonetDB using multiple threads (10) in a java program, connecting to MonetDB/SQL via JDBC. Each thread executes a series of queries (50 queries). All threads run the same SQL query (only different literal values). Each thread uses its own JDBC-connection. Each query runs for +-5 to 10 seconds. After a while, 1 thread throws an exception (all others continue):
SQLException:optimizer: 'multiplex' should be the last
SQLException:optimizer: 'deadcode' should be used at least once
SQLException:optimizer: pipeline set to 'inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex'
This seems to happens consistently when firing queries with 10 threads or more. It does not happen when running with only 4 threads.
What could be wrong? What information is relevant to find the cause?
the queries look like:
START TRANSACTION;
CREATE VIEW ...
CREATE TABLE ...
CREATE VIEW ...
SELECT ...
ROLLBACK;
the database is created from a SQL dump of +-40GB.
the system is loki (a quad-core machine)
## Comment 12614
Date: 2009-10-31 19:44:55 +0100
From: @mlkersten
Most likely a concurrency conflict on the optimizer pipeline structures. The pipeline is global and current not protected it seems by a lock.
## Comment 12615
Date: 2009-10-31 19:58:12 +0100
From: @mlkersten
Patch has been provided on the candidate release (Nov2009)
## Comment 12616
Date: 2009-11-05 12:57:57 +0100
From: Wouter Alink <<alink>>
i cannot reproduce the same error on Nov2009 branch. closing bug.
(see bug[2892548] for next issue)
## Comment 12617
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2890035 at http://sourceforge.net/support/tracker.php?aid=2890035
| SQL: optimizer confused by concurrency | https://api.github.com/repos/MonetDB/MonetDB/issues/2234/comments | 0 | 2020-11-30T10:29:26Z | 2024-06-27T11:42:24Z | https://github.com/MonetDB/MonetDB/issues/2234 | 753,355,167 | 2,234 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-31 04:27:19 +0100
From: winston <<wwinston>>
To: Peter Boncz <<boncz>>
Version: -- development
CC: @drstmane
Last updated: 2011-05-03 10:43:03 +0200
## Comment 12606
Date: 2009-10-31 16:27:19 +0100
From: winston <<wwinston>>
I installed MonetDB4/XQuery 32-bit on (1) Windows XP 32-bit, and (2) Windows Vista 64-bit. I need to use the exact same MonetDB version.
For example, when I compare the two using the XPath (XQuery) "//open_auction//description//listitem//keyword" on XMark database size=0.005:
(1) On Windows XP the query takes: 0.016 seconds and returns 47 rows.
(2) On Windows Vista the query takes 18.7 seconds to return the same 47 rows.
This demonstrates that Vista runs this application 1000x SLOWER than on Windows XP.
The computer is a new Dell laptop, with 8GB Ram and 2GH processer. The processor speeds are the same on the XP and Vista boxes.
I uninstalled the McAfee virus checker thinking it was the problem and installed Microsoft One Care (also installed on the XP machine), but there is no change in the performance.
What is going on here? Why is Windows Vista so excruciatingly SLOW for MonetDB, 1000x slower, when compared to Windows XP?
Any idea how to improve MonetDB performance on Vista?
## Comment 12607
Date: 2009-10-31 17:37:26 +0100
From: winston <<wwinston>>
BTW: The measurements were taken from a Java program using the 1.14 client jar.
## Comment 12608
Date: 2009-11-02 19:15:38 +0100
From: @sjoerdmullender
Would it be possible to install the 64 bit version of MonetDB on your Vista and try the experiment again? I don't have a 64 bit Vista on bare metal to try this on, and I doubt running it in a virtual machine gives reliable timing results.
## Comment 12609
Date: 2009-11-02 19:59:44 +0100
From: @drstmane
As a side not In this context, not knowing whether it is indeed related, I just recall that I experienced some quite slow performance when trying to run our nightly testing of 32-bit Windows on a 64-bit Windows server ('ver' says "Microsoft Windows [Version 6.0.6001]", hence, I guess this is some Vista server version) --- I did not analyze this any further and cannot tell whether the slow performance was only with running the tests (i.e., running MonetDB) or also with compiling MonetDB ...
## Comment 12610
Date: 2009-11-02 20:00:15 +0100
From: @drstmane
"side not" -> "side note"
## Comment 12611
Date: 2009-11-17 00:54:48 +0100
From: @peterboncz
I will take a look with a recent Nov2009 build
## Comment 12612
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2889989 at http://sourceforge.net/support/tracker.php?aid=2889989
## Comment 15781
Date: 2011-05-03 10:43:03 +0200
From: @drstmane
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.
| MonetDB4/XQuery Extremely Slow on Vista 64-bit | https://api.github.com/repos/MonetDB/MonetDB/issues/2233/comments | 0 | 2020-11-30T10:29:22Z | 2024-06-28T13:21:48Z | https://github.com/MonetDB/MonetDB/issues/2233 | 753,355,118 | 2,233 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-28 10:11:33 +0100
From: Maurice van Keulen <<mvankeulen>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-10-30 01:34:15 +0100
## Comment 12599
Date: 2009-10-28 10:11:33 +0100
From: Maurice van Keulen <<mvankeulen>>
System: MacBook Pro, MacOS X 10.6.1
I tried to compile the Aug2009 cvs checkout, but it stopped in the MonetDB-module with the following error:
stream.mx: In function ‘file_fsync’:
stream.mx:798: error: implicit declaration of function ‘fdatasync’
config.log attached.
## Comment 12600
Date: 2009-10-28 10:24:06 +0100
From: @grobian
Can you please post the head of fdatasync manpage? (e.g. which includes are necessary?) Can you please download http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./0_latest/SourceSuperBall/MonetDB-Aug2009-SuperBall-DB0.tar.bz2 and run it's monetdb-install.sh as follows:
./monetdb-install.sh --prefix=/var/tmp/compile-test --enable-xquery
and report if that finishes successfully and if that also runs?
## Comment 12601
Date: 2009-10-28 11:46:27 +0100
From: Maurice van Keulen <<mvankeulen>>
I could not find a fdatasync manpage.
The source super ball does give the warning
stream.c: In function 'file_fsync':
stream.c:516: warning: implicit declaration of function 'fdatasync'
but it succesfully compiles to the end.
## Comment 12602
Date: 2009-10-28 12:34:10 +0100
From: @grobian
thanks, that makes this issue not a blocker for SP2, however, I'll look into a fix.
## Comment 12603
Date: 2009-10-28 12:54:02 +0100
From: @grobian
I checked in a fix in CVS a second ago. Care to test if it works?
## Comment 12604
Date: 2009-10-30 13:34:14 +0100
From: @grobian
NEEDINFO
## Comment 12605
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2887777 at http://sourceforge.net/support/tracker.php?aid=2887777
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.
| MonetDB module fails to compile on my new Mac | https://api.github.com/repos/MonetDB/MonetDB/issues/2232/comments | 0 | 2020-11-30T10:29:19Z | 2024-06-28T13:21:47Z | https://github.com/MonetDB/MonetDB/issues/2232 | 753,355,068 | 2,232 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-27 05:25:36 +0100
From: Allen <<allenzhangpmci>>
To: @njnes
Version: -- development
Last updated: 2009-11-11 08:35:42 +0100
## Comment 12596
Date: 2009-10-27 17:25:36 +0100
From: Allen <<allenzhangpmci>>
sql query ignore the where condition towards last union table or result set.
## Comment 12597
Date: 2009-11-11 20:35:40 +0100
From: @njnes
added test to sql union_where_combined.SF-2887282.sql
fixed a bug in select push down.
## Comment 12598
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2887282 at http://sourceforge.net/support/tracker.php?aid=2887282
| union bug | https://api.github.com/repos/MonetDB/MonetDB/issues/2231/comments | 0 | 2020-11-30T10:29:15Z | 2024-06-27T11:42:21Z | https://github.com/MonetDB/MonetDB/issues/2231 | 753,355,012 | 2,231 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-26 12:41:11 +0100
From: @swingbit
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2009-10-27 11:08:06 +0100
## Comment 12591
Date: 2009-10-26 12:41:11 +0100
From: @swingbit
While indexing in PFTijah a rathr large collection (2M XML documents, ~75GB in total),
the following assertion pops up.
Given the size of the data and the IP constraints, I cannot easily provide a reproducible test here,
but the gdb session is open on my machine at CWI, anyone itching to give it a go? ;-)
0 0xa000000000010621 in __kernel_syscall_via_break ()
1 0x20000000020781c0 in raise () from /lib/libc.so.6.1
2 0x200000000207a810 in abort () from /lib/libc.so.6.1
3 0x2000000002068680 in __assert_fail () from /lib/libc.so.6.1
4 0x20000000014b10f0 in GDKfree_ () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libbat.so.1
5 0x20000000015b39d0 in merge_getmemh () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libbat.so.1
6 0x20000000015d0630 in merge_at_oid () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libbat.so.1
7 0x20000000016481c0 in GDKssort () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libbat.so.1
8 0x200000000131dfb0 in BATsorder () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libbat.so.1
9 0x200000000131e8d0 in BATssort () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libbat.so.1
10 0x200000000007cc30 in CMDssort () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_algebra.so.4
11 0x200000000006f480 in CMDssort_unpack1538144325 ()
from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_algebra.so.4
12 0x20000000002ee630 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
13 0x2000000000314640 in interpret_assignment () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
14 0x20000000002f0050 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
15 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
16 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
17 0x20000000002f2ad0 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
18 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
19 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
20 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
21 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
22 0x20000000002ece30 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
23 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
24 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
25 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
26 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
27 0x20000000002ece30 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
28 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
29 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
30 0x20000000001f6360 in CMDcatch () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_builtin.so.4
31 0x20000000002eeec0 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
32 0x2000000000314220 in interpret_assignment () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
33 0x2000000000314bb0 in interpret_var () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
34 0x20000000002eeff0 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
35 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
36 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
37 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
38 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
39 0x20000000002ece30 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
40 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
41 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
42 0x20000000002f2890 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
43 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
44 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
45 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
46 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
47 0x20000000002ece30 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
48 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
49 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
50 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
51 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
52 0x20000000002ece30 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
53 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
54 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
55 0x20000000002f2890 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
56 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
57 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
58 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
59 0x20000000002f0150 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
60 0x20000000002f91b0 in tuple_interpret_vpval_fival () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
61 0x20000000001b26e0 in doCMDbatloop () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_bat.so.4
62 0x20000000001a09d0 in CMDbatloop_std_unpack733212973 ()
from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_bat.so.4
63 0x2000000000317fd0 in interpret_iterator () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
64 0x20000000002ede20 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
65 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
66 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
67 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
68 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
69 0x20000000002ece30 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
70 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
71 0x20000000002f0110 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
72 0x20000000001f6360 in CMDcatch () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_builtin.so.4
73 0x20000000002eeec0 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
74 0x20000000003147c0 in interpret_assignment () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
75 0x20000000002f0050 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
76 0x2000000000313860 in interpret_seqblock () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
77 0x20000000002f0150 in interpret () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/libmonet.so.4
78 0x200000000aa69f50 in xquery_tree_exec (ctx=0x60000000001b56e8, t=0x6000000000d9f648, repeat=0)
at /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/src/pathfinder/runtime/pathfinder.mx:4525
79 0x200000000aa6b0c0 in xquery_mil_exec (ctx=0x60000000001b56e8,
buf=0x6000000001574c30 "var tijah_scoreDB;\nvar tijah_dummyPOS;\ntijah_dummyPOS := new (oid, oid);\nvar tijah_ftiTape;\ntijah_ftiTape := new (str, bat);\nvar xrpc_qid;\nvar xrpc_caller;\nvar xrpc_hdl;\nvar xrpc_seqnr;\nvar xrpc_timeo"...)
at /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/src/pathfinder/runtime/pathfinder.mx:4583
80 0x200000000aa6cb00 in xquery_compile_exec (ctx=0x60000000001b56e8, options=2,
xquery=0x6000000000d17d99 "tijah:create-ft-index((\"clefip2009\"),<TijahOptions stemmer=\"stopwords-english\" whitelist=\"abstract description invention-title claim\"/>)\n", is_url=0, prologue=0x200000000d1fe528, query=0x200000000d1fe530, epilogue=0x200000000d1fe538, module=0x0)
at /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/src/pathfinder/runtime/pathfinder.mx:4746
81 0x200000000aa80c60 in xquery_prepare (ctx=0x60000000001b56e8, usec=18635914162,
query=0x6000000000d17d99 "tijah:create-ft-index((\"clefip2009\"),<TijahOptions stemmer=\"stopwords-english\" whitelist=\"abstract description invention-title claim\"/>)\n") at /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/src/pathfinder/runtime/pathfinder.mx:6065
82 0x200000000aa820d0 in xquery_client_engine (mc=0x200000000b1d3818)
at /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/src/pathfinder/runtime/pathfinder.mx:6220
83 0x200000000b1be270 in mapi_client_engine () from /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/MonetDB/lib/MonetDB4/lib/lib_mapi.so.4
84 0x2000000001be5050 in start_thread () from /lib/libpthread.so.0
85 0x20000000021acb10 in __clone2 () from /lib/libc.so.6.1
## Comment 12592
Date: 2009-10-26 12:57:49 +0100
From: @drstmane
What excatly does the assertion say?
;-)
## Comment 12593
Date: 2009-10-26 13:30:48 +0100
From: @swingbit
True, I forgot that:
Mserver: /space/home/rcornacc/lhm_code/HyServer/MonetDB/MonetDB.stable/src/MonetDB/src/gdk/gdk_utils.mx:1126: GDKfree_: Assertion `size != 0' failed.
## Comment 12594
Date: 2009-10-27 11:08:06 +0100
From: @swingbit
my apologies, this is an invalid bug report.
It appears that the problem was caused by leftovers in the installation dir of MonetDB.
Discovered after Wouter made me notice there were no debug info in my gdb session, although I had compiled with debug info on.
Closing the bug report (and changing my scripts to make uninstall first)
## Comment 12595
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2886428 at http://sourceforge.net/support/tracker.php?aid=2886428
| Assertion in GDKfree_() while indexing with PFTijah | https://api.github.com/repos/MonetDB/MonetDB/issues/2230/comments | 0 | 2020-11-30T10:29:11Z | 2024-06-28T13:21:46Z | https://github.com/MonetDB/MonetDB/issues/2230 | 753,354,958 | 2,230 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-22 06:44:36 +0200
From: @romulogoncalves
To: Documentation maintainers <<bugs-docs>>
Version: unspecified
Last updated: 2011-09-07 17:03:50 +0200
## Comment 12588
Date: 2009-10-22 18:44:36 +0200
From: @romulogoncalves
In monetdb web-page I read the VOC tutorial and I see the the following:
shell> mclient -lsql -uvoc -Pvoc
sql> \< voc_dump.sql
Then I went to:
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/MAPI-Client.htmlMAPI-Client
And for client options I see:
-P passwd | --passwd=passwd password
I just tried in my cvs head version and the option -P does not work. Reading some check ins in clients module, it seems
we have to use .monetdb file to avoid typing the password. However, the syntax of the file was not specified. I create
the file .monetdb with following content:
monetdb
monetdb
And I get the following message:
[goncalve@sirius scripts]$ ./mclient current debug sql
.monetdb:1: syntax error: monetdb
.monetdb:2: syntax error: monetdb
password:
## Comment 12589
Date: 2009-10-22 19:01:11 +0200
From: @grobian
the webpage reflects the current stable version
We keep this one around as reminder for somewhere in february 2010
## Comment 12590
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2884056 at http://sourceforge.net/support/tracker.php?aid=2884056
## Comment 13989
Date: 2010-05-04 14:28:48 +0200
From: @grobian
TODO: figure out what's the current state again and compare to
http://monetdb.cwi.nl/SQL/Documentation/MAPI-Client.htmlMAPI-Client
## Comment 15423
Date: 2011-01-25 15:05:44 +0100
From: @grobian
current state is wrong, but I fail to find the source for this page.
## Comment 16192
Date: 2011-09-07 17:03:50 +0200
From: @sjoerdmullender
On the new website the page is:
http://www.monetdb.org/Documentation/Cookbooks/SQLrecipies/Clients/MAPI
I updated the page with the current (Apr2011-SP2) information.
| update MAPI-Client documentation page | https://api.github.com/repos/MonetDB/MonetDB/issues/2229/comments | 0 | 2020-11-30T10:29:08Z | 2024-06-27T11:42:19Z | https://github.com/MonetDB/MonetDB/issues/2229 | 753,354,918 | 2,229 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-22 06:38:47 +0200
From: @romulogoncalves
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-12-01 12:44:23 +0100
## Comment 12584
Date: 2009-10-22 18:38:47 +0200
From: @romulogoncalves
Hello,
In this page:
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/Start-and-Stop.htmlStart-and-Stop
I click on
See for a more complete session "VOC demo."
and I end up in the same page, I think the right link should be:
http://monetdb.cwi.nl/projects/monetdb/SQL/QuickTour/VOC/index.html
## Comment 12585
Date: 2009-11-17 00:18:55 +0100
From: @drstmane
Seems to be fine (fixed?) in CVS:
$ egrep 'See for a more complete session|VOC demo' monetweb/Docs/MonetDB/StartStop.texi
See for a more complete session @url{"SQL/QuickTour/VOC/index.html",VOC demo}.
Will be live (and should be checked) once we re-build the live web site with the upcoming release ...
## Comment 12586
Date: 2009-12-01 12:44:22 +0100
From: @drstmane
Fixed:
===================================================================
2009/12/01 - manegold: monetweb/Docs/MonetDB/StartStop.texi,1.23
monetweb/Docs/MonetDB/StartStop.texi,1.22
(trying to) fix URL; cf.,
ID: 2884050 "Broken link to VOC tutorial"
https://sourceforge.net/tracker/?func=detail&aid=2884050&group_id=56967&atid=482468
===================================================================
2009/12/01 - manegold: monetweb/Docs/MonetDB/Features.texi,1.13
monetweb/Docs/MonetDB/SalesFeatures.texi,1.4
monetweb/Docs/MonetDB/iSQL-Viewer.texi,1.4
monetweb/Docs/MonetDB/perlmanual.texi,1.2
monetweb/Docs/XQuery/Research.texi,1.8
fixed URLs in texi code:
no quotes, no whitespace!
===================================================================
website is currently being rebuilt.
## Comment 12587
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2884050 at http://sourceforge.net/support/tracker.php?aid=2884050
| Broken link to VOC tutorial | https://api.github.com/repos/MonetDB/MonetDB/issues/2228/comments | 0 | 2020-11-30T10:29:04Z | 2024-06-27T11:42:18Z | https://github.com/MonetDB/MonetDB/issues/2228 | 753,354,867 | 2,228 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-18 01:09:02 +0200
From: @mlkersten
To: clients devs <<bugs-clients>>
Version: -- development
Last updated: 2012-11-12 21:35:12 +0100
## Comment 12565
Date: 2009-10-18 13:09:02 +0200
From: @mlkersten
Make a file x with the content "trace select * from tables:"
run:
mk@eir::~/tpch> mclient -lsql -fsql <x
+------------------------------------------------------------------------------+
| 2 usec mdb.setTimer(true); |
| 1 usec @0 mdb.setThread(true); |
| 5 usec @0 barrier _292 := language.dataflow(); |
+--------------------------------------+---------------------------------------+
| 8 usec @0 _2:bat[:oid | :sht |
| 4 usec @0 _7:bat[:oid | :oid |
+------------------------------------------------------------------------------+
| 5 usec @0 _9<tmpr_2074>[0 |
+--------------------------------------+---------------------------------------+
| 4 usec @0 _7:bat[:oid
The formatting is screwed up.
## Comment 12566
Date: 2009-10-18 13:16:11 +0200
From: @grobian
I think you mean the timer information is written in the output, which may very well be an artifact of a feature request I implemented.
## Comment 12567
Date: 2009-10-18 13:22:38 +0200
From: @mlkersten
The expected output was
sql>trace select * from tables;
| 6 usec mdb.setTimer(true); |
| 1 usec @0 mdb.setThread(true); |
| 21 usec @0 barrier _292 := language.dataflow(); |
| 10 usec @0 _2:bat[:oid,:sht] <tmp_2320>[0] := sql.bind("tmp","_tables","type",0); |
|
## Comment 12568
Date: 2009-10-18 13:24:12 +0200
From: @mlkersten
Alternatively, there would be a two-column table, separating the timing from the instruction itself
## Comment 12569
Date: 2009-10-18 13:39:07 +0200
From: @grobian
that actually would best be done just at the server end by emitting two columns...
## Comment 12570
Date: 2009-10-18 17:48:49 +0200
From: @grobian
the server sends stuff like this:
[ 4 usec _138<tmp_1216>[26] := bat.append(<tmp_1216>[26],<tmp_1217>[0],true); ]
which is neither a quoted string, nor a string that doesn't contain potentially confusing chars like ]
It remains weird that the rendering differs depending on how the data is fed into mclient.
## Comment 12571
Date: 2009-10-18 18:05:31 +0200
From: @grobian
Actually, it sees the comma and splits on it. I don't understand why it behaves differently when executed via doFileByLines vs. doFile. However, we can trace back the rendering garbage to the server not adhering the protocol.
## Comment 12572
Date: 2009-10-18 19:52:05 +0200
From: @mlkersten
Yes, timing information, like debugging information, is not in strict tuple field format.
Therefore, in mclient the state of computation (trace,debug modes) was used for rendering decisions.
Whose semantics seems to got lost in the recent modifications.
To align the raw mode required, i will change the marker to ''. This way all values returned as comment
can be cast as a string covering all columns in mclient. Even replacing | into
## Comment 12573
Date: 2009-10-18 19:56:05 +0200
From: @grobian
seems to me this got introduced when the TABLEformatter was introduced, which is not so recent.
## Comment 12574
Date: 2009-10-22 16:57:04 +0200
From: @sjoerdmullender
The main problem is in the data being generated. After the recent changes, the trace output is output with a leading `=' which makes mclient think that bit is a single column table. However, this is interspersed with the output of the query being traced. This confuses the hell out of mclient.
A possible solution is to collect the trace output in a table on the server, and then outputting the table at the end of the query as an extra SQL result set.
Another solution could be to suppress the query output and only output the trace results. After all, you prepend the query with the trace keyword because that is the output you want to see. If you want the query result, omit the trace.
In any case, bouncing this back to Martin.
## Comment 12575
Date: 2009-10-24 23:08:50 +0200
From: @mlkersten
The SQL trace facility has been changed. The events are collected in BATs and printed after the result set has been sent. The table-based rendering of this information can be further improved.
## Comment 12576
Date: 2009-10-24 23:08:55 +0200
From: @mlkersten
The SQL trace facility has been changed. The events are collected in BATs and printed after the result set has been sent. The table-based rendering of this information can be further improved.
## Comment 12577
Date: 2009-10-27 14:30:04 +0100
From: @grobian
all formatting issues are resolved now the faulty trace renderer has been removed.
## Comment 12578
Date: 2009-10-29 22:40:22 +0100
From: @mlkersten
The sql rendering is not yet fixed in the candidate. It does not properly distribute the space over the variable fields, nor split those over multiple lines as original intended and required.
## Comment 12579
Date: 2009-10-29 22:51:39 +0100
From: @mlkersten
Also the EXPLAIN functionality is gone, which is unacceptable!
sql>explain select * from tables;
0 tuples
## Comment 12580
Date: 2009-10-29 23:49:35 +0100
From: @drstmane
explain works fine for me with the CVS code base as of late afternoon (CET) today (Thu Oct 29 2009) of all three active branches ("Stable" Aug2009, "Candidate" Nov2009, "Current" trunk):
"Stable" Aug2009:
$ mserver5 --dbinit='include sql;'
MonetDB server v5.14.4, based on kernel v1.32.4
MonetDB/SQL module v2.32.3 loaded
$ mclient -lsql
sql>explain select * from tables;
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| function user.s0_1{autoCommit=true}():void; |
[...]
| end s0_1; |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
sql>
"Candidate" Nov2009:
$ mserver5 --dbinit='include sql;'
MonetDB server v5.16.0, based on kernel v1.34.0
MonetDB/SQL module v2.34.0 loaded
$ mclient -lsql
Welcome to mclient, the MonetDB/SQL interactive terminal
Database: MonetDB v5.16.0, 'demo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>explain select * from tables;
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| mal |
+====================================================================================================================================================================================================================================================+
| function user.s1_1{autoCommit=true}():void; |
[...]
| end s1_1; |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
251 tuples
sql>
"Current" CVS trunk:
$ mserver5 --dbinit='include sql;' --dbname=MyDemo
MonetDB server v5.17.0, based on kernel v1.35.0
MonetDB/SQL module v2.35.0 loaded
$ mclient -lsql
Welcome to mclient, the MonetDB/SQL interactive terminal
Database: MonetDB v5.17.0, 'MyDemo'
Type \q to quit, \? for a list of available commands
auto commit mode: on
sql>explain select * from tables;
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| mal |
+====================================================================================================================================================================================================================================================+
| function user.s1_1{autoCommit=true}():void; |
[...]
| end s1_1; |
+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
251 tuples
sql>
## Comment 12581
Date: 2009-11-16 22:33:37 +0100
From: @drstmane
What is the status of this one?
Is this still an issue?
Is there a test?
Is a test required?
If not, why not?
Thanks!
## Comment 12582
Date: 2009-11-16 22:44:43 +0100
From: @mlkersten
The -fsql option does not seem to properly grab the window width anymore in which it runs. Thereby, not respecting the maximal table rendering width. It is an issue for the user who sets their window size too narrow.
Testing is by visual inspection on a window.
As a rendering issue it is not critical.
## Comment 12583
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2881239 at http://sourceforge.net/support/tracker.php?aid=2881239
## Comment 17934
Date: 2012-11-12 21:35:12 +0100
From: @mlkersten
This bug can be closed. No special issues encountered in mclient rendering.
| SQL: mclient formatting issues | https://api.github.com/repos/MonetDB/MonetDB/issues/2227/comments | 0 | 2020-11-30T10:29:00Z | 2024-06-27T11:42:17Z | https://github.com/MonetDB/MonetDB/issues/2227 | 753,354,827 | 2,227 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-15 01:48:03 +0200
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2009-10-22 05:14:55 +0200
## Comment 12562
Date: 2009-10-15 13:48:03 +0200
From: @swingbit
On the website documentation, in the 'Syntax' page, table about operator precedences, this line appears:
LIKE ILIKE SIMILAR string pattern matching
However, SIMILAR is not a recognised keyword.
## Comment 12563
Date: 2009-10-22 17:14:54 +0200
From: @sjoerdmullender
I removed SIMILAR from the page. The website is being rebuilt.
## Comment 12564
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2879833 at http://sourceforge.net/support/tracker.php?aid=2879833
| SQL: SIMILAR keyword does not exist | https://api.github.com/repos/MonetDB/MonetDB/issues/2226/comments | 0 | 2020-11-30T10:28:57Z | 2024-06-27T11:42:16Z | https://github.com/MonetDB/MonetDB/issues/2226 | 753,354,778 | 2,226 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-15 01:36:07 +0200
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2009-10-27 02:31:54 +0100
## Comment 12558
Date: 2009-10-15 13:36:07 +0200
From: @swingbit
On the website, the following string operations are shown:
string_funcs:
SUBSTRING ( scalar_exp FROM scalar_exp FOR scalar_exp )
| SUBSTRING ( scalar_exp, scalar_exp, scalar_exp )
| SUBSTRING ( scalar_exp FROM scalar_exp )
| SUBSTRING ( scalar_exp, scalar_exp )
| SUBSTRING ( scalar_exp <int_value> scalar_exp )
| scalar_exp CONCATSTRING scalar_exp
However,
scalar_exp CONCATSTRING scalar_exp
doesn't appear to be valid.
Instead,
concat(scalar_exp, scalar_exp)
seems to d the job.
## Comment 12559
Date: 2009-10-15 13:42:22 +0200
From: @swingbit
After talking to Fabian, I learned that CONCATSTRING is defined as ||.
But how am I (as a user) supposed to know that?
So, the real problem of this bug report is that documentation on web is not incorrect, but just incomplete (also in many other points).
Making a documentation out of sources can be ok, but then it must be complete.
## Comment 12560
Date: 2009-10-22 17:38:36 +0200
From: @sjoerdmullender
I fixed the documentation in CVS by replacing CONCATSTRING with '||'. The remaining question is, do we need to explain that || is string concatenation?
## Comment 12561
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2879823 at http://sourceforge.net/support/tracker.php?aid=2879823
| SQL: incomplete documentation | https://api.github.com/repos/MonetDB/MonetDB/issues/2225/comments | 0 | 2020-11-30T10:28:53Z | 2024-06-27T11:42:15Z | https://github.com/MonetDB/MonetDB/issues/2225 | 753,354,734 | 2,225 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-14 08:04:41 +0200
From: Guillaume Theoret <<smokinn>>
To: @njnes
Version: -- development
Last updated: 2009-11-22 10:08:35 +0100
## Comment 12548
Date: 2009-10-14 20:04:41 +0200
From: Guillaume Theoret <<smokinn>>
It seems I can consistently crash MonetDB by running inserts in a while loop.
I have a script that reads 7.5MM rows from mysql and runs the inserts on MonetDB. After about 24 hours the database segfaults.
The messages my scripts output before crashing
Run 1:
6380000 done - 84.2207% in 86083.58 (0.0109 avg)
Segmentation fault
Run 2:
6380000 done - 84.2207% in 85957.17 (0.0107 avg)
Segmentation fault (core dumped)
I also log all get_last_error messages if there are any and got these two messages just before the crash:
MALException:!ERROR: HEAPextend: failed to extend to 244108529 for 07/744theap
MALException:!ERROR: HEAPextend: failed to extend to 244108529 for 07/744theap
On the second run I installed Apport to get a dump that I've attached.
I'm running Ubuntu 9.04 Jaunty on a 32bit machine with 2GB of ram. I compiled from the bz2 tarball linked here: http://monetdb.cwi.nl/projects/monetdb//Download/ ( http://monetdb.cwi.nl/downloads/sources/Aug2009-SP1/MonetDB-Aug2009-SuperBall-SP1.tar.bz2 ) and the crash occurs both when compiling with and without optimizations and with and without debug.
guillaume@dev3:~$ gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.3.3-5ubuntu4' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --enable-nls --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3 --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc --enable-mpfr --enable-targe1970-01-01 01:00:00 +0100all --with-tune=generic --enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4)
guillaume@dev3:~$ bison -V
bison (GNU Bison) 2.3
guillaume@dev3:~$ yacc -V
bison (GNU Bison) 2.3
guillaume@dev3:~$ autoconf -V
autoconf (GNU Autoconf) 2.63
guillaume@dev3:~$ automake --version
automake (GNU automake) 1.10.2
guillaume@dev3:~$ libtool --version
ltmain.sh (GNU libtool) 2.2.6
The attached tarball also contains the script I was running.
Thanks,
Guillaume
Edit: I've tried attaching the file but sourceforge keeps telling me I haven't chosen a group when I have. I'm going to submit without the file and try to add the file later.
## Comment 12549
Date: 2009-10-14 20:12:28 +0200
From: Guillaume Theoret <<smokinn>>
Sourceforge refuses to let me upload a file. It says success but nothing happens. I've uploaded the file here:
http://smokinn.com/files/monetdb_crash.tar.gz
## Comment 12550
Date: 2009-10-14 20:33:00 +0200
From: @drstmane
While indeed MonetDB should not segfault (will have to investigate and fix that), I have two comments / questions:
1)
How wide is your 7.5M row table (number and type of columns), i.e., how much data do you try to load in total?
MonetDB might just run out of address space on your 32-bit system.
How big was mserver5 just before crashing?
2)
Would it be an option for you to have MySQL dump the table into a CSV file, and then bulk-load the data from there into MonetDB using COPY INTO?
In MonetDB, bulk-loading should be (much) faster than individual insert statements ...
## Comment 12551
Date: 2009-10-14 21:29:24 +0200
From: Guillaume Theoret <<smokinn>>
I will run it again and check memory usage before it crashes.
My use case is ~10-15k inserts/updates by cron job every 15 minutes with a few (< 250-500 / 15 min) sporadic inserts at any time. I could probably rewrite the cron job to do a batch insert rather than sequential inserts.
As for how wide the table is, this is the table definition:
CREATE TABLE test.aggregated_detail_data_2009 (
date_added int NOT NULL,
hash_key char(32) NOT NULL,
landing_page int NOT NULL,
domain int NOT NULL,
ad_domain int NOT NULL,
ad_unit int NOT NULL,
ad_path int NOT NULL,
referer_domain int NOT NULL,
referer_path int NOT NULL,
campaign_id int DEFAULT NULL,
program_id int DEFAULT NULL,
affiliate_id int NOT NULL DEFAULT '0',
sub_campaign int NOT NULL,
os int NOT NULL,
os_version int NOT NULL,
browser int NOT NULL,
browser_version int NOT NULL,
search_engine int NOT NULL,
search_keyword int NOT NULL,
traffic_type int NOT NULL,
country_code char(2) NOT NULL,
flash_version_major int NOT NULL,
flash_version int NOT NULL,
is_member int DEFAULT NULL,
member_id int NOT NULL,
payout_type int NOT NULL,
payout decimal(14,8) NOT NULL,
payout_units int NOT NULL,
num_visits int NOT NULL,
num_unique_visits int NOT NULL,
num_impressions int NOT NULL,
num_unique_impressions int NOT NULL,
num_clicks int NOT NULL,
num_unique_clicks int NOT NULL,
sum_time_on_site int NOT NULL,
sum_page_views int NOT NULL,
num_bounce_visits int NOT NULL,
num_joins int NOT NULL,
num_attempts_step1 int NOT NULL,
num_attempts_step2 int NOT NULL,
num_premium_upgrades int NOT NULL,
membership_id int NOT NULL,
movie_id int NOT NULL,
stop_reason int NOT NULL,
stop_note int NOT NULL,
num_premium_stops int NOT NULL,
num_premium_stops_for_percent int NOT NULL,
num_premium_starts int NOT NULL,
num_running_premium int NOT NULL,
num_running_free int NOT NULL,
num_running_overdue int NOT NULL,
num_vod int NOT NULL,
sum_vod_revenues decimal(10,2) NOT NULL,
sum_vod_royalties decimal(10,2) NOT NULL,
num_vod_refunds int NOT NULL,
sum_vod_refunds decimal(10,2) NOT NULL,
num_dto int NOT NULL,
sum_dto_revenues decimal(10,2) NOT NULL,
sum_dto_royalties decimal(10,2) NOT NULL,
num_dto_refunds int NOT NULL,
sum_dto_refunds decimal(10,2) NOT NULL,
num_svod int NOT NULL,
sum_svod_revenues decimal(10,2) NOT NULL,
sum_svod_royalties decimal(10,2) NOT NULL,
num_svod_refunds int NOT NULL,
sum_svod_refunds decimal(10,2) NOT NULL,
num_affiliate_sales int NOT NULL,
sum_affiliate_payouts decimal(10,2) DEFAULT NULL,
sum_cpc_payouts decimal(16,8) NOT NULL,
sum_cpm_payouts decimal(16,8) NOT NULL,
signup_flow int NOT NULL,
CONSTRAINT hash_key_detailed UNIQUE (hash_key,date_added)
);
## Comment 12552
Date: 2009-10-14 22:14:21 +0200
From: @drstmane
These are 71 columns most of them int or decimal, i.e., 4 byte wide, one being a char(32); (70*4B+32B)*7.5M = 2340MB ~= 2.3GB.
This comes close to the practical limit on 32-bit systems; surely when considering address space fragmentation and the fact the 32-bit systems usually do not allow processes to use the full (theoretical) address space of 4GB ...
## Comment 12553
Date: 2009-10-14 22:40:14 +0200
From: Guillaume Theoret <<smokinn>>
So I ran out of addressable memory space, thanks.
Does monetdb need the addressable memory space globally or per table?
Basically, if instead of a single table with 7.5MM rows, I had 30 tables of 250k rows or 4 tables of 1875000 rows would I still have the problem? The 7.5MM rows was 1 month worth of data so I'd split it by day or week.
Thanks
## Comment 12554
Date: 2009-10-15 09:17:21 +0200
From: @drstmane
Well, there is not proof, yet, but there is a high chance that you simply ran out of address space ...
In MonetDB, each column that is accessed is entirely loaded/mapped into the address space. Hence, all columns that are required during query processing need to fit into the address space. For insert and bulk-loads, this means that the whole table (all columns) need to fit into the address space. Of course, MonetDB also need extra space, e.g., for temporary data and intermediate results.
Thus, splitting your large table into multiple smaller ones should allow you to load each smaller table individually, as well as to query each table individually. Also querying multiple/all tables concurrently (e.g., an on-the-fly union of them) might work, provided you only use a small subset of all columns per query.
Alternatively, you might want to consider moving to a 64-bit system ...
## Comment 12555
Date: 2009-10-15 16:46:51 +0200
From: Guillaume Theoret <<smokinn>>
The production server is 64 bit but my test machine isn't.
I tried creating individual tables but it segfaulted again after inserting ~9000 rows.
The program creates tablename_day_num and tablename_week_num as needed and this is my output:
Inserting
Creating _day_89 for Tue, 31 Mar 2009 00:00:00 -0400
Creating _week_14 for Tue, 31 Mar 2009 00:00:00 -0400
Creating _day_90 for Wed, 01 Apr 2009 00:00:00 -0400
Creating _day_91 for Thu, 02 Apr 2009 00:00:00 -0400
Creating _day_92 for Fri, 03 Apr 2009 00:00:00 -0400
[...]
Creating _day_158 for Mon, 08 Jun 2009 00:00:00 -0400
Creating _week_24 for Mon, 08 Jun 2009 00:00:00 -0400
Creating _day_159 for Tue, 09 Jun 2009 00:00:00 -0400
Creating _day_160 for Wed, 10 Jun 2009 00:00:00 -0400
3000 done - 0.0396% in 31.06 (0.014 avg)
4000 done - 0.0528% in 39.28 (0.0082 avg)
5000 done - 0.066% in 48.28 (0.009 avg)
6000 done - 0.0792% in 54.48 (0.0062 avg)
7000 done - 0.0924% in 60.62 (0.0061 avg)
8000 done - 0.1056% in 67.05 (0.0064 avg)
9000 done - 0.1188% in 73.51 (0.0065 avg)
Segmentation fault (core dumped)
This time mserver5 wasn't using a lot of memory when it segfaulted (according to top).
I can upload another dump if it's useful.
## Comment 12556
Date: 2009-11-22 22:08:35 +0100
From: @njnes
again 32 bit adressing problems. We are working on to improve this problem, ie give proper errors (no crashes).
## Comment 12557
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2879117 at http://sourceforge.net/support/tracker.php?aid=2879117
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| Consistent segmentation fault | https://api.github.com/repos/MonetDB/MonetDB/issues/2224/comments | 0 | 2020-11-30T10:28:48Z | 2024-06-28T13:21:46Z | https://github.com/MonetDB/MonetDB/issues/2224 | 753,354,665 | 2,224 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-14 06:09:35 +0200
From: Wouter Alink <<alink>>
To: @njnes
Version: -- development
Last updated: 2009-11-22 09:27:59 +0100
## Comment 12544
Date: 2009-10-14 18:09:35 +0200
From: Wouter Alink <<alink>>
(Aug2009, todays checkout)
The following script returns a mal-error.
CREATE TABLE a (name VARCHAR(10));
CREATE TABLE b (name VARCHAR(10));
INSERT INTO a VALUES ('a'),('b');
INSERT INTO b VALUES ('a'),('b');
SELECT a.name as x, b.name as y FROM a,b WHERE a.name LIKE b.name;
Yields:
!TypeException:user.s0_2[42]:'algebra.leftjoin' undefined in: _55:any := algebra.leftjoin(_54:bat[:oid,:void], _27:bat[:oid,:str], _50:lng)
!SQLException:SQLengine:Program contains errors
0 tuples
This does not happen when only selecting 1 column, as in:
SELECT a.name as x FROM a,b WHERE a.name LIKE b.name;
## Comment 12545
Date: 2009-11-15 16:55:38 +0100
From: Wouter Alink <<alink>>
added test leftjoin_undefined.SF-2879011 in src/test/BugTracker-2009. Test still fails.
## Comment 12546
Date: 2009-11-22 21:27:59 +0100
From: @njnes
fixed by properly implementing join based on like expressions (ie crossproduct + filter on like)
## Comment 12547
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2879011 at http://sourceforge.net/support/tracker.php?aid=2879011
| SQL: leftjoin undefined | https://api.github.com/repos/MonetDB/MonetDB/issues/2223/comments | 0 | 2020-11-30T10:28:45Z | 2024-06-27T11:42:13Z | https://github.com/MonetDB/MonetDB/issues/2223 | 753,354,614 | 2,223 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-14 06:06:39 +0200
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-11-22 09:33:38 +0100
## Comment 12538
Date: 2009-10-14 18:06:39 +0200
From: @swingbit
create table a (x varchar(10);
insert into a values ('aaa');
create table b (x varchar(10);
insert into b values ('aaa');
insert into b values ('aAa');
insert into b values ('aA');
create ab as select a.x as x, b.x as y from a,b;
select x from ab where x LIKE y;
Returns the correct result:
+-------+
| x |
+=======+
| aaa |
+-------+
1 tuple
However, the case insensitive version returns the same result as LIKE:
select x from ab where x ILIKE y;
+-------+
| x |
+=======+
| aaa |
+-------+
1 tuple
It misses 'aAa'
## Comment 12539
Date: 2009-10-27 15:12:41 +0100
From: @grobian
the unexpanded (view-less) version exhibits the same bug.
## Comment 12540
Date: 2009-10-29 14:22:23 +0100
From: @grobian
case reduced to
SELECT 'a' ILIKE 'A'; (fixed, test pending)
the BAT version is still not fixed though.
## Comment 12541
Date: 2009-10-29 14:43:21 +0100
From: @grobian
The problem seems unrelated to ilike to me, but in the MAL plan:
function user.s9_0{autoCommit=true}():void;
_2:bat[:oid,:str] := sql.bind("sys","a","x",0);
_7:bat[:oid,:str] := sql.bind("sys","a","x",2);
_9 := algebra.kdifference(_2,_7);
_2:bat[:oid,:str] := nil:BAT;
_10 := algebra.kunion(_9,_7);
_9 := nil:BAT;
_7:bat[:oid,:str] := nil:BAT;
_11:bat[:oid,:str] := sql.bind("sys","a","x",1);
_13 := algebra.kunion(_10,_11);
_10 := nil:BAT;
_11:bat[:oid,:str] := nil:BAT;
_14:bat[:oid,:oid] := sql.bind_dbat("sys","a",1);
_15 := bat.reverse(_14);
_14:bat[:oid,:oid] := nil:BAT;
_16 := algebra.kdifference(_13,_15);
_13 := nil:BAT;
_15 := nil:BAT;
_17 := batcalc.str(_16);
_18:bat[:oid,:str] := sql.bind("sys","b","x",0);
_20:bat[:oid,:str] := sql.bind("sys","b","x",2);
_21 := algebra.kdifference(_18,_20);
_18:bat[:oid,:str] := nil:BAT;
_22 := algebra.kunion(_21,_20);
_21 := nil:BAT;
_20:bat[:oid,:str] := nil:BAT;
_23:bat[:oid,:str] := sql.bind("sys","b","x",1);
_24 := algebra.kunion(_22,_23);
_22 := nil:BAT;
_23:bat[:oid,:str] := nil:BAT;
_25:bat[:oid,:oid] := sql.bind_dbat("sys","b",1);
_26 := bat.reverse(_25);
_25:bat[:oid,:oid] := nil:BAT;
_27 := algebra.kdifference(_24,_26);
_24 := nil:BAT;
_26 := nil:BAT;
_28 := batcalc.str(_27);
_27 := nil:BAT;
_29 := bat.mirror(_17);
_30 := bat.mirror(_28);
_31 := algebra.join(_29,_30);
_29 := nil:BAT;
_30 := nil:BAT;
_32 := algebra.markH(_31,0@0);
_34 := algebra.markT(_31);
_31 := nil:BAT;
_35 := bat.reverse(_34);
_34 := nil:BAT;
_36 := algebra.join(_35,_17);
_35 := nil:BAT;
_17 := nil:BAT;
_37 := algebra.join(_32,_28);
_28 := nil:BAT;
_104 := bat.new(nil:oid,nil:bit);
barrier (_108,_109,_110) := bat.newIterator(_36);
_112 := algebra.find(_37,_109);
_114 := str.ilike(_110,_112);
bat.insert(_104,_109,_114);
redo (_108,_109,_110) := bat.hasMoreElements(_36);
exit (_108,_109,_110);
_38:bat[:oid,:bit] := _104;
_36 := nil:BAT;
_37 := nil:BAT;
_41 := algebra.uselect(_38,true);
_38:bat[:oid,:bit] := nil:BAT;
_42 := bat.reverse(_41);
_41 := nil:BAT;
_43 := algebra.join(_42,_32);
_42 := nil:BAT;
_32 := nil:BAT;
_44 := bat.reverse(_43);
_43 := nil:BAT;
_45 := algebra.markT(_44,0@0);
_44 := nil:BAT;
_46 := bat.reverse(_45);
_45 := nil:BAT;
_47 := algebra.leftjoin(_46,_16,nil:lng);
_46 := nil:BAT;
_16 := nil:BAT;
_49 := sql.resultSet(1,1,_47);
sql.rsColumn(_49,"sys.a","x","varchar",10,0,_47);
_47 := nil:BAT;
_54 := io.stdout();
sql.exportResult(_54,_49);
end s9_0;
in particular this line:
_31 := algebra.join(_29,_30);
generates a join between sys.a.x and sys.b.x tables, leaving only the entry for 'aaa' around. This subresult is then used to reconstruct _36 and _37 from the full columns, making the iterator only looping over 'aaa', making the entire str.ilike pretty useless.
I cannot fix this.
## Comment 12542
Date: 2009-11-22 21:33:38 +0100
From: @njnes
fixed by properly implementing a crossproduct + like filter
( test from the like_bug.SF-2878994.sql)
## Comment 12543
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2879008 at http://sourceforge.net/support/tracker.php?aid=2879008
| SQL: WHERE A.x LIKE A.y misses results | https://api.github.com/repos/MonetDB/MonetDB/issues/2222/comments | 0 | 2020-11-30T10:28:40Z | 2024-06-27T11:42:12Z | https://github.com/MonetDB/MonetDB/issues/2222 | 753,354,548 | 2,222 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-14 06:01:58 +0200
From: Wouter Alink <<alink>>
To: @njnes
Version: -- development
Last updated: 2009-11-11 07:40:31 +0100
## Comment 12535
Date: 2009-10-14 18:01:58 +0200
From: Wouter Alink <<alink>>
(Aug2009, todays checkout)
The script below generates a table with two 'name' columns.
Besides the duplicate column names, it also yields the wrong result (expected 4 tuples: a-a, a-b, b-a, and b-b)
I don't know whether these two bugs are related, or that they should be reported seperately.
CREATE TABLE a (name VARCHAR(10));
CREATE TABLE b (name VARCHAR(10));
INSERT INTO a VALUES ('a'),('b');
INSERT INTO b VALUES ('a'),('b');
CREATE TABLE ab AS SELECT * FROM a,b WITH DATA;
SELECT * FROM ab;
+-------+-------+
| name | name |
+=======+=======+
| a | a |
| a | a |
| b | b |
| b | b |
| a | a |
| b | b |
| a | a |
| b | b |
+-------+-------+
8 tuples
## Comment 12536
Date: 2009-11-11 19:40:26 +0100
From: @njnes
added test to create_table_dup_name.SF-2879005
fixed by disallowing duplicate column names
## Comment 12537
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2879005 at http://sourceforge.net/support/tracker.php?aid=2879005
| SQL: duplicate column name | https://api.github.com/repos/MonetDB/MonetDB/issues/2221/comments | 0 | 2020-11-30T10:28:38Z | 2024-06-27T11:42:11Z | https://github.com/MonetDB/MonetDB/issues/2221 | 753,354,518 | 2,221 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-14 05:56:29 +0200
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-11-17 12:07:37 +0100
## Comment 12531
Date: 2009-10-14 17:56:29 +0200
From: @swingbit
create table a (x varchar(10);
insert into a values ('aaa');
create table b (x varchar(10);
insert into b values ('aaa');
insert into b values ('aAa');
insert into b values ('aA');
select a.x from a,b where a.x LIKE b.x;
Returns no results (it should have returned 'aaa')
## Comment 12532
Date: 2009-10-29 14:23:57 +0100
From: @grobian
hmmm, cannot reproduce this on Aug2009 branch
## Comment 12533
Date: 2009-11-17 00:07:37 +0100
From: @drstmane
activated already existing test in sql/src/test/BugTracker-2009/Tests/like_bug.SF-2878994.sql
Appears to work fine in Nov2009 branch.
Closing.
## Comment 12534
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2878994 at http://sourceforge.net/support/tracker.php?aid=2878994
| SQL: WHERE A.x LIKE B.x does not work | https://api.github.com/repos/MonetDB/MonetDB/issues/2220/comments | 0 | 2020-11-30T10:28:35Z | 2024-06-28T13:21:45Z | https://github.com/MonetDB/MonetDB/issues/2220 | 753,354,486 | 2,220 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-12 03:21:56 +0200
From: Maurice van Keulen <<mvankeulen>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-11-15 03:31:41 +0100
## Comment 12526
Date: 2009-10-12 15:21:56 +0200
From: Maurice van Keulen <<mvankeulen>>
(Aug2009 stable; Linux)
The query below gives a type error: binding sequence in a for clause has static type `empty'. It gives the same error for both expressions $error1 and $error2. The error goes away if you replace $wsa by $wsb while that should affect the result.
let $wsa := (
<r1><v>1</v><v>2</v></r1>
,<r2><v>1</v><v>2</v></r2>
)
let $wsb := (
<r1><v>1</v><v>2</v></r1>
)
let $error1 := $wsa/v[parent::r1]
let $error2 := $wsa/self::r1/v
return $error1
## Comment 12527
Date: 2009-10-12 16:04:36 +0200
From: Jan Rittinger <<jan.rittinger>>
problem already known...
see http://sourceforge.net/tracker/?func=detail&aid=2211565&group_id=56967&atid=482468
## Comment 12528
Date: 2009-11-12 10:44:49 +0100
From: @peterboncz
Jan, that bug is closed, so it should not be? Is this fixable?
## Comment 12529
Date: 2009-11-15 15:31:41 +0100
From: Jan Rittinger <<jan.rittinger>>
I disabled the type disjointness test for path steps. Now this query compiles fine again.
## Comment 12530
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2877044 at http://sourceforge.net/support/tracker.php?aid=2877044
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: binding sequence in a for clause has static type `empty' | https://api.github.com/repos/MonetDB/MonetDB/issues/2219/comments | 0 | 2020-11-30T10:28:32Z | 2024-06-27T11:42:09Z | https://github.com/MonetDB/MonetDB/issues/2219 | 753,354,436 | 2,219 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-12 11:07:53 +0200
From: Maurice van Keulen <<mvankeulen>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-11-12 06:32:50 +0100
## Comment 12522
Date: 2009-10-12 11:07:53 +0200
From: Maurice van Keulen <<mvankeulen>>
("Aug2009" stable, Linux)
Elements without textnodes are not treated correctly in predicates. The query below gives the error "We do not support the value NaN.". If you modify the query to return $noerror or $guarded, it works fine.
declare function ltnum($e as element(), $num as xs:double) as xs:boolean
{ if (empty($e/text())) then false() else ($e > $num) };
let $elems := (<a/>,<b/>,<c>20</c>)
let $error := $elems[. > 5]
let $noerror := for $e in $elems return if (empty($e/text())) then () else $e[. > 5]
let $guarded := $elems[ltnum(.,5)]
return $error
## Comment 12523
Date: 2009-10-12 14:27:16 +0200
From: Jan Rittinger <<jan.rittinger>>
We cannot neither handle NaN values in the algebra nor on the MIL level. On the MIL level we have no runtime support for Nan. On the algebra level this would require that the following snippets 'not(23 > <a/>)' and '23 < </a>' result in 'true' and 'false', respectively. For the algebra both snippets result in the same plan and we give an error at runtime if we see such behavior.
BTW: All your variants fail if you replace '<a/>' by '<a>no number</a>'.
To avoid this problem we added a rewrite that can cope with fn:number()---the replacement for the atomization---on equality predicates.
## Comment 12524
Date: 2009-10-12 18:20:02 +0200
From: Jan Rittinger <<jan.rittinger>>
I just checked in a possible fix in the CVS HEAD (-- in my eyes its more an extension than a fix). If testing shows no problems we might think about back-porting it to the Stable branch.
## Comment 12525
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2876948 at http://sourceforge.net/support/tracker.php?aid=2876948
| PF: error "We do not support the value NaN" | https://api.github.com/repos/MonetDB/MonetDB/issues/2218/comments | 0 | 2020-11-30T10:28:29Z | 2024-06-27T11:42:08Z | https://github.com/MonetDB/MonetDB/issues/2218 | 753,354,405 | 2,218 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-11 08:28:33 +0200
From: winston <<wwinston>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-10-31 04:11:36 +0100
## Comment 12518
Date: 2009-10-11 20:28:33 +0200
From: winston <<wwinston>>
See the MonetDB4 documentation: XQuery Documentation -> 3.1 The Mapi Client Utility -> 3.1.2 Timing
The "Timer" value is not defined in the documentation, but what does it measure?
When I run an mclient query using the -t option, I get numbers for the following line items:
For example, query command:
mclient -t -lx -f none q0.xq
results in:
Trans 16.000 msec
Shred 0.000 msec
Query 31.000 msec
Print 0.000 msec
Timer 60.211 msec
So what does "Timer" measure? Is it the total cost, but it also appears to measure something beyond query too?
=x=x=
OS=Windows XP
2GB RAM
MonetDB4 installed from latest stable build, August 2009 version.
## Comment 12519
Date: 2009-10-22 17:40:43 +0200
From: @sjoerdmullender
Timer is the wall clock time, i.e. the real time you have to wait for the query to be executed.
I guess we should document this somewhere.
## Comment 12520
Date: 2009-10-31 16:11:33 +0100
From: winston <<wwinston>>
Thank you.
## Comment 12521
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2876590 at http://sourceforge.net/support/tracker.php?aid=2876590
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.
| What does the value "Timer" measure? | https://api.github.com/repos/MonetDB/MonetDB/issues/2217/comments | 0 | 2020-11-30T10:28:26Z | 2024-06-28T13:22:51Z | https://github.com/MonetDB/MonetDB/issues/2217 | 753,354,373 | 2,217 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-07 05:13:46 +0200
From: @swingbit
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-10-07 06:01:39 +0200
## Comment 12515
Date: 2009-10-07 17:13:46 +0200
From: @swingbit
On the Nov2009 branch, the following query fails :
for $i in doc("/ufs/roberto/lhm_code/HyServer/console/doclist.xml")//doc return $i
where the file doclist.xml is:
<docs>
<doc wf="true">ALPA-406/EP/000001/03/03/03/EP-1030303-A2.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/07/EP-1030307-A1.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/07/EP-1030307-B1.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/80/EP-1030380-B1.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/80/EP-1030380-A2.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/52/EP-1030352-A2.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/86/EP-1030386-A1.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/77/EP-1030377-A2.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/81/EP-1030381-B1.xml</doc>
<doc wf="true">ALPA-406/EP/000001/03/03/81/EP-1030381-A1.xml</doc>
</docs>
Output:
Mserver: /ufs/roberto/lhm_code/HyServer/MonetDB/MonetDB.stable/src/pathfinder/compiler/mil/milgen.brg:2619: reduce: Assertion `rule' failed.
## Comment 12516
Date: 2009-10-07 18:01:23 +0200
From: @swingbit
There is something wrong in the code itself, so this bug is closed as invalid.
The problem was about incorrect dependencies, which makes it necessary to recompile from scratch (delete the build directory and recompile)
## Comment 12517
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2874154 at http://sourceforge.net/support/tracker.php?aid=2874154
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-xquery@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| PF: 'for $i in doc()' broken | https://api.github.com/repos/MonetDB/MonetDB/issues/2216/comments | 0 | 2020-11-30T10:28:23Z | 2024-06-28T13:22:50Z | https://github.com/MonetDB/MonetDB/issues/2216 | 753,354,323 | 2,216 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-07 01:32:00 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-11-11 06:33:40 +0100
## Comment 12512
Date: 2009-10-07 13:32:00 +0200
From: @skinkie
select (select 1) * (select vettecrash from tables);
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f0928f1b6f0 (LWP 22280)]
0x00007f09169c5971 in list_select (l=0x0, key=0x1b92938,
cmp=0x7f091698a3f4 <exp_is_correlation>, dup=0x7f0916988710 <exp_dup>)
at ../../../src/common/sql_list.mx:282
282 list *res = list_create(l->destroy);
I would expect the same error as in:
select vettecrash from tables;
!SELECT: identifier 'vettecrash' unknown
After limiting the problem to a smaller query:
>select (select vettecrash from tables);
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fb14e9396f0 (LWP 22409)]
0x00007fb13c3e2ba0 in sql_ref_inc (r=0x0) at ../../../src/common/sql_mem.mx:44
44 assert(r->refcnt > 0);
## Comment 12513
Date: 2009-11-11 18:33:39 +0100
From: @njnes
added test segv_for_unknown_identifier_in_subquery.SF-2874045.sql
Fixed by more defensive list_select.
## Comment 12514
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2874045 at http://sourceforge.net/support/tracker.php?aid=2874045
| SQL: segv for unknown identifier in subquery | https://api.github.com/repos/MonetDB/MonetDB/issues/2215/comments | 0 | 2020-11-30T10:28:19Z | 2024-06-27T11:42:05Z | https://github.com/MonetDB/MonetDB/issues/2215 | 753,354,278 | 2,215 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-07 12:20:21 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
CC: @mlkersten
Last updated: 2012-11-12 21:37:13 +0100
## Comment 12510
Date: 2009-10-07 00:20:21 +0200
From: @skinkie
The following output I saw on my screen; I don't know how to reproduce it yet. And this not the latest head. Still I hope the backtrace could be useful to debug the issue. I am running the database now in valgrind, and as far as I know only one query is fired upon it.
skinkie@productie ~ $ /opt/monetdb-head/bin/mserver5 --dbinit="include sql; sql.start();" --dbname=monitor --readonly --set mapi_port=50001
MonetDB server v5.17.0, based on kernel v1.35.0
Serving database 'monitor', using 4 threads
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
Detected 3.856 GiB (4140695552 bytes) main-memory.
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
Visit http://monetdb.cwi.nl/ for further information
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:50001/
MonetDB/SQL module v2.35.0 loaded
>select * from sta^?^?^?^?^?^?^?*** glibc detected *** /opt/monetdb-head/bin/mserver5: double free or corruption (!prev): 0x00000000064de650 ***
======= Backtrace: =========
/lib/libc.so.6[0x7fee456eb258]
/lib/libc.so.6(cfree+0x6c)[0x7fee456efd0c]
/opt/monetdb-head/lib/libbat.so.1[0x7fee478dc283]
/opt/monetdb-head/lib/libbat.so.1(GDKfree+0x46)[0x7fee478dc30c]
/opt/monetdb-head/lib/libbat.so.1(HEAPfree+0x39)[0x7fee478192d0]
/opt/monetdb-head/lib/libbat.so.1(BATclear+0x4fd)[0x7fee47a875fd]
/opt/monetdb-head/lib/MonetDB5/lib/lib_sql.so[0x7fee36332d7b]
/opt/monetdb-head/lib/MonetDB5/lib/lib_sql.so[0x7fee36332de6]
/opt/monetdb-head/lib/MonetDB5/lib/lib_sql.so(sql_trans_clear_table+0xef)[0x7fee36324c6d]
/opt/monetdb-head/lib/MonetDB5/lib/lib_sql.so(sql_session_reset+0x89)[0x7fee363276a9]
/opt/monetdb-head/lib/MonetDB5/lib/lib_sql.so(mvc_reset+0xe2)[0x7fee362df592]
/opt/monetdb-head/lib/MonetDB5/lib/lib_sql.so(SQLinitClient+0x168)[0x7fee36299c20]
/opt/monetdb-head/lib/libmonetdb5.so.5[0x7fee483b9668]
/opt/monetdb-head/lib/libmonetdb5.so.5[0x7fee483b96d1]
/opt/monetdb-head/lib/libmonetdb5.so.5(runScenario+0x3e)[0x7fee483b9989]
/opt/monetdb-head/lib/libmonetdb5.so.5(MSserveClient+0x108)[0x7fee4837473d]
/lib/libpthread.so.0[0x7fee4660f2c7]
/lib/libc.so.6(clone+0x6d)[0x7fee4574938d]
======= Memory map: ========
00400000-00405000 r-xp 00000000 08:03 69774938 /opt/monetdb-head/bin/mserver5
00604000-00605000 r--p 00004000 08:03 69774938 /opt/monetdb-head/bin/mserver5
00605000-00606000 rw-p 00005000 08:03 69774938 /opt/monetdb-head/bin/mserver5
00606000-00610000 rw-p 00000000 00:00 0
01aff000-06c44000 rw-p 00000000 00:00 0 [heap]
...
## Comment 12511
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2873758 at http://sourceforge.net/support/tracker.php?aid=2873758
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 13965
Date: 2010-05-04 10:32:52 +0200
From: @grobian
We need more information to be able to debug this. Please reopen if you have that information.
## Comment 17935
Date: 2012-11-12 21:37:13 +0100
From: @mlkersten
Too old to consider relevant given the information provided.
The reference bug report is gone.
| Double free error | https://api.github.com/repos/MonetDB/MonetDB/issues/2214/comments | 0 | 2020-11-30T10:28:16Z | 2024-06-28T13:22:49Z | https://github.com/MonetDB/MonetDB/issues/2214 | 753,354,222 | 2,214 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-06 06:26:14 +0200
From: Guillaume Theoret <<smokinn>>
To: @njnes
Version: -- development
Last updated: 2009-11-11 09:35:08 +0100
## Comment 12507
Date: 2009-10-06 18:26:14 +0200
From: Guillaume Theoret <<smokinn>>
When creating a unique constraint, if one of the columns is of type char, the unique constraint is ignored.
To reproduce:
ql>CREATE TABLE test.keytest (
more> date_added int NOT NULL,
more> hash_key char(32) NOT NULL,
more> dimension1 int NOT NULL,
more> dimension2 int NOT NULL,
more> metric1 int NOT NULL,
more> metric2 int NOT NULL,
more>
more> CONSTRAINT key_test UNIQUE (hash_key,date_added)
more>);
Operation successful
sql>insert into test.keytest (date_added, hash_key, dimension1,
dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2);
Rows affected 1
Timer 12.126 msec 0 rows
sql>insert into test.keytest (date_added, hash_key, dimension1,
dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2);
Rows affected 1
Timer 18.345 msec 0 rows
sql>select * from test.keytest;
select * from test.keytest;
+------------+----------------------------------+------------+------------+---------+---------+
| date_added | hash_key | dimension1 |
dimension2 | metric1 | metric2 |
+============+==================================+============+============+=========+=========+
| 1 | a | 1 |
1 | 2 | 2 |
| 1 | a | 1 |
1 | 2 | 2 |
+------------+----------------------------------+------------+------------+---------+---------+
2 tuples
Timer 1.997 msec 2 rows
sql>CREATE UNIQUE INDEX unique_key_test ON test.keytest (date_added, hash_key);
Operation successful
Timer 25.904 msec 2 rows
sql>insert into test.keytest (date_added, hash_key, dimension1,
dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2);
Rows affected 1
Timer 78.637 msec 2 rows
sql>insert into test.keytest (date_added, hash_key, dimension1,
dimension2, metric1, metric2) VALUES (1, 'a', 1, 1, 2, 2);
Rows affected 1
Timer 31.788 msec 2 rows
sql>select * from test.keytest;
select * from test.keytest;
+------------+----------------------------------+------------+------------+---------+---------+
| date_added | hash_key | dimension1 |
dimension2 | metric1 | metric2 |
+============+==================================+============+============+=========+=========+
| 1 | a | 1 |
1 | 2 | 2 |
| 1 | a | 1 |
1 | 2 | 2 |
| 1 | a | 1 |
1 | 2 | 2 |
| 1 | a | 1 |
1 | 2 | 2 |
+------------+----------------------------------+------------+------------+---------+---------+
4 tuples
Timer 18.083 msec 4 rows
Unique constraint on all int columns is not affected:
sql>CREATE TABLE test.keytest2 (
more> date_added int NOT NULL,
more> key int NOT NULL,
more> dimension1 int NOT NULL,
more> dimension2 int NOT NULL,
more> metric1 int NOT NULL,
more> metric2 int NOT NULL,
more>
more> CONSTRAINT key_test2 UNIQUE (key,date_added)
more>);
Operation successful
Timer 167.384 msec 0 rows
sql>insert into test.keytest2 (date_added, key, dimension1,
dimension2, metric1, metric2) VALUES (1, 1, 1, 1, 2, 2);
Rows affected 1
Timer 1.693 msec 0 rows
sql>insert into test.keytest2 (date_added, key, dimension1,
dimension2, metric1, metric2) VALUES (1, 1, 1, 1, 2, 2);
!SQLException:assert:INSERT INTO: UNIQUE constraint
'keytest2.key_test2' violated
0 tuples
Timer 66.634 msec 0 rows
sql>select * from test.keytest2;
select * from test.keytest2;
+------------+-------+------------+------------+---------+---------+
| date_added | key | dimension1 | dimension2 | metric1 | metric2 |
+============+=======+============+============+=========+=========+
| 1 | 1 | 1 | 1 | 2 | 2 |
+------------+-------+------------+------------+---------+---------+
## Comment 12508
Date: 2009-11-11 21:35:08 +0100
From: @njnes
added test unique_constraint_on_char.SF-2873564.sql
fix by fixing the hash computation. (it was computed on the pointer instead of on the value for strings)
## Comment 12509
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2873564 at http://sourceforge.net/support/tracker.php?aid=2873564
| Cannot create unique constraint on char column | https://api.github.com/repos/MonetDB/MonetDB/issues/2213/comments | 0 | 2020-11-30T10:28:12Z | 2024-06-27T11:42:03Z | https://github.com/MonetDB/MonetDB/issues/2213 | 753,354,178 | 2,213 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-05 04:20:46 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-10-05 09:37:03 +0200
## Comment 12504
Date: 2009-10-05 16:20:46 +0200
From: @romulogoncalves
The SQL file in attach crashes the mserver. The back trace of the crash is the following one.
It seems a infinite loop in the generation of the statement tree of Niels.
(gdb) bt
0 0x0000003830845882 in vfprintf () from /lib64/libc.so.6
1 0x00000038308715ba in vsnprintf () from /lib64/libc.so.6
2 0x000000383084ff13 in snprintf () from /lib64/libc.so.6
3 0x00007fffe2f2a7a7 in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x14d3778)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:479
4 0x00007fffe2f2f6ff in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1598be8)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1493
5 0x00007fffe2f2e911 in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1598fb8)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1324
6 0x00007fffe2f2f6ff in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1598d78)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1493
7 0x00007fffe2f2e911 in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1599148)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1324
8 0x00007fffe2f2f6ff in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1598f08)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1493
9 0x00007fffe2f2e911 in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x15992d8)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1324
10 0x00007fffe2f2f6ff in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1599098)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1493
11 0x00007fffe2f2e911 in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1599468)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1324
12 0x00007fffe2f2f6ff in _dumpstmt (sql=0x125be08, mb=0x13fb2b8, s=0x1599228)
at /ufs/goncalve/MonetDB/stable/sql/src/backends/monet5/sql_gencode.mx:1493
---Type <return> to continue, or q <return> to quit---
## Comment 12505
Date: 2009-10-05 21:36:53 +0200
From: @njnes
duplicate of 2102167 SQL: too may nested operators in algebra version
## Comment 12506
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2872948 at http://sourceforge.net/support/tracker.php?aid=2872948
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| nested operation crash | https://api.github.com/repos/MonetDB/MonetDB/issues/2212/comments | 0 | 2020-11-30T10:28:08Z | 2024-06-28T13:22:48Z | https://github.com/MonetDB/MonetDB/issues/2212 | 753,354,125 | 2,212 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-10-05 02:30:45 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-10-05 09:43:10 +0200
## Comment 12501
Date: 2009-10-05 14:30:45 +0200
From: @skinkie
CREATE TABLE "sys"."test" (
"date" TIMESTAMP
);
INSERT INTO test VALUES ('2000-01-01 01:00:00.000000');
The following query return in an error:
select extract(year from date) from test group by extract(year from date) limit 10;
syntax error, unexpected EXTRACT in: "select extract(year from date) from test group by extract"
While grouping over an alias in fact works:
select extract(year from date) as x from test group by x limit 10;
I would expect that the group by would allow the same kind of operations without the actual column.
## Comment 12502
Date: 2009-10-05 21:43:09 +0200
From: @njnes
We don't allow for expressions in the group by.
## Comment 12503
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2872902 at http://sourceforge.net/support/tracker.php?aid=2872902
| SQL: group by extract(day from date) fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2211/comments | 0 | 2020-11-30T10:28:02Z | 2024-06-28T13:22:48Z | https://github.com/MonetDB/MonetDB/issues/2211 | 753,354,049 | 2,211 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.