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: 2009-06-18 05:06:05 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-09-20 09:48:51 +0200
## Comment 11956
Date: 2009-06-18 17:06:05 +0200
From: @skinkie
(gdb) bt
0 0x0000000000000000 in ?? ()
1 0x00007feea4ba5495 in mvc_append_wrap (cntxt=0x605780, mb=0x2131828, stk=0x213e8c8, pci=0x21445a8) at ../../../../src/backends/monet5/sql.mx:1743
2 0x00007feeb671e4ec in runMALsequence (cntxt=0x605780, mb=0x2131828, startpc=1, stoppc=0, stk=0x213e8c8, env=0x0, pcicaller=0x0) at ../../../src/mal/mal_interpreter.mx:1766
3 0x00007feeb671601e in callMAL (cntxt=0x605780, mb=0x2131828, env=0x7feea4778e88, argv=0x7feea4778ed0, debug=0 '\0') at ../../../src/mal/mal_interpreter.mx:394
4 0x00007feea4bdee6a in SQLexecutePrepared (c=0x605780, be=0x20e5a38, q=0x21319d8) at ../../../../src/backends/monet5/sql_scenario.mx:1195
5 0x00007feea4bdf0d9 in SQLengineIntern (c=0x605780, be=0x20e5a38) at ../../../../src/backends/monet5/sql_scenario.mx:1248
6 0x00007feea4bdf5a0 in SQLengine (c=0x605780) at ../../../../src/backends/monet5/sql_scenario.mx:1358
7 0x00007feeb6757988 in runPhase (c=0x605780, phase=4) at ../../../src/mal/mal_scenario.mx:602
8 0x00007feeb6757b15 in runScenarioBody (c=0x605780) at ../../../src/mal/mal_scenario.mx:647
9 0x00007feeb6757ca9 in runScenario (c=0x605780) at ../../../src/mal/mal_scenario.mx:672
10 0x00007feeb6714019 in MSserveClient (dummy=0x605780) at ../../../src/mal/mal_session.mx:493
11 0x00007feeb49ddff7 in start_thread () from /lib/libpthread.so.0
12 0x00007feeb3b20f4d in clone () from /lib/libc.so.6
13 0x0000000000000000 in ?? ()
Database was started with readonly, copy into was used.
## Comment 11957
Date: 2009-08-06 15:58:18 +0200
From: @mlkersten
See report 2830238
## Comment 11958
Date: 2009-08-14 13:54:40 +0200
From: @drstmane
tagged subject
## Comment 11959
Date: 2009-09-20 21:48:51 +0200
From: @njnes
don't allow update statements in readonly mode. Testing would be the same as for the readonly / create bug, ie we don't add a special test for this.
## Comment 11960
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2808453 at http://sourceforge.net/support/tracker.php?aid=2808453
| SQL: Trying a copy into in read only database segfault | https://api.github.com/repos/MonetDB/MonetDB/issues/2110/comments | 0 | 2020-11-30T10:22:07Z | 2024-06-27T11:40:19Z | https://github.com/MonetDB/MonetDB/issues/2110 | 753,349,679 | 2,110 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-18 04:19:33 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-07 04:46:57 +0200
## Comment 11951
Date: 2009-06-18 16:19:33 +0200
From: @skinkie
select naam, vestigingsplaats from anbi except select naam, vestigingsplaats, beschikking from anbi, kvk where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
!EXCEPT: column counts (4 and 10) do not match
(that is basically a typo, but see the count is only one off, not 6)
select naam, vestigingsplaats from anbi except select naam, vestigingsplaats from anbi, kvk where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
==> 16937 tuples
select naam, vestigingsplaats, beschikking from anbi except select naam, vestigingsplaats, beschikking from anbi, kvk where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
==> 16941 tuples
select naam, vestigingsplaats, beschikking, intrekking from anbi except select naam, vestigingsplaats, beschikking, intrekking from anbi, kvk where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
fail; column intrekking contains null values.
==> 27167 tuples
## Comment 11952
Date: 2009-06-18 19:29:24 +0200
From: @skinkie
additionally except doesn't respect 'limit X';
## Comment 11953
Date: 2009-08-06 16:01:06 +0200
From: @mlkersten
To be investigated when a scaled down version of this problem provided.
## Comment 11954
Date: 2009-08-07 16:46:57 +0200
From: @njnes
added test to src/test/BugTracker-2009/Tests/except_error_wrong.SF-2808409.sql
fixed error message.
## Comment 11955
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2808409 at http://sourceforge.net/support/tracker.php?aid=2808409
| except breaks on date column / null | https://api.github.com/repos/MonetDB/MonetDB/issues/2109/comments | 0 | 2020-11-30T10:22:04Z | 2024-06-27T11:40:18Z | https://github.com/MonetDB/MonetDB/issues/2109 | 753,349,636 | 2,109 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-18 02:48:10 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-11-20 03:18:28 +0100
## Comment 11945
Date: 2009-06-18 14:48:10 +0200
From: @skinkie
To create the table; /export refers to loki.
create table kvk (kvk bigint, bedrijfsnaam varchar(255), adres varchar(64),
postcode varchar(6), plaats varchar(32), type varchar(16));
create table anbikvk (naam varchar(256), vestigingsplaats varchar(32), besch
ikking date, intrekking date, kvk bigint);
create table anbi (naam varchar(256), vestigingsplaats varchar(32), beschikk
ing timestamp, intrekking timestamp);
COPY 27598 RECORDS INTO anbi FROM '/export/scratch1/konink/anbi.csv' USING DELIMITERS ',', '\n', '""';
COPY 1621594 RECORDS INTO kvk FROM '/export/scratch1/konink/allesn' USING DELIMITERS ',', '\n', '""';
insert into anbikvk select naam, vestigingsplaats, beschikking, intrekking,
kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lo
wer(vestigingsplaats);
select count(*) from kvk,anbi where not (lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lowers(vestigingsplaats));
Known errors are:
- Segmentation fault (64/32)
- BUN error
- !ERROR: GDKsave: error on: name=54/5412, ext=head, mode=1
!OS: No space left on device
!ERROR: GDKload: failed name=54/5412, ext=head
The database is by far smaller than main memory.
## Comment 11946
Date: 2009-08-06 16:03:26 +0200
From: @mlkersten
To be further investigated when the minimal database + testscript is provided.
Alternatively, a TRACE of this query against the original might provide the information needed.
## Comment 11947
Date: 2009-08-11 02:30:56 +0200
From: @skinkie
Points:
1) Can lower = lower (or upper = upper) be recognized in the parser as case insensitive comparison? Instead of transforming two entire columns to another value.
Plan:
project (
| group by (
| | select (
| | | crossproduct (
| | | | table(sys.kvk) [ kvk.bedrijfsnaam, kvk.plaats, kvk.%TID% NOT NULL ],
| | | | table(sys.anbi) [ anbi.naam, anbi.vestigingsplaats, anbi.%TID% NOT NULL ]
| | | )
| | ) [ not(and(=(lower(anbi.naam), lower(kvk.bedrijfsnaam)), =(lower(kvk.plaats), lower(anbi.vestigingsplaats)))) = true ]
| ) [ ] [ count NOT NULL as L1 ]
) [ L1 NOT NULL ]
Trace (doesn't run on a full database) as will be attached.
## Comment 11948
Date: 2009-08-14 13:58:39 +0200
From: @drstmane
tagged subject
## Comment 11949
Date: 2009-11-20 15:18:26 +0100
From: @njnes
closing as the generated plan is correct. The crossproduct is in this case needed because of the not and and lower. As long as we do not have a case insensitive join, rewriting lower(x) = lower(y) isn't possible/usefull.
No test possible as the crash (caused by the large crossproduct result) would re quire a bit table.
## Comment 11950
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2808353 at http://sourceforge.net/support/tracker.php?aid=2808353
| SQL: not (...) goes far out of hand | https://api.github.com/repos/MonetDB/MonetDB/issues/2108/comments | 0 | 2020-11-30T10:22:01Z | 2024-06-28T13:25:16Z | https://github.com/MonetDB/MonetDB/issues/2108 | 753,349,594 | 2,108 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-17 11:25:24 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-06 10:08:03 +0200
## Comment 11941
Date: 2009-06-17 11:25:24 +0200
From: @skinkie
sql>create table test (a integer, b integer);
0 tuples
sql>insert into test (a) values (select 2);
Rows affected 1
sql>insert into test (a,b) values (select 2, 2);
!INSERT INTO: number of values doesn't match number of columns of table
'test'
0 tuples
## Comment 11942
Date: 2009-08-06 16:07:32 +0200
From: @mlkersten
See BugTracker-2009/ insert_ambiguity.SF-2807609.sql
## Comment 11943
Date: 2009-08-06 22:08:03 +0200
From: @njnes
added test to BugTracker-2009/insert_into_values_bug.SF-2807609.sql
Bug fixed by correctly disallowing all selects within values() lists.
## Comment 11944
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2807609 at http://sourceforge.net/support/tracker.php?aid=2807609
| !INSERT INTO: number of values doesn't match number of colum | https://api.github.com/repos/MonetDB/MonetDB/issues/2107/comments | 0 | 2020-11-30T10:21:57Z | 2024-06-27T11:40:15Z | https://github.com/MonetDB/MonetDB/issues/2107 | 753,349,543 | 2,107 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-16 09:39:20 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-06-16 10:23:20 +0200
## Comment 11934
Date: 2009-06-16 21:39:20 +0200
From: @skinkie
sql>select naam, vestigingsplaats, beschikking, intrekking, kvk.kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats) limit 10;
+------------------------------------------+------------------+-------------+------------+-------------+
| naam | vestigingsplaats | beschikking | intrekking | kvk |
+==========================================+==================+=============+============+=============+
| WERELDWINKEL HEERENVEEN | HEERENVEEN | 2008-01-01 | null | 10702640000 |
| STICHTING MONUMENTENZORG LEEUWARDERADEEL | STIENS | 2009-01-01 | null | 1079853 |
| STICHTING FRIES NATUURHISTORISCH MUSEUM | LEEUWARDEN | 2008-01-01 | null | 1079917 |
| STICHTING VRIENDEN VAN ZIENN | OENTSJERK | 2008-01-01 | null | 1080218 |
| NEDERLANDSE HOOFDPIJN STICHTING | DOKKUM | 2008-01-01 | null | 1081350 |
| STICHTING SEBO DETMERS | OOSTERWOLDE FR | 2008-01-01 | null | 1081838 |
| STICHTING AMBULANCE DIER IN NOOD | PEINS | 2008-01-01 | null | 1082006 |
| STICHTING ORANJECOMITE JOURE | JOURE | 2008-01-01 | null | 1082094 |
| STICHTING O.S.G. PITER JELLES | LEEUWARDEN | 2008-01-01 | null | 1082181 |
| STICHTING VOORZIENINGEN OLMENES | APPELSCHA | 2008-01-01 | null | 1082205 |
+------------------------------------------+------------------+-------------+------------+-------------+
10 tuples
sql>insert into anbikvk values (select naam, vestigingsplaats, beschikking, intrekking, kvk.kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats));
!INSERT INTO: number of values doesn't match number of columns of table 'anbikvk'
0 tuples
sql>\d anbikvk
CREATE TABLE "sys"."anbikvk" (
"naam" varchar(256),
"vestigingsplaats" varchar(32),
"beschikking" date,
"intrekking" date,
"kvk" bigint
);
sql>insert into anbikvk (naam, vestigingsplaats, beschikking, intrekking, kvk) values (select naam, vestigingsplaats, beschikking, intrekking, kvk.kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats));
!INSERT INTO: number of values doesn't match number of columns of table 'anbikvk'
0 tuples
Today it was mentioned to 'read' error messages, but counting is also an ability that I seem to lack :\
## Comment 11935
Date: 2009-06-16 22:21:16 +0200
From: @skinkie
>create table anbikvk (naam varchar(256), vestigingsplaats varchar(32), besch
ikking date, intrekking date, kvk bigint);
0 tuples
sql>insert into anbikvk (naam, vestigingsplaats) values (select 'test', 'bla');
!INSERT INTO: number of values doesn't match number of columns of table 'anbikvk
'
0 tuples
sql>drop table anbikvk;
0 tuples
sql>create table anbikvk (naam varchar(256), vestigingsplaats varchar(32));
0 tuples
sql>insert into anbikvk (naam, vestigingsplaats) values (select 'test', 'bla');
!INSERT INTO: number of values doesn't match number of columns of table 'anbikvk
'
0 tuples
sql>insert into anbikvk (naam, vestigingsplaats) values ('test', 'bla');
Rows affected 1
sql>select 'test', 'bla'
more>;
+--------------+--------------+
| single_value | single_value |
+==============+==============+
| test | bla |
+--------------+--------------+
1 tuple
## Comment 11936
Date: 2009-06-16 22:23:07 +0200
From: @skinkie
I guess my SQL is bad...
insert into anbikvk select naam, vestigingsplaats, beschikking, intrekking, kvk.kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
works...
## Comment 11937
Date: 2009-06-17 08:44:36 +0200
From: @grobian
I can live with that
## Comment 11938
Date: 2009-06-17 08:59:33 +0200
From: @skinkie
sql>create table test (a integer, b integer);
0 tuples
sql>insert into test name (a) values (select 2);
!syntax error, unexpected sqlNAME, expecting SCOLON in: "insert into test name"
0 tuples
sql>insert into test (a) values (select 2);
Rows affected 1
sql>insert into test (a,b) values (select 2, 2);
!INSERT INTO: number of values doesn't match number of columns of table 'test'
0 tuples
Can you live with this too?
## Comment 11939
Date: 2009-06-17 10:37:52 +0200
From: @grobian
> !syntax error, unexpected sqlNAME, expecting SCOLON in: "insert into test name"
name is a reserved keyword, and indeed it is unexpected here (at least I don't know what it means there, which may be a problem on my side)
## Comment 11940
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2807341 at http://sourceforge.net/support/tracker.php?aid=2807341
| INSERT INTO doesn't match number of columns | https://api.github.com/repos/MonetDB/MonetDB/issues/2106/comments | 0 | 2020-11-30T10:21:54Z | 2024-06-28T13:25:16Z | https://github.com/MonetDB/MonetDB/issues/2106 | 753,349,504 | 2,106 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-16 09:27:11 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-07 10:38:39 +0200
## Comment 11924
Date: 2009-06-16 21:27:11 +0200
From: @skinkie
>mserver5: ../../../src/server/rel_select.mx:4289: rel_select_exp: Assertion `re->type == e_column' failed.
Is caused by:
update anbi set kvk = (select kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats));
Now I know this query might not be valid... but I was toying around :)
## Comment 11925
Date: 2009-06-24 11:57:02 +0200
From: @sjoerdmullender
database schema?
Presumably we don't need data, but this cannot be tested without a database schema.
## Comment 11926
Date: 2009-06-24 12:00:27 +0200
From: @skinkie
CREATE TABLE "sys"."anbi" (
"naam" varchar(256),
"vestigingsplaats" varchar(32),
"beschikking" date,
"intrekking" date
);
CREATE TABLE "sys"."kvk" (
"kvk" bigint,
"bedrijfsnaam" varchar(255),
"adres" varchar(64),
"postcode" varchar(6),
"plaats" varchar(32),
"type" varchar(16)
);
The data is available with Niels, but I have kindly requested not to incorporate the entire database in a public test suite until further notice.
## Comment 11927
Date: 2009-06-24 14:12:27 +0200
From: @sjoerdmullender
Sorry:
sql>update anbi set kvk = (select kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats));
!UPDATE: no such column 'anbi.kvk'
The schema does not match the query.
## Comment 11928
Date: 2009-06-24 14:19:24 +0200
From: @skinkie
Sorry, that was a production copy. Adding kvk bigint to the schema definition of anbi works.
sql>CREATE TABLE "sys"."anbi" ( "naam" varchar(256), "vestigingsplaats" varchar(32), "beschikking" date, "intrekking" date, kvk bigint);
0 tuples
sql>CREATE TABLE "sys"."kvk" ("kvk" bigint, "bedrijfsnaam" varchar(255), "adres" varchar(64), "postcode" varchar(6), "plaats" varchar(32), "type" varchar(16));
0 tuples
sql>update anbi set kvk = (select kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats));
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = update anbi set kvk = (select kvk from kvk,anbi where lower(naam) =
ERROR = Connection terminated
## Comment 11929
Date: 2009-06-24 14:54:16 +0200
From: @drstmane
sql>CREATE TABLE "sys"."anbi" ( "naam" varchar(256), "vestigingsplaats" varchar(32), "beschikking" date, "intrekking" date, kvk bigint);
0 tuples
sql>CREATE TABLE "sys"."kvk" ("kvk" bigint, "bedrijfsnaam" varchar(255), "adres" varchar(64), "postcode" varchar(6), "plaats" varchar(32), "type" varchar(16));
0 tuples
sql>select kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
!SELECT: identifier 'kvk' unknown or ambiguous
0 tuples
sql>
## Comment 11930
Date: 2009-06-24 14:57:56 +0200
From: @drstmane
sql>select kvk.kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats);
0 tuples
sql>update anbi set kvk = (select kvk.kvk from kvk,anbi where lower(naam) = lower(bedrijfsnaam) and lower(plaats) = lower(vestigingsplaats));
Rows affected 0
sql>
## Comment 11931
Date: 2009-06-24 14:59:17 +0200
From: @drstmane
... in other words, the actual problem is that the error in the sub query is not handled/propagated properly ...
## Comment 11932
Date: 2009-08-07 10:38:39 +0200
From: @njnes
added test script to src/test/BugTracker-2009/Tests/assert_in_update.SF-2807336.sql
on ambiguous columns we now always fail (instead of trying correlated queries)
## Comment 11933
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2807336 at http://sourceforge.net/support/tracker.php?aid=2807336
| UPDATE Assertion `re->type == e_column' | https://api.github.com/repos/MonetDB/MonetDB/issues/2105/comments | 0 | 2020-11-30T10:21:51Z | 2024-06-27T11:40:13Z | https://github.com/MonetDB/MonetDB/issues/2105 | 753,349,463 | 2,105 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-16 01:03:48 +0200
From: @yzchang
To: @yzchang
Version: -- development
Last updated: 2011-04-28 16:39:01 +0200
## Comment 11916
Date: 2009-06-16 13:03:48 +0200
From: @yzchang
Hi all, I think the following error message is a bit misleading:
$ echo 'fn:resolve-QName("foo:test", <a xmlns:foo="bar"/>)' | pf
error in function application: at (1,1-1,50): wrong number of arguments for function `fn:resolve-QName' (expected 1, got 2)
because the query itself is correct (according to the standard), and the error is actually caused by that pathfinder implements a different signature than the standard one.
So I have two suggestions:
- change the error message into: reference to undefined function `fn:resolve-QName', which makes the code and the documentation (http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/QName-Functions.html) matching each other
- since pathfinder supports a 'resolve-QName' function, with different signature, maybe we should consider using the prefix 'pf', instead of 'fn'?
Regards,
Jennie
## Comment 11917
Date: 2009-06-18 18:05:58 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi Jennie,
I added a signature for fn:resolve-QName with two arguments. The error message now is: ``fatal error: Algebra implementation for function `fn:resolve-QName' unknown.''
Can you live with that?
## Comment 11918
Date: 2009-06-25 18:13:55 +0200
From: @yzchang
That is fine with me.
But how about the fn:resolve-QName with one argument? It's quite unclear what it does.
## Comment 11919
Date: 2009-07-29 17:20:10 +0200
From: @sjoerdmullender
Jan, can you pronounce on this?
## Comment 11920
Date: 2009-08-14 13:59:54 +0200
From: @drstmane
tagged subject
## Comment 11921
Date: 2009-09-07 23:37:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Jennie,
this is an artifact from Jens. fn:resolve-QName with one parameter basically is a cast to xs:QName -- but have a look in compiler/algebra/builtins.c for more information.
## Comment 11922
Date: 2009-11-12 10:50:47 +0100
From: @peterboncz
It appears there is little chance this feature will be added to pf soon => won't fix
## Comment 11923
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2807105 at http://sourceforge.net/support/tracker.php?aid=2807105
## Comment 15777
Date: 2011-04-28 16:39:01 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| XQ: misleading error msg for fn:resolve-QName | https://api.github.com/repos/MonetDB/MonetDB/issues/2104/comments | 0 | 2020-11-30T10:21:48Z | 2024-06-28T13:25:15Z | https://github.com/MonetDB/MonetDB/issues/2104 | 753,349,425 | 2,104 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-16 10:30:40 +0200
From: @lsidir
To: @sjoerdmullender
Version: -- development
Last updated: 2009-06-24 11:52:06 +0200
## Comment 11913
Date: 2009-06-16 10:30:40 +0200
From: @lsidir
In the MAL console (at the server or mclient -lmal) if you type a module name that has functions in addition to commands, put the dot and a closing parenthesis ) to get the help message, the server will seg fault. Example:
sql.) + tab
or
sql.bbp) + tab
but
algebra.) + tab
will work since algebra module defines only commands and not functions.
## Comment 11914
Date: 2009-06-24 11:52:06 +0200
From: @sjoerdmullender
Fixed in CVS on stable branch.
I don't know how this can be tested, so no test added.
## Comment 11915
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2807038 at http://sourceforge.net/support/tracker.php?aid=2807038
| tab + ) + mal function = seg fault | https://api.github.com/repos/MonetDB/MonetDB/issues/2103/comments | 0 | 2020-11-30T10:21:45Z | 2024-06-27T11:40:11Z | https://github.com/MonetDB/MonetDB/issues/2103 | 753,349,384 | 2,103 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-15 02:31:25 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-04 12:23:41 +0200
## Comment 11910
Date: 2009-06-15 14:31:25 +0200
From: @skinkie
It is very cool that this is a feature, but it would be better if we had ilike and like :)
## Comment 11911
Date: 2009-08-04 00:23:41 +0200
From: @njnes
we now have like and ilike.
## Comment 11912
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2806571 at http://sourceforge.net/support/tracker.php?aid=2806571
| like is case insensitive | https://api.github.com/repos/MonetDB/MonetDB/issues/2102/comments | 0 | 2020-11-30T10:21:42Z | 2024-06-27T11:40:10Z | https://github.com/MonetDB/MonetDB/issues/2102 | 753,349,346 | 2,102 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-15 11:37:26 +0200
From: John van Schie <<johnvanschie>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2011-04-28 16:38:56 +0200
## Comment 11886
Date: 2009-06-15 11:37:26 +0200
From: John van Schie <<johnvanschie>>
MonetDB/XQuery Feb2009-SP2, Fedora Core 10 x86_64, 64 bit OID's, RPM install.
We have a MonetDB server that contains a fairly large (678 docs) collection of small documents. When selecting attributes from elements within the documents, some strange behaviour is noticed. It can be explained best with an query.
----
let $tasks := pf:collection('c2_log.xml')//success/task[@duration]
for $task in $tasks
(: tasks should always have a xid and duration attribute when successful :)
where count($task/@*) != 2
return element {$task/name()} {$task/@*, $task}
----
<task duration="49506"><task duration="49506" xid="3"/></task>,
<task duration="24503"><task duration="24503" xid="799"/></task>,
<task duration="1531"><task duration="1531" xid="822"/></task>,
<task duration="5724"><task duration="5724" xid="7971"/></task>,
<task duration="439"><task duration="439" xid="8591"/></task>,
<task duration="510"><task duration="510" xid="8592"/></task>,
<task duration="1351"><task duration="1351" xid="8600"/></task>,
<task duration="749"><task duration="749" xid="8602"/></task>,
<task duration="2100"><task duration="2100" xid="22742"/></task>,
----
Thus we select all tasks that do not have two attributes and we see tasks elements that have their xid attribute missing. But if we print the whole task element, the missing xid attribute magically re-appears.
When we run the same query on a single document of the collection, we see the same strange behaviour. We are not able to reproduce this behaviour by exporting a problematic document and shredding it.
## Comment 11887
Date: 2009-06-16 10:34:26 +0200
From: @drstmane
John,
how has your collection initially been created?
a) shredding all 678 docs in one go?
b) shredding the 678 docs incrementally into the same collection (e.g., in small batches or one at a time)?
Have there been updates on the collection during (incremental) and/or after shredding (all documents)?
If so, have those updates touched/altered the data that now appears to be inconsistent, i.e., the task elements with two attributes of with only one appears to be directly addressable?
Thanks!
Stefan
## Comment 11888
Date: 2009-06-16 11:58:20 +0200
From: John van Schie <<johnvanschie>>
Stefan,
The 678 documents are shredded incrementally into the same collection. After each tool run, a XML log file is created and shredded in MonetDB, into the log collection.
The only other operation performed on the log collection is copy; A selection on the collection ( pf:collection("c2_log.xml")//run ) is executed and the XML that is returned is stored to file. This file is than read-only shredded in the database, but *not* into the log collection.
No XQuery updates are performed on the log document, although the documents are flagged 'updateable'.
If you need more information (the server is still running), please let me know.
John
## Comment 11889
Date: 2009-06-16 13:56:16 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi John,
I checked the compile time part of the query which looks fine. So it most certainly is a runtime problem.
Out of curiosity, what happens if you modify your query to check for the xid attributes directly?
let $tasks := pf:collection('c2_log.xml')//success/task[@duration]
for $task in $tasks
where count($task/@xid) != 1
return element {$task/name()} {$task/@*, $task}
And what happens if you choose a newer compiler version to run the query? To do that just compile your query with pf and feed the resulting MIL code to the old runtime.
## Comment 11890
Date: 2009-06-16 14:36:45 +0200
From: @drstmane
John,
could you please run the following queries on the same database and report their results:
let $tasks := pf:collection('c2_log.xml')//success/task[@xid]
for $task in $tasks
where count($task/@*) != 2
return element {$task/name()} {$task/@*, $task}
count(pf:collection('c2_log.xml')//success/task)
count(pf:collection('c2_log.xml')//success/task[@*])
count(pf:collection('c2_log.xml')//success/task[count(@*) < 2])
count(pf:collection('c2_log.xml')//success/task[count(@*) = 2])
count(pf:collection('c2_log.xml')//success/task[count(@*) > 2])
count(pf:collection('c2_log.xml')//success/task[count(@*) != 2])
## Comment 11891
Date: 2009-06-16 15:42:50 +0200
From: John van Schie <<johnvanschie>>
Stefan,
I'm sorry, but when I inspect our code, I see that it is possible for successful tasks to have only an xid attribute. Valid combinations are either an xid attribute or an xid and duration attribute. So succesful tasks without xid attribute are not valid.
The changed assumption, changes the expected output for your requested queries. Am I correct to change them by adding a @duration filter to your first, third, fourth, fifth, sixth and seventh requested query?
Jan,
I'll generate the MIL and execute it as soon as I have a May2009 install ready.
Regards,
John
## Comment 11892
Date: 2009-06-16 16:06:01 +0200
From: @drstmane
John,
sounds fine with me.
Stefan
## Comment 11893
Date: 2009-06-16 16:25:41 +0200
From: John van Schie <<johnvanschie>>
Stefan,
The requested queries:
1)
Query:
let $tasks := pf:collection('c2_log.xml')//success/task[@xid and @duration]
for $task in $tasks
where count($task/@*) != 2
return element {$task/name()} {$task/@*, $task}
Result:
No output
2)
Query:
count(pf:collection('c2_log.xml')//success/task)
Result:
1104491
3)
Query:
count(pf:collection('c2_log.xml')//success/task[@* and @duration])
Result::
135
4)
Query:
count(pf:collection('c2_log.xml')//success/task[count(@*) < 2 and @duration])
Result:
135
5)
Query:
count(pf:collection('c2_log.xml')//success/task[count(@*) = 2 and @duration])
Result
0
6)
Query:
count(pf:collection('c2_log.xml')//success/task[count(@*) > 2 and @duration])
Result:
0
7)
Query:
count(pf:collection('c2_log.xml')//success/task[count(@*) != 2 and @duration])
Result:
0
8) (bonus)
Query:
count(pf:collection('c2_log.xml')//success/task[@* and not(@duration)])
Result:
1104356
## Comment 11894
Date: 2009-06-16 16:35:06 +0200
From: @drstmane
To which extend do the results match with your expectation, e.g., do you expect only 135 of the 1104491 successful tasks to have a duration attribute?
Am I right, that the 9 tasks listed as result of your original query are just a sample of the complete result?
(from you below results, I'd expect 135 tasks, right?)
## Comment 11895
Date: 2009-06-16 17:37:25 +0200
From: Jan Rittinger <<jan.rittinger>>
How many attributes does the task element have?
count(pf:collection('c2_log.xml')//success/task/@*)
How many xid attributes does the task elements have?
count(pf:collection('c2_log.xml')//success/task/@xid)
If understand your setup correctly the first query should return 1104626 and the second 1104491...(Otherwise I assume we have a simplified version of the problem.)
## Comment 11896
Date: 2009-06-17 10:21:43 +0200
From: John van Schie <<johnvanschie>>
I see that I've made a typo in the results of the queries. Query 7 returns 135.
> To which extend do the results match with your expectation, e.g., do you
> expect only 135 of the 1104491 successful tasks to have a duration
> attribute?
I expect a total of 1104491 successful tasks, 1104356 with only an xid attribute and 135 with an xid attribute and a duration attribute. So I expected query 4 to return 0, query 5 to return 135 and query 7 to return 0.
> Am I right, that the 9 tasks listed as result of your original query are
> just a sample of the complete result? (from you below results, I'd expect 135 tasks, right?)
You're right. It was just to make a small report, explaining the problem.
## Comment 11897
Date: 2009-06-17 10:31:39 +0200
From: John van Schie <<johnvanschie>>
> How many attributes does the task element have?
> count(pf:collection('c2_log.xml')//success/task/@*)
>
> How many xid attributes does the task elements have?
> count(pf:collection('c2_log.xml')//success/task/@xid)
xquery>count(pf:collection('c2_log.xml')//success/task/@*)
more>1104491
xquery>count(pf:collection('c2_log.xml')//success/task/@xid)
more>1104356
> If understand your setup correctly the first query should return 1104626
> and the second 1104491...(Otherwise I assume we have a simplified version
> of the problem.)
I don't really get how you've deduced those numbers. The problem, as I see it, is that for all successful task elements that have a duration attribute, the xid attribute is not available in the index. So the query on @xid returns empty for those elements, but printing the elements does yield their xid attribute. An example can be seen in the first post of the bug report.
Thus we have 1104491 successful tasks that have any attribute, and all of them should have an xid attribute. There are 135 elements that have an xid and a duration attribute, and for those, the xid attribute seems ignored/unqueryable by MonetDB. So a count on all successful tasks with an xid attribute yields 1104491 - 135 = 1104356.
I hope this explanation describes the problem better.
Jan, I'll try to generate the MIL for the query listed in your first post on the May2009 next and post the result here.
## Comment 11898
Date: 2009-06-17 13:20:54 +0200
From: John van Schie <<johnvanschie>>
Jan,
I've tried to execute the query listed below with the MIL code generated by the Feb2009-SP2 release and the May2009 release. Although the MIL code generated differs, the resulting XML output does not. Both return 135 task items, where I expect 0.
The query:
let $tasks := pf:collection('c2_log.xml')//success/task[@duration]
for $task in $tasks
where count($task/@xid) != 1
return element {$task/name()} {$task/@*, $task}
## Comment 11899
Date: 2009-06-18 18:35:38 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi John,
already the simplified query ``count(pf:collection('c2_log.xml')//success/task/@*)'' provides an incorrect result as it should return (1104491 xid + 135 Duration =) 1104626 attributes.
Without more information I however cannot help further.
(With the anonymized working set information in ATTR_OWN, ATTR_OWN_PRIVATE, ATTR_OWN_SHARED, and the NID values of the tasks somebody at CWI could perhaps get an idea.)
## Comment 11900
Date: 2009-06-23 14:43:34 +0200
From: John van Schie <<johnvanschie>>
Hi Jan,
I can provide all required data, if you give me pointers how to obtain it. The data is not confidential, and thus I could provide an non-anonymized data set.
## Comment 11901
Date: 2009-07-09 13:28:28 +0200
From: John van Schie <<johnvanschie>>
Jan,
Is there any way I can provide you with more information to find a solution? Or should this bug be re-assigned to somebody else (as it could be non-pathfinder related)
Thanks,
John
## Comment 11902
Date: 2009-07-09 17:44:35 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi John,
I guess something is wrong in the document representation (and I'm not the M/XQ runtime guy).
I however attached a MIL script (debug.mil) that runs the simplified query
``count(pf:collection('c2_log.xml')//success/task/@*)'' and gives some additional information about the inputs to the attribute step. I hope the result will give a better indication who needs to fix the problem :)
## Comment 11903
Date: 2009-07-09 20:15:54 +0200
From: @peterboncz
This is most likely a collection with updatable documents. Most likely some xid attributes, were deleted? Is that correct? Or where they inserted? I also think that you man that the correct behavior would be that the xid attributes would not appear when printed.
The problem is probably in the interaction between the shared master ATTR_OWN and the deltas in the query working set. Most likely in the serialization code. Maybe it does not properly handle deleted attributes.
I fear we can conclude from your recent batch of bugs that there are still a number of bugs in the update code. We will try to locate them, but this is often complicated. Also by the fact that this month I am on holiday in Argentina...
## Comment 11904
Date: 2009-08-12 13:20:07 +0200
From: John van Schie <<johnvanschie>>
Jan, Peter,
I've attached the output of the mil script that Jan provided as debug.output. I do not fully comprehend the output, but I hope it is useful.
About the xid attributes: I have checked the code, and it does not remove attributes from the documents.
It starts by shredding a document under the name 'c2_log.xml' with the same collection, and thus initialising the collection 'c2_log.xml'. The shredded document has updatable set to true.
Next, for each iteration of the framework, it shreds a document under an unique name in the collection 'c2_log.xml'.
On the side: There was no need for the initial document to be updatable. Since we changed this to read-only, about 2 months ago, we haven't seen the error re-appear.
## Comment 11905
Date: 2009-08-12 13:47:46 +0200
From: John van Schie <<johnvanschie>>
Sorry, but due to limitations of sourceforge, I'm not able to send the debug.mil output. Can I send it via e-mail to someone?
## Comment 11906
Date: 2009-08-14 13:56:11 +0200
From: @drstmane
tagged subject
## Comment 11907
Date: 2009-11-15 15:37:18 +0100
From: Jan Rittinger <<jan.rittinger>>
This looks like a problem in the storage of updateable document and we have to less information at hand to fix it.
## Comment 11908
Date: 2009-11-16 23:21:17 +0100
From: @peterboncz
well, this is an open problem, and given time, we might find a way to reproduce a way and fix, it is serious enough
## Comment 11909
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2806488 at http://sourceforge.net/support/tracker.php?aid=2806488
## Comment 15764
Date: 2011-04-28 16:38:56 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| XQ: Some XML attributes not selectable. | https://api.github.com/repos/MonetDB/MonetDB/issues/2101/comments | 0 | 2020-11-30T10:21:39Z | 2024-06-28T13:25:14Z | https://github.com/MonetDB/MonetDB/issues/2101 | 753,349,313 | 2,101 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-15 02:20:40 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-06-15 03:01:37 +0200
## Comment 11882
Date: 2009-06-15 02:20:40 +0200
From: @skinkie
The following informational error message is present at copy into time. It might be extended...
sql>COPY 1203854 RECORDS INTO kvk FROM '/tmp/proper' USING DELIMITERS ',', '\n', '""';
0 tuples
write error
I think it is related to a not valid input related to the use of " " within a delimited part. Message is private due to the content of this query.
## Comment 11883
Date: 2009-06-15 02:27:06 +0200
From: @skinkie
Ok this is again related to 'special characters'. I remember a question from the mailinglist and my previous bug report on this matter...
## Comment 11884
Date: 2009-06-15 03:01:36 +0200
From: @skinkie
This is a duplicate of http://sourceforge.net/support/tracker.php?aid=2177734; POSIX locale again.
The interesting thing is that after reading back the following does give output:
/opt/monetdb-head/bin/mclient -lsql -Een_US.UTF-8 -H
/opt/monetdb-head/bin/mclient: warning: cannot convert local character set en_US.UTF-8 to UTF-8
/opt/monetdb-head/bin/mclient: warning: cannot convert UTF-8 to local character set en_US.UTF-8
sql>COPY 8 RECORDS INTO kvk FROM '/tmp/test' USING DELIMITERS ',', '\n', '""';
!SQLException:sql:value 'Co�eratieve Rabobank \"Koudum\" B.A. I.L.' while parsing 'Co�eratieve Rabobank \"Koudum\" B.A. I.L.", "Dubbelstraat 6", "8561BC", "Balk", "Hoofdvestiging"' from line 7 field 1 not inserted, expecting type str
!SQLException:importTable:failed to import table
0 tuples
while:
-Eutf8 does not. [and just writes the previously mentioned error]
CREATE TABLE "sys"."kvk" (
"kvk" bigint,
"bedrijfnaam" varchar(255),
"adres" varchar(64),
"postcode" varchar(6),
"plaats" varchar(32),
"type" varchar(16)
);
So the solution was rather simple; though the following sequence of commands still made me wonder if the -E actually works...
skinkie@productie ~ $ iconv -o /tmp/test2 -f iso-8859-1 -t utf8 /tmp/test
skinkie@productie ~ $ /opt/monetdb-head/bin/mclient -lsql
sql>skinkie@productie ~ $ /opt/monetdb-head/bin/mclient -lsql -H
sql>COPY 8 RECORDS INTO kvk FROM '/tmp/test' USING DELIMITERS ',', '\n', '""';
!SQLException:sql:value 'Co�peratieve Raboban Koudum B.A. I.L.' while parsing 'Co�peratieve Raboban Koudum B.A. I.L.", "Dubbelstraat 6", "8561BC", "Balk", "Hoofdvestiging"' from line 7 field 1 not inserted, expecting type str
!SQLException:importTable:failed to import table
0 tuples
sql>COPY 8 RECORDS INTO kvk FROM '/tmp/test2' USING DELIMITERS ',', '\n', '""';
Rows affected 8
sql>
skinkie@productie /opt/monetdb-head/bin/mclient -lsql -Eiso-8859-1 -H
sql>COPY 8 RECORDS INTO kvk FROM '/tmp/test2' USING DELIMITERS ',', '\n', '""';
Rows affected 8
sql>COPY 8 RECORDS INTO kvk FROM '/tmp/test' USING DELIMITERS ',', '\n', '""';
0 tuples
write error
## Comment 11885
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2806351 at http://sourceforge.net/support/tracker.php?aid=2806351
| write error after copy into | https://api.github.com/repos/MonetDB/MonetDB/issues/2100/comments | 0 | 2020-11-30T10:21:36Z | 2024-06-28T13:25:14Z | https://github.com/MonetDB/MonetDB/issues/2100 | 753,349,283 | 2,100 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-12 05:22:10 +0200
From: @yzchang
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-06-16 05:15:35 +0200
## Comment 11869
Date: 2009-06-12 17:22:10 +0200
From: @yzchang
With May 2009 release, Algebra backend, calling fn:trace() results in a monet_sprintf error:
$ echo 'fn:trace(<a>blah</a>, "test ")' | pf | Mserver
MonetDB Server v4.30.0
based on GDK v1.30.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB> PF/Tijah module v0.13.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB><?xml version="1.0" encoding="utf-8"?>
<XQueryResult><a>blah</a></XQueryResult>
MonetDB>!ERROR: monet_sprintf(): illegal type in param 1.
!ERROR: print_format: operation failed.
MonetDB>
## Comment 11870
Date: 2009-06-14 18:04:31 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi Jennie,
this works for me both with the Current as well as the stable branch:
$ echo 'fn:trace(<a>blah</a>, "test ")' | pf | MonetDB Server v4.30.1
based on GDK v1.30.1
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for i386-apple-darwin9.7.0/64bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.13.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
<?xml version="1.0" encoding="utf-8"?>
<XQueryResult><a>blah</a></XQueryResult>
<scope id="0">
<iteration no="1">
<trace msg="test " id="1">
<item pos="1" type="node" id="2" fragment="0"><a>blah</a></item>
</trace>
</iteration>
</scope>
## Comment 11871
Date: 2009-06-16 00:17:36 +0200
From: @yzchang
It indeed works on Mac OSX. But on my FC10 machine, I even get this error with a fresh installed version of the May 2009 release (i.e., installed with monetdb-install.sh --enable-xquery).
Could someone else (using a FC10 machine) check if he/she could reproduce this error? Thanks!
Jennie
## Comment 11872
Date: 2009-06-16 02:34:37 +0200
From: @sjoerdmullender
It is a bug and the bug is in pf_support.mx on one of the lines that say printf("<scope id=\"%i\">\n",...). The problem is the mismatch between the format (%i) and the type of the argument.
Since I'm on vacation, somebody else can fix it.
Hint: try setting a breakpoint on monet_sprintf and then run the script.
## Comment 11873
Date: 2009-06-16 10:47:17 +0200
From: @drstmane
A quick analysis following Sjoerd's recipe reveals that the %i format is used with a lng argument --- an obvious mismatch, correctly triggering the error --- still open, whether the the lng argument is to be expected, here, next to or in addition to an int argument ...
## Comment 11874
Date: 2009-06-16 10:51:44 +0200
From: @drstmane
works fine on 32-bit systems and on 64-bit systems with 32-bit OIDs --- apparently an OID is printed using the "%i" format ...
(nice example the adding a test would have easily revealed this pattern with nightly testing ;-))
## Comment 11875
Date: 2009-06-16 10:57:32 +0200
From: @yzchang
I have just tested a patch received from Jan (R.). It works with the patch. This bug could be closed soon.
Don't we have a test for each built-in function we support/implement? Then, maybe we should consider adding them.
## Comment 11876
Date: 2009-06-16 11:02:47 +0200
From: @drstmane
On 64-bit systems with 64-bit OIDs, we get
MonetDB>var o:=0@0;
MonetDB>var i:=1;
MonetDB>var l:=2LL;
MonetDB>print(o);
[ 0@0 ]
MonetDB>print(i);
[ 1 ]
MonetDB>print(l);
[ 2 ]
MonetDB>printf("%i\n",o);
!ERROR: monet_sprintf(): illegal type in param 1.
!ERROR: print_format: operation failed.
MonetDB>printf("%lli\n",o);
0
MonetDB>printf("%i\n",i);
1
MonetDB>printf("%lli\n",i);
1
MonetDB>printf("%i\n",l);
!ERROR: monet_sprintf(): illegal type in param 1.
!ERROR: print_format: operation failed.
MonetDB>printf("%lli\n",l);
2
MonetDB>printf("%lli\n",lng(o));
0
MonetDB>printf("%s\n",str(o));
0@0
From the code of monet_sprintf() in MonetDB4/src/monet/monet.mx, it appears to be save to use "%lli" format for OID, also with 32-bit OIDs, since the code internally takes care of proper casting.
I'll apply the fix.
Stefan
## Comment 11877
Date: 2009-06-16 11:03:34 +0200
From: @drstmane
What does Jan's patch do?
## Comment 11878
Date: 2009-06-16 11:20:43 +0200
From: Jan Rittinger <<jan.rittinger>>
I added casts to int in the MIL code as I didn't know what the 'real' problem was.
Stefan, I think your fix is the better one :)
Could you please apply it -- Thanks.
## Comment 11879
Date: 2009-06-16 11:41:53 +0200
From: @drstmane
I will --- later ...
## Comment 11880
Date: 2009-06-16 17:15:34 +0200
From: @drstmane
Fixed in CVS (May2009 branch):
In MIL, printing (the numeric value of) OIDs using printf()
requires to use format "%lli" to cope with 64-bit OIDs
(the undelying C implementation of monet_sprintf() takes care
of handling 32-bit OIDs correctly).
Added test in pathfinder/tests/BugTracker/Tests/fn-trace.SF-2805513.*
## Comment 11881
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2805513 at http://sourceforge.net/support/tracker.php?aid=2805513
| fn:trace() produces output _and_ error | https://api.github.com/repos/MonetDB/MonetDB/issues/2099/comments | 0 | 2020-11-30T10:21:32Z | 2024-06-27T11:40:07Z | https://github.com/MonetDB/MonetDB/issues/2099 | 753,349,241 | 2,099 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-12 12:39:59 +0200
From: Wouter Alink <<alink>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-06-12 02:03:07 +0200
## Comment 11860
Date: 2009-06-12 12:39:59 +0200
From: Wouter Alink <<alink>>
The JDBC client 1.10 seems to not be able to connect to the May2009 release monetdb instances?
The following error is given:
Exception in thread "main" java.sql.SQLException: InvalidCredentialsException:checkCredentials:invalid credentials for user 'monetdb'
at nl.cwi.monetdb.jdbc.MonetConnection.<init>(MonetConnection.java:220)
at nl.cwi.monetdb.jdbc.MonetDriver.connect(MonetDriver.java:159)
at java.sql.DriverManager.getConnection(DriverManager.java:620)
at java.sql.DriverManager.getConnection(DriverManager.java:200)
In the May2009 branch I could find a possible cause in MapiSocket.java (line 424-457) where the password is overriden which might have been set at line 400.
Fabian, could you have a look?
## Comment 11861
Date: 2009-06-12 12:54:19 +0200
From: Wouter Alink <<alink>>
my mistake... misinterpreted the code. There's nothing wrong in MapiSocket, at least not what I described. But I still don't know why I can't connect.
## Comment 11862
Date: 2009-06-12 13:46:54 +0200
From: @grobian
can you please let JDBC make a debug-log and attach/mail?
## Comment 11863
Date: 2009-06-12 14:03:07 +0200
From: Wouter Alink <<alink>>
found it: database was corrupted. unfortunately I cannot reproduce how the database got corrupted. will close this bugreport. (and reopen when i can reproduce)
## Comment 11864
Date: 2009-06-12 14:05:02 +0200
From: Wouter Alink <<alink>>
For the record:
RD 1244801341680: read final block: 56 bytes
RX 1244801341680: HbbH4Fxu:mserver:9:RIPEMD160,SHA256,SHA1,MD5:LIT:SHA512:
RD 1244801341680: inserting prompt
TD 1244801341693: write final block: 67 bytes
TX 1244801341693: BIG:monetdb:{SHA1}b1c047bf133001d81e91d985b777c7ceee17ce9c:sql:aap:
RD 1244801341694: read final block: 85 bytes
RX 1244801341694: !InvalidCredentialsException:checkCredentials:invalid credentials for user 'monetdb'
RD 1244801341694: inserting prompt
## Comment 11865
Date: 2009-06-12 14:08:17 +0200
From: @grobian
This must have been a database that once was a trunk thinghy, as it speaks proto 9, so it's not the previous release, which spoke proto 8.
## Comment 11866
Date: 2009-06-12 14:16:30 +0200
From: Wouter Alink <<alink>>
Hmmm,
Vault keys where probably the cause of my confusion:
When you do not specify a vault-key, starting mserver5 will cause a warning (which asks you to set it)
If you do set the vault-key, then the database that has just been created will become unusable (user 'monetdb' cannot login), so you first have to delete the respective dbfarm folder after setting the vault-key.
Perhaps a warning in monet5.conf would be nice, which would say something: "warning: changing the vault-key will make all existing databases inaccessible".
And another experiment i just did showed another bug, when setting an zero-size vault-key, MonetDB correctly warns about the zero-sized key, but crashes upon first attempt to connect to it with an mclient.
$ touch ~/opt/MonetDB-stable-debug/etc/monetdb.secret
$ mserver5 --dbname=aap --dbinit="include sql;" --set mapi_port=50100
MonetDB server v5.12.0, based on kernel v1.30.0
Serving database 'aap', 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: your vault key is too short (0), enlarge your vault key!
Listening for connection requests on mapi:monetdb://127.0.0.1:50100/
MonetDB/SQL module v2.30.0 loaded
>Floating point exception
## Comment 11867
Date: 2009-06-15 14:45:59 +0200
From: @grobian
both vault-key issues have been dealt with
## Comment 11868
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2805368 at http://sourceforge.net/support/tracker.php?aid=2805368
| Mapi: JDBC cannot connect: | https://api.github.com/repos/MonetDB/MonetDB/issues/2098/comments | 0 | 2020-11-30T10:21:29Z | 2024-06-28T13:25:13Z | https://github.com/MonetDB/MonetDB/issues/2098 | 753,349,201 | 2,098 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-12 11:43:47 +0200
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2010-03-29 02:58:25 +0200
## Comment 11854
Date: 2009-06-12 11:43:47 +0200
From: @grobian
% monetdb start database
% mclient -lsql -ddatabase
works fine, however, if database is stopped
% mclient -lsql -ddatabase
returns
MAPI = monetdb@localhost:50000
ACTION= mapi_start_talking
ERROR = Connection terminated
merovingian.log:
2009-06-12 11:39:23 MSG merovingian[18322]: starting database 'three', up min/avg/max: 40s/11h/1d, crash average: 0.00 0.00 0.00 (6-6=0)
2009-06-12 11:39:24 MSG merovingian[18322]: proxying client 127.0.0.1:64112 for database 'three' to mapi:monetdb://pegasus.ins.cwi.nl:50001/
2009-06-12 11:39:24 MSG three[17027]: MonetDB server v5.13.0, based on kernel v1.31.0
2009-06-12 11:39:24 MSG three[17027]: Serving database 'three', using 1 thread
2009-06-12 11:39:24 MSG three[17027]: Compiled for x86_64-pc-solaris2.11/64bit with 64bit OIDs dynamically linked
2009-06-12 11:39:24 MSG three[17027]: Copyright (c) 1993-July 2008 CWI.
2009-06-12 11:39:24 MSG three[17027]: Copyright (c) August 2008-2009 MonetDB B.V., all rights reserved
2009-06-12 11:39:24 MSG three[17027]: Visit http://monetdb.cwi.nl/ for further information
2009-06-12 11:39:24 MSG three[17027]: Listening for connection requests on mapi:monetdb://pegasus.ins.cwi.nl:50001/
2009-06-12 11:39:24 MSG merovingian[18322]: database 'three' (17027) was killed by signal 11
2009-06-12 11:39:24 MSG merovingian[18322]: client 127.0.0.1:64112 has disconnected from proxy
Looks like the mserver doesn't like the client to be connecting this fast. Could be related to the sql startup change made for the last release.
## Comment 11855
Date: 2009-06-12 14:30:27 +0200
From: Wouter Alink <<alink>>
I noticed this behaviour too. I think it also happens every now and then when you immediately start an mclient after a 'monetdb start database' command. i noticed that 'monetdb start database; mclient -lsql -ddatabase' on a stopped database seems to fail regularly.
## Comment 11856
Date: 2009-07-01 17:40:39 +0200
From: @grobian
fixed in CVS
## Comment 11857
Date: 2009-07-01 17:45:20 +0200
From: @grobian
3 times is ...?
## Comment 11858
Date: 2010-03-29 14:58:25 +0200
From: @grobian
I haven't seen this issue occurring any more after the fixes to the server not to report too early it's ready
## Comment 11859
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2805340 at http://sourceforge.net/support/tracker.php?aid=2805340
| Merovingian (?): mserver5 segfaults if started by a client | https://api.github.com/repos/MonetDB/MonetDB/issues/2097/comments | 0 | 2020-11-30T10:21:26Z | 2024-06-27T11:40:05Z | https://github.com/MonetDB/MonetDB/issues/2097 | 753,349,165 | 2,097 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-11 03:46:52 +0200
From: francois guerin <<fguerin>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2010-03-17 07:50:17 +0100
## Comment 11838
Date: 2009-06-11 15:46:52 +0200
From: francois guerin <<fguerin>>
Hi,
when launching Mserver, i get a Fatal Error:
!FATAL: GDKlockHome: Database lock '.gdk_lock' denied
I manually delete the file (which is in /var/.../dbfarm/demo/), but the error still comes out.
(MonetDB May release |Â Macbook 32bits | install options: --enable-xquery --enable-optimise)
## Comment 11839
Date: 2009-06-11 15:56:20 +0200
From: @sjoerdmullender
This message usually means there is already another server running for that database. First make sure that there really aren't any other servers around.
## Comment 11840
Date: 2009-06-11 16:04:34 +0200
From: francois guerin <<fguerin>>
there's no server around using this connection :-z
## Comment 11841
Date: 2009-06-11 16:14:05 +0200
From: @sjoerdmullender
I'm not sure we're entirely on the same wavelength. What I'm referring to is another Mserver process. I don't know the invocation on MacOS, but on Linux you'd check this using
ps -e | grep -i mserver
ps -e gives a list of all processes on the system, and the grep will select those that have mserver (case insensitive) in the name.
## Comment 11842
Date: 2009-06-11 17:06:15 +0200
From: @grobian
ps ax | grep -i '[m]server'
will do on OSX.
## Comment 11843
Date: 2009-06-11 17:20:38 +0200
From: francois guerin <<fguerin>>
there's still no process :-S
## Comment 11844
Date: 2009-07-20 20:48:22 +0200
From: @mlkersten
Seems like an xquery related issue, perhaps the application restarts the server already.
## Comment 11845
Date: 2009-07-21 16:28:04 +0200
From: @yzchang
Hi Francois, do you still having this problem? If yes, I'm wondering if it is the .gdk_lock file in the dir /var/.../dbfarm/demo/, which is causing the problem, since this dir is not the default place where monet put its dbfarm. Do you maybe have dbfarm somewhere else?
If you don't have this problem anymore, could you please give us some information how you have solved it?
Thanks!
## Comment 11846
Date: 2009-08-06 14:38:32 +0200
From: @yzchang
We cannot reproduce this bug, and there is no new information from the user if the problem persists.
Change the status to pending, and if there is no new information about this before time expires, I think we could close it as 'invalid' or 'out of date' or something
## Comment 11847
Date: 2009-08-06 16:11:52 +0200
From: francois guerin <<fguerin>>
(please, excuse-me, i was on vacation...)
- i checked via the command netstat, there's no monetdb process running.
- that problem didnt just happen once. sometimes, i violently shut down monetdb server (Mserver) with a ctrl-c, and when i try to launch it again, i am told " Database lock '.gdk_lock' denied ". So, i delete it but the error still appears!
- the dbfarm is in the right place (the place the installation script put it in)
- that problem may happen at anytime. it doesnt seem to depend on the commands I've executed before (that's why i didnt spend time on describing all the actions that could have lead to that gdk_lock problem).
- I havent solve the problem:I have stopped shutting down the server with a ctrl-c and, so far, the gdk_lock problem seems to have vanished.
## Comment 11848
Date: 2009-08-06 16:56:02 +0200
From: @sjoerdmullender
I wonder if this could be a MacOS issue where the server process is not exiting completely when interrupted. The process starts multiple threads and I wonder if they all exit when the process is interrupted. Assigning to Fabian to shine his light on this.
## Comment 11849
Date: 2009-08-14 19:23:38 +0200
From: @grobian
What's the filesystem in use here? HFS+? UFS? NFS? CIFS? Does a reboot help?
## Comment 11850
Date: 2009-09-01 17:41:12 +0200
From: francois guerin <<fguerin>>
the filesystem in use is Mac OSX's (ie HFS, i guess)
a reboot doesnt help.
## Comment 11851
Date: 2009-09-01 18:01:28 +0200
From: @drstmane
I'm confused:
Can you now start Merver, or not?
I.e., does the .gdk_lock problem occur permanently or only when re-starting Mserver (shortly?) after killing it with ctrl-c?
If the former, please make sure that your .../dbfarm/ & .../dbfarm/demo/ are writable for you (i.e., the user that starts the Mserver process), or try to use different location for the dbfarm (Mserver --dbfarm=...).
If the latter, there might just be a MacOS / HFS releated issue/timeout before the fs lock on .gdk_lock is released ... try to shutdown the Mserver with ctrl-d iso. ctrl-c ...
## Comment 11852
Date: 2010-03-17 19:50:16 +0100
From: @mlkersten
The may release has been superseded with a few releases. If the problem re-appears on Mac OS depends on our support line for that platform.
## Comment 11853
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2804854 at http://sourceforge.net/support/tracker.php?aid=2804854
| .gdk_lock | https://api.github.com/repos/MonetDB/MonetDB/issues/2096/comments | 0 | 2020-11-30T10:21:22Z | 2024-06-28T13:25:12Z | https://github.com/MonetDB/MonetDB/issues/2096 | 753,349,140 | 2,096 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-11 02:34:10 +0200
From: francois guerin <<fguerin>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-06-11 03:20:44 +0200
## Comment 11835
Date: 2009-06-11 14:34:10 +0200
From: francois guerin <<fguerin>>
Hi,
according to the "The Mapi Client Utility" section in the XQuery documentation, to add a local XML document, you can use the command line:
mclient -lx --collection="my-collection" --input="my-document" < /tmp/my_document.xml
you should then have (with the command pf:documents() ) that answer below:
<document updatable="false" url="my-document" collection="my-collection">my-document</document>
but instead of this, you get:
<document updatable="false" url="my-document my-collection" collection="my-document my-collection">my-document my-collection</document>
it seems Mapi concatenes the collection name and the document name in each slot...
(FYI, i use the MonetDB May release on a MacBook 32bits - install options: --enable-xquery --enable-optimise)
## Comment 11836
Date: 2009-06-11 15:20:44 +0200
From: @sjoerdmullender
Bug has been fixed in the stable branch.
Test added as pathfinder/tests/BugTracker/Tests/stream-document.SF-2804823.
The problem was a discrepancy between what the client sent as separator between document name and collection name (a space) and what the server expected (a comma).
## Comment 11837
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2804823 at http://sourceforge.net/support/tracker.php?aid=2804823
| The Mapi Client Utility | https://api.github.com/repos/MonetDB/MonetDB/issues/2095/comments | 0 | 2020-11-30T10:21:19Z | 2024-06-27T11:40:03Z | https://github.com/MonetDB/MonetDB/issues/2095 | 753,349,107 | 2,095 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-10 02:51:58 +0200
From: @koelma
To: @sjoerdmullender
Version: -- development
Last updated: 2009-07-01 05:40:17 +0200
## Comment 11829
Date: 2009-06-10 14:51:58 +0200
From: @koelma
I compiled the May2009 release on two machines. The first runs 64bit CentOS 5.2 and the second runs 32bit Fedora 8.
The 64bit client can connect to the 32bit server, but the 32bit client cannot connect to the 64bit server:
!incomplete challenge '9aEHC64YK'
BTW, both run the same version of OpenSLL: OpenSSL 0.9.8d
## Comment 11830
Date: 2009-06-11 10:11:48 +0200
From: @sjoerdmullender
I compiled a 32 bit version on my (64 bit) Fedora 10 system, and I was able to connect to the 64 bit server with no problem.
## Comment 11831
Date: 2009-06-23 11:55:25 +0200
From: @drstmane
I just successfully did connect with a 32-bit client to a 64-bit server and vice versa for MIL (M4), XQuery (M4), MAL (M5) & SQL (M5).
Dennis,
could you please check again and report?
Stefan
## Comment 11832
Date: 2009-07-01 17:13:16 +0200
From: @koelma
Well, of course the original 32bit client still cannot connect to the 64bit server, but I installed the same Monetdb release on a virtual machine also running Fedora8 32bit and that client can connect to the server. So, I assume there is something wrong in the "configuration" of the original 32bit (real) machine and I'll stop using it. Not worth spending more time on this.
## Comment 11833
Date: 2009-07-01 17:40:17 +0200
From: @sjoerdmullender
Let's call it a glitch.
## Comment 11834
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2804134 at http://sourceforge.net/support/tracker.php?aid=2804134
| 32bit mclient fails to connect to 64bit server | https://api.github.com/repos/MonetDB/MonetDB/issues/2094/comments | 0 | 2020-11-30T10:21:15Z | 2024-06-28T13:25:11Z | https://github.com/MonetDB/MonetDB/issues/2094 | 753,349,071 | 2,094 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-09 02:49:23 +0200
From: @arjenderijke
To: @njnes
Version: -- development
Last updated: 2009-06-15 09:29:15 +0200
## Comment 11825
Date: 2009-06-09 14:49:23 +0200
From: @arjenderijke
Using the may 2009 source tarball on a standard cwi desktop, doing a add table drop constraint command in sql, the database schema administration is corrupted. If you run the attached script, the command "/mclient -lsql -ddatabasename -D" reports 2 foreign key constraints, but there are 4. The same thing happens if you do the add constraint before the drop constraint. The script is the simplest situation where the error occurs.
If you replace "ALTER TABLE TABLE_B DROP CONSTRAINT UNQ_VALUE_C;" with
"ALTER TABLE TABLE_C DROP CONSTRAINT FK_TABLE_C_TABLE_D_ID;" the error also occurs.
If you replace it with "ALTER TABLE TABLE_C DROP CONSTRAINT FK_TABLE_C_TABLE_A_ID;", the error does not occur.
## Comment 11826
Date: 2009-06-15 21:29:15 +0200
From: @njnes
fixed by using leftjoins
## Comment 11827
Date: 2009-06-15 21:30:24 +0200
From: @njnes
a test was added to the bugtracker-2009 directory (alter_table_drop_constraint.SF-2803477)
## Comment 11828
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2803477 at http://sourceforge.net/support/tracker.php?aid=2803477
| alter table drop contraint error | https://api.github.com/repos/MonetDB/MonetDB/issues/2093/comments | 0 | 2020-11-30T10:21:12Z | 2024-06-27T11:40:01Z | https://github.com/MonetDB/MonetDB/issues/2093 | 753,349,024 | 2,093 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-09 02:07:57 +0200
From: francois guerin <<fguerin>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-08-06 04:13:13 +0200
## Comment 11818
Date: 2009-06-09 14:07:57 +0200
From: francois guerin <<fguerin>>
When i attempt to insert a file in my MonetDB database, the document shredding crashes with the error:
xquery>pf:add-doc("/MonetDB/mercredi.xml","mercredi.xml","final")
more><>
GDKmmap(430702592) fails, try to free up space [memory in use=158280300,virtual memory in use=0]
GDKmmap(430702592) result [mem=158280300,vm=0]
MAPI = monetdb@localhost:50000
QUERY = pf:add-doc("/MonetDB/mercredi.xml","mercredi.xml","final")
ERROR = !ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
!ERROR: [shred_url]: first error was:
!ERROR: HEAPextend: failed to extend to 430598008 for 05/522tail
!ERROR: shredBAT_extend: BATextend["_attr_own"](107649502 to 107649502) fails
!ERROR: CMDshred_url: operation failed.
Timer 638806.145 msec
The xml file can be accessed at the address: ftp://fguerin.inria.perso.neuf.fr/mercredi.xml.bz2
it's about 4-5Go and well-formed (i checked it)
I installed the lastest version of MonetDB ("May") with the options --enable-xquery --enable-optimize
on several OS (mandriva, debian and macosx).
## Comment 11819
Date: 2009-06-09 16:32:34 +0200
From: @drstmane
Is your OS and your MonetDB 32-bit or 64-bit?
## Comment 11820
Date: 2009-06-09 16:41:42 +0200
From: @yzchang
On Mac OS, I suspect MonetID is compiled for 32-bits.
By default, (my) gcc on Mac produces 32-bits binaries, and with monetdb-install.sh, there is no option to specify that it should produce 64-bits binaries. I installed the stable nightly build yesterday, and tried to shred the same document, and I got similar error. Moreover, if the document is shredded as updatable doc., Mserver segmentation faults.
I will (try to) compile monet on my mac for 64-bits to see if the problem still exists.
Below are copy-paste of what I did, and the error messages:
$monetdb-install.sh --prefix=/Users/jennie/mdb_may2009 --enable-optimize --enable-xquery --nightly=stable
[Mon Jun 8 23:31:50 CEST 2009]
[leopard:/Users/jennie/mdb_may2009/bin]
$ Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.30.1
based on GDK v1.30.1
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for i386-apple-darwin9.7.0/32bit with 32bit OIDs; dynamically
linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.13.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>shred_doc("/Users/jennie/tmp/mercredi.xml", "mercredi.xml",
"mercredi.xml", 10LL);
shredding with holes: pagesize=16384, fillsize=14746
GDKmmap(376438784) fails, try to free up space [memory in
use=157277132,virtual memory in use=79298560]
GDKmmap(376438784) result [mem=157277132,vm=79298560]
Segmentation fault
[Mon Jun 8 23:38:08 CEST 2009]
[leopard:/Users/jennie/mdb_may2009/bin]
$ ls -lh ~/tmp/mercredi.xml
-rw-r--r-- 1 jennie staff 4.7G May 14 13:25 /Users/jennie/tmp/
mercredi.xml
[Mon Jun 8 23:45:47 CEST 2009]
[leopard:/Users/jennie/mdb_may2009/bin]
$ Mserver --dbinit="module(pathfinder);" MonetDB Server v4.30.1
based on GDK v1.30.1
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for i386-apple-darwin9.7.0/32bit with 32bit OIDs; dynamically
linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.13.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>xmldb_print();
-----------------------------------------
collection alias URI size name
str str str lng type
-----------------------------------------
MonetDB>shred_doc("/Users/jennie/tmp/mercredi.xml", "mercredi.xml",
"mercredi.xml", 0LL);
GDKmmap(430702592) fails, try to free up space [memory in
use=157297100,virtual memory in use=0]
GDKmmap(430702592) result [mem=157297100,vm=0]
!ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
!ERROR: [shred_url]: first error was:
!ERROR: HEAPextend: failed to extend to 430598008 for 02/236tail
!ERROR: shredBAT_extend: BATextend["_attr_own"](107649502 to 107649502)
fails
!ERROR: CMDshred_url: operation failed.
MonetDB>exit();
[Mon Jun 8 23:55:35 CEST 2009]
[leopard:/Users/jennie/mdb_may2009/bin]
$
## Comment 11821
Date: 2009-06-09 16:45:30 +0200
From: @grobian
env CC="gcc -m64" CXX="g++ -m64" ./monetdb-install.sh --ga-helemaal-los
(but that will fail on OSX, unless you have 64-bits variants of the libraries libpcre and openssl)
## Comment 11822
Date: 2009-06-17 12:39:25 +0200
From: @yzchang
This is indeed a 32bits related problem, it works with 64bits monet:
$ env CC="gcc -m64" CXX="g++ -m64" monetdb-install.sh --prefix=/Users/jennie/mdb_may2009_64bits --enable-optimize --enable-xquery
$ Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.30.0
based on GDK v1.30.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for i386-apple-darwin9.7.0/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.13.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>xmldb_print();
-----------------------------------------
collection alias URI size name
str str str lng type
-----------------------------------------
MonetDB>shred_doc("/Users/jennie/tmp/mercredi.xml", "merc.xml", "merc.xml", 10LL);
shredding with holes: pagesize=16384, fillsize=14746
Elapsed time = 34m 05s 860ms 584us [008us/node]
Shredded 1 XML document (merc.xml), total time after commit=2315.454s
The document might be just too large for 32bits, but it should give an error, instead of segmentation fault, which still (i.e., today) happens:
$ monetdb-install.sh --prefix=/Users/jennie/mdb_may2009_32bits --enable-optimize --enable-xquery --nightly=stable
[Wed Jun 17 12:14:17 CEST 2009]
[leopard:/Users/jennie/mdb_may2009_32bits/bin]
$ Mserver --dbinit="module(pathfinder);"
MonetDB Server v4.30.1
based on GDK v1.30.1
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for i386-apple-darwin9.7.0/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.13.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>shred_doc("/Users/jennie/tmp/mercredi.xml", "merc.xml", "merc.xml", 10LL);
shredding with holes: pagesize=16384, fillsize=14746
GDKmmap(301072384) fails, try to free up space [memory in use=103246812,virtual memory in use=0]
GDKmmap(301072384) result [mem=103246812,vm=0]
Segmentation fault
## Comment 11823
Date: 2009-08-06 16:13:13 +0200
From: @mlkersten
A larger machine seems the solution. Albeit some cleanup of error messages could be helpful for the user.
## Comment 11824
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2803460 at http://sourceforge.net/support/tracker.php?aid=2803460
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.
| #GDKmmap(...) fails, try to free up space | https://api.github.com/repos/MonetDB/MonetDB/issues/2092/comments | 0 | 2020-11-30T10:21:08Z | 2024-06-28T13:25:11Z | https://github.com/MonetDB/MonetDB/issues/2092 | 753,348,979 | 2,092 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-06-05 11:50:08 +0200
From: John van Schie <<johnvanschie>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2011-04-28 16:39:01 +0200
## Comment 11808
Date: 2009-06-05 11:50:08 +0200
From: John van Schie <<johnvanschie>>
We are using MonetDB4, Feb2009-SP2, build from source (build log attached) with 64bit OIDS.
The platform is Fedora core 10, with 64 GB RAM (55GB cached) and 99GB free disk space for the dbfarm.
Our application uses mclient to manipulate XML in the database. This morning, I saw a mclient process that did not terminate and is still running after approx. 12 hours. Using strace on the mclient process shows that the process is waiting for blocking I/O. Executing a fresh mclient with the query "1+1" results in a stalled application, that also waits for blocking I/O. (see attached strace). It seems that Mserver stopped sending data to the clients.
To debug this problem, I've generated stack traces of all threads for the Mserver and a list of open files (lsof). The server is still running, and I plan to keep it running unless no more information is needed.
Unfortunately, the server is build with optimisation enabled and cannot share the data, as it is confidential.
## Comment 11809
Date: 2009-06-08 18:04:07 +0200
From: @sjoerdmullender
This looks like a classic deadlock situation:
thread 23 is waiting for a lock in pflock_trycommit,
thread 21 is waiting for a lock in pflock_end,
threads 11, 9, 8, 6, 5, 4, 3, 2 are waiting for a lock in pflock_begin,
threads 19, 7 are waiting for a lock in set_lock.
What might be the case is that all but one of the threads waiting in pflock_begin and the two threads waiting in pflock_trycommit and pflock_end are all waiting for the same lock (PF_META_LOCK) which might be held by that one pflock_begin thread, which itself could be waiting for another lock (PF_SHORT_LOCK). Perhaps one of the other two threads waiting in set_lock has PF_SHORT_LOCK and is waiting for yet another lock.
In any case, this seems an area where Peter has the expertise.
## Comment 11810
Date: 2009-06-09 17:08:19 +0200
From: @peterboncz
Hi John,
Thanks for the bug report. It is hard to say what has happenend, it could be that the so-called short lock, which is apparently taken but not freed by an interpreter thread is not given back. This in the end blocks all incoming queries.
The most useful info you attached is the gdb trace. However, it would really help if you could send me the last (~12) queries that went into the server. It would already be good to know whether these are read-only, document managment (add_doc/del_doc) or update queries. There appears to be at least one update query there.
Another possible cause of deadlocks is sometimes bad error handling. Therefore, if there have been anby error messages coming out of that MonetDB instance, that would also be great to know.
I will try to keep thinking, but if there is any additional information that you can share, it would greatly help the chances of finiding a solution/fix.
thanks,
Peter
## Comment 11811
Date: 2009-06-12 11:44:15 +0200
From: John van Schie <<johnvanschie>>
Peter,
I've attached a query log (querylog.log) that contains the requested information. In fact, it is the tail of the full query log. Each query in the log is assigned a number and when the query returns, the duration of the query is printed. So we know that query 1144 returned a non-zero exit code and query 1145, 1146 and 1147 never returned.
Although I'm not able to supply you the exact documents that are referenced in the query log, I could explain the structure of the documents if required.
Hope this helps in finding the cause.
Cheers,
John
## Comment 11812
Date: 2009-07-09 13:32:55 +0200
From: John van Schie <<johnvanschie>>
Peter,
Is there anything else I could do to provide more information for you? For what it's worth, we haven't encountered this problem any more, so it seems a really exceptional case.
Cheers,
John
## Comment 11813
Date: 2009-07-09 20:32:53 +0200
From: @peterboncz
John,
I am very sorry I missed your query log attach on June 12. Either the sourceforge notification mail (as it is assigned to me= got lost or I mssed it. SF is a bit crappy, so feel free to write me a ping message in the future when you respond, then you are sure I see it quickly.
The querylog is very useful and shows that one complicated read query was busy when to concurrent add-docs eneterd the system. This apparently caused a deadlock. I will now start thinking and looking at the code, where this could be.
thanks
Peter
1144: Thu Jun 04 20:39:08 CEST 2009 storeLargeXQueryResultToFile (file: /tmp/jobGen19669.xml):
element job {attribute tool {"general-purpose/mime-tool"},attribute project { "prj_xx"}, for $xirafNode in subsequence( for $xirafIter in (
doc("prj_xx.xml")//file[properties/stream/@xstart and properties/stream/@xend]
)
where $xirafIter/@xid
and not($xirafIter/container/@tool[.="general-purpose/mime-tool"])and not(some $x in (for $taskIter in doc("50E5E1E3-F45A-ED1F-8122-963D5A04DDE8.xml")//run[@tool="general-purpose/mime-tool"]//task/@xid return $taskIter cast as xs:integer) satisfies $x = $xirafIter/@xid)
and $xirafIter/properties/stream/@xstart
return $xirafIter, 327681, 16384)
return element { "item" } {$xirafNode/@xid,if (exists($xirafNode/properties/point/@xpoint)) then
($xirafNode/properties/point/@xpoint, $xirafNode/../../properties/stream/@xstart, $xirafNode/../../properties/stream/@xend)
else
($xirafNode/properties/stream/@xstart, $xirafNode/properties/stream/@xend)
,element properties { element property {attribute key {"error-trace-info-1"},attribute value {zero-or-one($xirafNode/properties/path)}}, ()}
}}
1145: Thu Jun 04 20:39:09 CEST 2009 insertXMLDoc:
pf:add-doc("/var/dbtransfer/xiraf19672.xml","-1690507529760011806-62-1244140748843.xml","prj_xx_log.xml")
1146: Thu Jun 04 20:39:09 CEST 2009 insertXMLDoc:
pf:add-doc("/var/dbtransfer/xiraf19673.xml","-9054443763826720862-61-1244140748843.xml","prj_xx_log.xml")
1147: Thu Jun 04 20:49:08 CEST 2009 executeQuery:
1+1
## Comment 11814
Date: 2009-08-13 10:09:20 +0200
From: John van Schie <<johnvanschie>>
Peter,
It seems that I have another case of the same problem. This time it is on a Ubuntu 8.04 LTS machine, x86_64, 64 bits Monet Feb2009-SP2 (incl patch for fast inserting, see a thread in your mail box with the subject 'Slow import of large XML documents'). The machine has 32G RAM and 1.9T free for the DB farm.
I suspect that this incident has the same cause as the incident for which I first reported this bug. The symptoms are equal and the gdb backtraces look very similar. I will attach the gdb traces of this new occurrence as gdb.2.txt. I will also add an query log for you.
Hope this helps in finding the cause.
Cheers,
John
## Comment 11815
Date: 2009-08-13 10:44:44 +0200
From: John van Schie <<johnvanschie>>
In the attached query log, you can see that query 2936, 2937, and 2938 never returned with an answer. In my process list, I can see a mclient process for query 2936, while query 2937 and 2938 are performed via JDBC.
BTW, the XML files contain no confidential data, so could be send to the CWI if needed.
## Comment 11816
Date: 2009-08-14 13:59:27 +0200
From: @drstmane
tagged subject
## Comment 11817
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2801629 at http://sourceforge.net/support/tracker.php?aid=2801629
## Comment 15776
Date: 2011-04-28 16:39:01 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| XQ: Mserver sends no response, client hangs. | https://api.github.com/repos/MonetDB/MonetDB/issues/2091/comments | 0 | 2020-11-30T10:21:05Z | 2024-06-28T13:25:10Z | https://github.com/MonetDB/MonetDB/issues/2091 | 753,348,936 | 2,091 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-29 12:23:31 +0200
From: @lsidir
To: @njnes
Version: -- development
Last updated: 2009-06-15 09:26:40 +0200
## Comment 11804
Date: 2009-05-29 12:23:31 +0200
From: @lsidir
if the following scenario is executed:
create table bug (a int, b int);
insert into bug values (1,1);
insert into bug values (1,2);
insert into bug values (1,3);
create view bug_2 as select * from bug;
create view bug_3 as select * from bug_2 except select * from bug where bug.b=2;
then if:
select * from bug_3;
+---+---+
| a | b |
+===+===+
| 1 | 1 |
| 1 | 3 |
+---+---+
which is correct. But if:
select * from bug_3 limit 1;
0 tuples
which is wrong.
I have only tested to the development branch, not the stable version.
## Comment 11805
Date: 2009-06-09 22:36:41 +0200
From: @njnes
added test to BugTracker-2009/Tests/view-except-limit.SF-2798333
## Comment 11806
Date: 2009-06-09 22:38:18 +0200
From: @njnes
The new test seems to run correctly on the stable branch
## Comment 11807
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2798333 at http://sourceforge.net/support/tracker.php?aid=2798333
| view+except+limit | https://api.github.com/repos/MonetDB/MonetDB/issues/2090/comments | 0 | 2020-11-30T10:21:02Z | 2024-06-28T13:25:09Z | https://github.com/MonetDB/MonetDB/issues/2090 | 753,348,890 | 2,090 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-29 12:16:00 +0200
From: Pawel Lewicki <<plewy>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-07-10 11:54:26 +0200
## Comment 11797
Date: 2009-05-29 12:16:00 +0200
From: Pawel Lewicki <<plewy>>
The same problem as reported in 2014118
SQL queries executed using ODBC driver are not properly transferred. Inserted data has broken utf-8 characters.
Broken data is recognized by "LIKE" queries if using the same driver (ODBC vs native Python bindings).
Windows 32-bit Feb2009-SP2 release.
ODBC driver version is 1.28.04.01
>>> import MonetSQLdb
>>> testStr = 'us\xc5\x82ugi'
>>> conPython= MonetSQLdb.connect(host = 'localhost', user = 'monetdb', password = 'monetdb', lang = 'sql', dbname='demo')
>>> cuPython = con.cursor()
>>> cuPython.execute("CREATE TABLE testtable (testfield varchar(30))")
0
>>> cuPython.execute("INSERT INTO testtable VALUES ('%s')"%testStr)
1
>>> cuPython.execute("SELECT * FROM testtable WHERE testfield LIKE '%s';"%testStr)
1
>>> print cuPython.fetchall()
[('us\xc5\x82ugi',)]
>>>
>>>
>>> import pyodbc
>>> conODBC = pyodbc.connect('DSN=demo')
>>> cuODBC = conODBC.cursor()
>>> cuODBC.execute("SELECT * FROM testtable WHERE testfield LIKE '%s';"%testStr)
<pyodbc.Cursor object at 0x00D322F8>
>>> print cuODBC.fetchall()
[]
>>> cuODBC.execute("INSERT INTO testtable VALUES ('%s')"%testStr)
1
>>> cuODBC.execute("COMMIT;") only Python driver is in autocommit mode
0
>>> cuODBC.execute("SELECT * FROM testtable WHERE testfield LIKE '%s';"%testStr)
<pyodbc.Cursor object at 0x00D31100>
>>> print cuODBC.fetchall()
[('us\xc4\xb9\xe2\x80\x9augi', )]
>>> cuPython.execute("SELECT * FROM testtable")
2
>>> print cuPython.fetchall()
[('us\xc5\x82ugi',), ('us\xc4\xb9\xe2\x80\x9augi',)]
>>> cuODBC.execute("SELECT * FROM testtable")
<pyodbc.Cursor object at 0x00D31100>
>>> print cuODBC.fetchall()
[('us\xc5\x82ugi', ), ('us\xc4\xb9\xe2\x80\x9augi', )]
>>> cuPython.execute("DROP TABLE testtable")
0
## Comment 11798
Date: 2009-06-03 18:01:12 +0200
From: @sjoerdmullender
I am not convinced that the problem is in the ODBC driver. In other words, I need more evidence.
Can you repeat the pyodbc interaction after setting the environment variable ODBCDEBUG to the name of a file where the ODBC driver can dump logging infromation (e.g.
set ODBCDEBUG=C:\odbc.log
). Can you then attach the resulting file to this bug report?
What I did to try out the bug is to create a table like you did, except I inserted just one value consisting of an a-ring (U+00C5, or '\xc4\xa5' in UTF-8). When I try to select with a like clause with the a-ring from a command window, SQLExecDirect is called with a string containing \xc3\x83\xc2\xa5 when I write out the UTF-8 sequence (similar to what you did), and \xe2\x80\xa0 if I use a literal a-ring. This shows that pyodbc (or the Windows ODBC driver manager) translates the input string from (presumably) cp1252 to UTF-8, even though the command window uses cp437.
My exact queries where:
cuODBC.execute('select * from testtable where testfield like \'\xc3\xa5\'')
cuODBC.execute('select * from testtable where testfield like \'Ã¥\'')
and the log shows these queries (and there is absolutely no conversion in the ODBC driver before this gets logged, i.e. these are the exact strings the driver gets from pyodbc):
SQLExecDirect: "select * from testtable where testfield like '<C3><83><C2><A5>'"
SQLExecDirect: "select * from testtable where testfield like '<E2><80><A0>'"
Note that in cp437 (which the console uses, a-ring has the value '\x86', and that this value is interpreted as the dagger (U+2020) in cp1252. The UTF-8 encoding of U+2020 is the 3 byte string shown above.
## Comment 11799
Date: 2009-06-05 14:07:23 +0200
From: Pawel Lewicki <<plewy>>
I updated client and server to May 2009 - no change.
odbc.log:
DllMain 1
DllMain 2
DllMain 2
DllMain 2
SQLAllocHandle Env 0
DllMain 2
new env 1172f28
SQLSetEnvAttr 1172f28 200 3
SQLAllocHandle Dbc 1172f28
new dbc 1174860
SQLGetInfoW 1174860 77
addDbcError 1174860 01004 String data, right-truncated 0
SQLSetConnectAttrW 1174860 115
addDbcError 1174860 HY092 Invalid attribute/option identifier 0
SQLDriverConnectW 1174860 "DSN=monet_demo;" 0
addDbcError 1174860 01004 String data, right-truncated 0
"DSN=monet_demo;" 0
SQLConnect: DSN=monet_demo UID=monetdb PWD=monetdb host=localhost port=50000 database=demo
addDbcError 1174860 01004 String data, right-truncated 0
SQLGetDiagRecW Dbc 1174860 1 0
SQLGetDiagRecW: [MonetDB][ODBC Driver 1.0]String data, right-truncated
SQLGetDiagRecW Dbc 1174860 1 56
SQLGetDiagRecW: [MonetDB][ODBC Driver 1.0]String data, right-truncated
SQLGetDiagFieldW Dbc 1174860 1 8 256
SQLGetDiagFieldW: ISO 9075
SQLGetDiagFieldW Dbc 1174860 1 9 256
SQLGetDiagFieldW: ISO 9075
SQLGetDiagFieldW Dbc 1174860 1 10 256
SQLGetDiagFieldW: MonetDB ODBC/Mapi
SQLGetDiagFieldW Dbc 1174860 1 11 256
SQLGetDiagFieldW: monet_demo
SQLGetDiagRecW Dbc 1174860 2 0
SQLGetFunctions 1174860 999
SQLGetInfoW 1174860 23
SQLGetInfoW 1174860 24
SQLGetInfoW 1174860 1750
addDbcError 1174860 HY096 Invalid information type 0
SQLSetConnectAttrW 1174860 102
SQLSetConnectAttr set autocommit off
SQLGetInfoW 1174860 10002
addDbcError 1174860 01004 String data, right-truncated 0
SQLAllocHandle Stmt 1174860
new stmt 1d440a0
SQLGetStmtAttrW 1d440a0 10010
SQLGetStmtAttrW 1d440a0 10011
SQLGetStmtAttrW 1d440a0 10012
SQLGetStmtAttrW 1d440a0 10013
SQLGetTypeInfoW 1d440a0 93
ODBCInitResult: querytype 1
SQLFetch 1d440a0
SQLGetData 1d440a0 3 4
SQLFreeStmt 1d440a0 0
SQLAllocHandle Stmt 1174860
new stmt 1174ba8
SQLGetStmtAttrW 1174ba8 10010
SQLGetStmtAttrW 1174ba8 10011
SQLGetStmtAttrW 1174ba8 10012
SQLGetStmtAttrW 1174ba8 10013
SQLFreeStmt 1174ba8 0
SQLExecDirectW 1174ba8
SQLExecDirect: "SELECT * FROM testtable WHERE testfield LIKE 'usługi';"
ODBCInitResult: querytype 1
SQLNumResultCols 1174ba8
SQLRowCount 1174ba8
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLFetch 1174ba8
SQLFreeStmt 1174ba8 0
SQLExecDirectW 1174ba8
SQLExecDirect: "INSERT INTO testtable VALUES ('usługi')"
ODBCInitResult: querytype 2
SQLNumResultCols 1174ba8
SQLRowCount 1174ba8
SQLFreeStmt 1174ba8 0
SQLExecDirectW 1174ba8
SQLExecDirect: "COMMIT;"
ODBCInitResult: querytype 4
SQLNumResultCols 1174ba8
SQLRowCount 1174ba8
SQLFreeStmt 1174ba8 0
SQLExecDirectW 1174ba8
SQLExecDirect: "SELECT * FROM testtable WHERE testfield LIKE 'usługi';"
ODBCInitResult: querytype 1
SQLNumResultCols 1174ba8
SQLRowCount 1174ba8
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLFetch 1174ba8
SQLGetData 1174ba8 1 1
SQLFetch 1174ba8
SQLFreeStmt 1174ba8 0
SQLExecDirectW 1174ba8
SQLExecDirect: "SELECT * FROM testtable"
ODBCInitResult: querytype 1
SQLNumResultCols 1174ba8
SQLRowCount 1174ba8
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLDescribeColW 1174ba8 1
addStmtError 1174ba8 01004 String data, right-truncated 0
SQLFetch 1174ba8
SQLGetData 1174ba8 1 1
SQLFetch 1174ba8
SQLGetData 1174ba8 1 1
SQLFetch 1174ba8
SQLFreeStmt 1174ba8 0
SQLFreeHandle Stmt 1174ba8
SQLEndTran Dbc 1174860 1
new stmt 1174ba8
SQLExecDirect: "rollback"
ODBCInitResult: querytype 4
SQLFreeStmt 1d440a0 1
SQLGetInfoW 1174860 1
SQLDisconnect 1174860
SQLFreeHandle Dbc 1174860
SQLFreeHandle Env 1172f28
DllMain 0
## Comment 11800
Date: 2009-06-05 15:56:11 +0200
From: @sjoerdmullender
The log shows that the ODBC driver is called using the SQLExecDirectW interface which is the wide character interface for SQLExecDirect. The parameter to SQLExecDirectW is a UTF-16 string which is translated by the ODBC driver to UTF-8 (there is a well-defined translation--there is no problem here).
I tried the query again, and also a variant:
>>> cuODBC.execute("SELECT * FROM testtable WHERE testfield LIKE '%s'" % testStr)
<pyodbc.Cursor object at 0x00C05C98>
>>> cuODBC.fetchall()
[]
>>> cuODBC.execute(u"SELECT * FROM testtable WHERE testfield LIKE '%s'" % testStr.decode('utf-8'))
<pyodbc.Cursor object at 0x00C05C98>
>>> cuODBC.fetchall()
[('us\xc5\x82ugi', )]
The first uses a UTF-8 encoded string which is translated to wide characters by pyodbc or the ODBC driver manager and then passed to the ODBC driver. The second does the conversion to a Python unicode string explicitly which is then passed to the ODBC driver as wide characters. The first query fails, the second works. The difference is in the conversion to wide characters. The first is done by pyodbc or the ODBC driver manager (I don't know which) and is incorrect, the second is done by explicit code and is correct.
(When I say "incorrect" I mean, the string that is converted to UTF-16 is not interpreted as UTF-8 (which was intended) but as some other encoding.)
From the evidence I've seen so far, I cannot put any blame on the ODBC driver. The problem, as I see it, is in the conversion to UTF-16 by pyodbc (or the ODBC driver manager).
## Comment 11801
Date: 2009-06-10 00:53:35 +0200
From: Pawel Lewicki <<plewy>>
I need to do some more tests but it seems that the problem is solved if I make ODBC queries unicode.
## Comment 11802
Date: 2009-07-10 11:54:26 +0200
From: @sjoerdmullender
As I said, from the evidence I've seen, the problem was one of GIGO (Garbage In, Garbage Out). The input garbage in this case being an input string which was encoded in UTF-8, but the process doing the conversion to UTF-16 not knowing that it was UTF-8 but thinking it was something else. The process doing this unintended conversion is not the MonetDB ODBC Driver, but something which eventually calls the MonetDB ODBC Driver (either the ODBC Driver Manager or pyodbc).
Getting the ODBC Driver Manager or pyodbc to do the intended conversion falls outside the scope of MonetDB. Hence closing this report as Invalid.
## Comment 11803
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2798331 at http://sourceforge.net/support/tracker.php?aid=2798331
| ODBC - broken 'utf-8' data | https://api.github.com/repos/MonetDB/MonetDB/issues/2089/comments | 0 | 2020-11-30T10:20:57Z | 2024-06-28T13:25:09Z | https://github.com/MonetDB/MonetDB/issues/2089 | 753,348,837 | 2,089 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-28 01:56:05 +0200
From: Floris Ouwendijk <<floris233>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-07-20 08:50:55 +0200
## Comment 11793
Date: 2009-05-28 13:56:05 +0200
From: Floris Ouwendijk <<floris233>>
While running MonetDB in production, inserting/removing large XML documents (>1GB), the following segfault was observed. After restarting and having the system continue, a similar dump was observed (see below). Another restart and continue later, the system seems to resume normal operation.
The version of MonetDB is the Feb2009 SP2, built from the super tarball.
MonetDB Server v4.28.4
based on GDK v1.28.4
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.4 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:19251/admin
MonetDB>*** glibc detected *** MonetDB-Feb2009SP2/bin/Mserver: double free or corruption (fasttop): 0x00007fe745aa50f0 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3f13877ec8]
/lib64/libc.so.6(cfree+0x76)[0x3f1387a486]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1[0x7fe9a3d87742]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1(HEAPfree+0x5c)[0x7fe9a3d13040]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1(BATdelete+0x3f9)[0x7fe9a3f88e49]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1[0x7fe9a3d0c04a]
/opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so(PFll_descendant+0x200)[0x1749360]
/opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so[0x16f2bed]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x20f0)[0x73c681c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x4f)[0x73d447f]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_var+0x15e)[0x73d48aa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x4e9)[0x73c4c15]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x73c5b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x73c5456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x84a)[0x73c4f76]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x73c5456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x4f)[0x73d447f]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_var+0x15e)[0x73d48aa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x4e9)[0x73c4c15]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x73c5b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x73c5456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x29b)[0x73d46cb]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x316)[0x73c4a42]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x73c5b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x73c5b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x73c5cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x73c5456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x29b)[0x73d46cb]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x316)[0x73c4a42]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x73d4114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x73c4aa0]
======= Memory map: ========
00110000-0013a000 r-xp 00000000 08:01 38764816 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_algebra.so.4.28.4
0013a000-00339000 ---p 0002a000 08:01 38764816 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_algebra.so.4.28.4
00339000-00345000 rw-p 00029000 08:01 38764816 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_algebra.so.4.28.4
00400000-00403000 r-xp 00000000 08:01 38765045 /opt/MonetDB-Feb2009SP2/bin/Mserver
00603000-00604000 rw-p 00003000 08:01 38765045 /opt/MonetDB-Feb2009SP2/bin/Mserver
00604000-00605000 rw-p 00604000 00:00 0
00605000-0064b000 r-xp 00000000 08:01 38764820 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_arith.so.4.28.4
0064b000-0084b000 ---p 00046000 08:01 38764820 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_arith.so.4.28.4
0084b000-00875000 rw-p 00046000 08:01 38764820 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_arith.so.4.28.4
00875000-00891000 r-xp 00000000 08:01 38764828 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_bat.so.4.28.4
00891000-00a91000 ---p 0001c000 08:01 38764828 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_bat.so.4.28.4
00a91000-00a99000 rw-p 0001c000 08:01 38764828 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_bat.so.4.28.4
00a99000-00aa8000 r-xp 00000000 08:01 38764840 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_builtin.so.4.28.4
00aa8000-00ca7000 ---p 0000f000 08:01 38764840 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_builtin.so.4.28.4
00ca7000-00cab000 rw-p 0000e000 08:01 38764840 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_builtin.so.4.28.4
00cab000-00cb5000 r-xp 00000000 08:01 38764904 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_str.so.4.28.4
00cb5000-00eb4000 ---p 0000a000 08:01 38764904 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_str.so.4.28.4
00eb4000-00eb9000 rw-p 00009000 08:01 38764904 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_str.so.4.28.4
00eb9000-00ec7000 r-xp 00000000 08:01 38764908 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_sys.so.4.28.4
00ec7000-010c7000 ---p 0000e000 08:01 38764908 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_sys.so.4.28.4
010c7000-010cc000 rw-p 0000e000 08:01 38764908 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_sys.so.4.28.4
010cc000-010d7000 r-xp 00000000 08:01 38764566 /opt/MonetDB-Feb2009SP2/lib/libstream.so.1.28.4
010d7000-012d6000 ---p 0000b000 08:01 38764566 /opt/MonetDB-Feb2009SP2/lib/libstream.so.1.28.4
012d6000-012d7000 rw-p 0000a000 08:01 38764566 /opt/MonetDB-Feb2009SP2/lib/libstream.so.1.28.4
012d7000-012da000 r-xp 00000000 08:01 38764864 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_lock.so.4.28.4
012da000-014d9000 ---p 00003000 08:01 38764864 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_lock.so.4.28.4
014d9000-014db000 rw-p 00002000 08:01 38764864 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_lock.so.4.28.4
014db000-014e4000 r-xp 00000000 08:01 38764856 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_streams.so.4.28.4
014e4000-016e3000 ---p 00009000 08:01 38764856 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_streams.so.4.28.4
016e3000-016e6000 rw-p 00008000 08:01 38764856 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_streams.so.4.28.4
016e6000-01777000 r-xp 00000000 08:01 38765073 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so.0.28.4
01777000-01976000 ---p 00091000 08:01 38765073 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so.0.28.4
01976000-0197e000 rw-p 00090000 08:01 38765073 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so.0.28.4
0197e000-01984000 r-xp 00000000 08:01 38764824 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_ascii_io.so.4.28.4
01984000-01b84000 ---p 00006000 08:01 38764824 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_ascii_io.so.4.28.4
01b84000-01b85000 rw-p 00006000 08:01 38764824 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_ascii_io.so.4.28.4
01c59000-03600000 rw-p 01c59000 00:00 0 [heap]
0395d000-03968000 r-xp 00000000 08:01 38764999 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_malalgebra.so.4.28.4
03968000-03b68000 ---p 0000b000 08:01 38764999 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_malalgebra.so.4.28.4
03b68000-03b6b000 rw-p 0000b000 08:01 38764999 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_malalgebra.so.4.28.4
04892000-04896000 r-xp 00000000 08:01 38764912 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_trans.so.4.28.4
04896000-04a95000 ---p 00004000 08:01 38764912 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_trans.so.4.28.4
04a95000-04a97000 rw-p 00003000 08:01 38764912 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_trans.so.4.28.4
04d33000-04d36000 r-xp 00000000 08:01 38764812 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_alarm.so.4.28.4
04d36000-04f35000 ---p 00003000 08:01 38764812 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_alarm.so.4.28.4
04f35000-04f37000 rw-p 00002000 08:01 38764812 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_alarm.so.4.28.4
04f37000-04f39000 rw-p 04f37000 00:00 0
0557e000-0558b000 r-xp 00000000 08:01 38764844 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_constant.so.4.28.4
0558b000-0578a000 ---p 0000d000 08:01 38764844 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_constant.so.4.28.4
0578a000-0578f000 rw-p 0000c000 08:01 38764844 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_constant.so.4.28.4
05f4c000-05f50000 r-xp 00000000 08:01 38764868 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_logger.so.4.28.4
05f50000-06150000 ---p 00004000 08:01 38764868 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_logger.so.4.28.4
06150000-06152000 rw-p 00004000 08:01 38764868 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_logger.so.4.28.4
062dc000-062f9000 r-xp 00000000 08:01 38764880 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_monettime.so.4.28.4
062f9000-064f8000 ---p 0001d000 08:01 38764880 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_monettime.so.4.28.4
064f8000-06500000 rw-p 0001c000 08:01 3Aborted
MonetDB Server v4.28.4
based on GDK v1.28.4
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.4 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:19251/admin
MonetDB>*** glibc detected *** MonetDB-Feb2009SP2/bin/Mserver: double free or corruption (fasttop): 0x00007f8bd0e2d900 ***
======= Backtrace: =========
/lib64/libc.so.6[0x3f13877ec8]
/lib64/libc.so.6(cfree+0x76)[0x3f1387a486]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1[0x7f8ce6afe742]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1(HEAPfree+0x5c)[0x7f8ce6a8a040]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1(BATdelete+0x3f9)[0x7f8ce6cffe49]
/opt/MonetDB-Feb2009SP2/lib/libbat.so.1[0x7f8ce6a8304a]
/opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so(PFll_descendant+0x200)[0x1dad360]
/opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so[0x1d56bed]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x20f0)[0x484881c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x4f)[0x485647f]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_var+0x15e)[0x48568aa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x4e9)[0x4846c15]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x4847b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x4847456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x84a)[0x4846f76]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x4847456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x4f)[0x485647f]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_var+0x15e)[0x48568aa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x4e9)[0x4846c15]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x4847b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x4847456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x29b)[0x48566cb]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x316)[0x4846a42]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x4847b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x1460)[0x4847b8c]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x15ce)[0x4847cfa]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0xd2a)[0x4847456]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_assignment+0x29b)[0x48566cb]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x316)[0x4846a42]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret_seqblock+0xd0)[0x4856114]
/opt/MonetDB-Feb2009SP2/lib/libmonet.so.4(interpret+0x374)[0x4846aa0]
======= Memory map: ========
00110000-0013a000 r-xp 00000000 08:01 38764816 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_algebra.so.4.28.4
0013a000-00339000 ---p 0002a000 08:01 38764816 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_algebra.so.4.28.4
00339000-00345000 rw-p 00029000 08:01 38764816 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_algebra.so.4.28.4
00400000-00403000 r-xp 00000000 08:01 38765045 /opt/MonetDB-Feb2009SP2/bin/Mserver
00603000-00604000 rw-p 00003000 08:01 38765045 /opt/MonetDB-Feb2009SP2/bin/Mserver
00604000-00605000 rw-p 00604000 00:00 0
00605000-0064b000 r-xp 00000000 08:01 38764820 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_arith.so.4.28.4
0064b000-0084b000 ---p 00046000 08:01 38764820 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_arith.so.4.28.4
0084b000-00875000 rw-p 00046000 08:01 38764820 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_arith.so.4.28.4
00875000-00891000 r-xp 00000000 08:01 38764828 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_bat.so.4.28.4
00891000-00a91000 ---p 0001c000 08:01 38764828 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_bat.so.4.28.4
00a91000-00a99000 rw-p 0001c000 08:01 38764828 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_bat.so.4.28.4
00a99000-00aa8000 r-xp 00000000 08:01 38764840 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_builtin.so.4.28.4
00aa8000-00ca7000 ---p 0000f000 08:01 38764840 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_builtin.so.4.28.4
00ca7000-00cab000 rw-p 0000e000 08:01 38764840 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_builtin.so.4.28.4
00cab000-00cb5000 r-xp 00000000 08:01 38764904 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_str.so.4.28.4
00cb5000-00eb4000 ---p 0000a000 08:01 38764904 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_str.so.4.28.4
00eb4000-00eb9000 rw-p 00009000 08:01 38764904 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_str.so.4.28.4
00eb9000-00ec7000 r-xp 00000000 08:01 38764908 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_sys.so.4.28.4
00ec7000-010c7000 ---p 0000e000 08:01 38764908 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_sys.so.4.28.4
010c7000-010cc000 rw-p 0000e000 08:01 38764908 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_sys.so.4.28.4
01118000-01125000 r-xp 00000000 08:01 38764844 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_constant.so.4.28.4
01125000-01324000 ---p 0000d000 08:01 38764844 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_constant.so.4.28.4
01324000-01329000 rw-p 0000c000 08:01 38764844 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_constant.so.4.28.4
01329000-0132c000 r-xp 00000000 08:01 38764562 /opt/MonetDB-Feb2009SP2/lib/libmutils.so.1.28.4
0132c000-0152b000 ---p 00003000 08:01 38764562 /opt/MonetDB-Feb2009SP2/lib/libmutils.so.1.28.4
0152b000-0152c000 rw-p 00002000 08:01 38764562 /opt/MonetDB-Feb2009SP2/lib/libmutils.so.1.28.4
0152c000-01530000 r-xp 00000000 08:01 38764868 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_logger.so.4.28.4
01530000-01730000 ---p 00004000 08:01 38764868 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_logger.so.4.28.4
01730000-01732000 rw-p 00004000 08:01 38764868 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_logger.so.4.28.4
01732000-0173d000 r-xp 00000000 08:01 38764999 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_malalgebra.so.4.28.4
0173d000-0193d000 ---p 0000b000 08:01 38764999 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_malalgebra.so.4.28.4
0193d000-01940000 rw-p 0000b000 08:01 38764999 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_malalgebra.so.4.28.4
01940000-01943000 r-xp 00000000 08:01 38764864 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_lock.so.4.28.4
01943000-01b42000 ---p 00003000 08:01 38764864 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_lock.so.4.28.4
01b42000-01b44000 rw-p 00002000 08:01 38764864 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_lock.so.4.28.4
01b44000-01b47000 r-xp 00000000 08:01 38764812 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_alarm.so.4.28.4
01b47000-01d46000 ---p 00003000 08:01 38764812 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_alarm.so.4.28.4
01d46000-01d48000 rw-p 00002000 08:01 38764812 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_alarm.so.4.28.4
01d48000-01d4a000 rw-p 01d48000 00:00 0
01d4a000-01ddb000 r-xp 00000000 08:01 38765073 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so.0.28.4
01ddb000-01fda000 ---p 00091000 08:01 38765073 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so.0.28.4
01fda000-01fe2000 rw-p 00090000 08:01 38765073 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_pf_support.so.0.28.4
01fe2000-01fe8000 r-xp 00000000 08:01 38764824 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_ascii_io.so.4.28.4
01fe8000-021e8000 ---p 00006000 08:01 38764824 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_ascii_io.so.4.28.4
021e8000-021e9000 rw-p 00006000 08:01 38764824 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_ascii_io.so.4.28.4
021e9000-021ef000 r-xp 00000000 08:01 38764876 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_mmath.so.4.28.4
021ef000-023ee000 ---p 00006000 08:01 38764876 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_mmath.so.4.28.4
023ee000-023f1000 rw-p 00005000 08:01 38764876 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_mmath.so.4.28.4
02462000-02681000 rw-p 02462000 00:00 0 [heap]
02699000-0269d000 r-xp 00000000 08:01 38764912 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_trans.so.4.28.4
0269d000-0289c000 ---p 00004000 08:01 38764912 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_trans.so.4.28.4
0289c000-0289e000 rw-p 00003000 08:01 38764912 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_trans.so.4.28.4
043ac000-043c9000 r-xp 00000000 08:01 38764880 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_monettime.so.4.28.4
043c9000-045c8000 ---p 0001d000 08:01 38764880 /opt/MonetDB-Feb2009SP2/lib/MonetDB4/lib/lib_monettime.so.4.28.4
045c8000-045d0000 rw-p 0001c000 08:01 387648Aborted
## Comment 11794
Date: 2009-07-09 20:48:51 +0200
From: @peterboncz
Hi Floris,
I am sorry it took long for me to notice this bug report. This is a hard one to answer just like that, with this little info.
Feb2009 SP2 dates from 28/2, and one important bug that can cause this was fixed in Feb2009 on April 19:
http://monetdb.cvs.sourceforge.net/viewvc/monetdb/MonetDB/src/gdk/gdk_bbp.mx?r1=1.251&r2=1.252
So the best thing I can cay is that I hope that later versions of Feb2009 as well as May2009 will not exhibit this problem.
Peter
## Comment 11795
Date: 2009-07-20 20:50:55 +0200
From: @mlkersten
Not reproducable as far as i can tell
## Comment 11796
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2797871 at http://sourceforge.net/support/tracker.php?aid=2797871
| Segfault: double free or corruption | https://api.github.com/repos/MonetDB/MonetDB/issues/2088/comments | 0 | 2020-11-30T10:20:53Z | 2024-06-28T13:27:03Z | https://github.com/MonetDB/MonetDB/issues/2088 | 753,348,788 | 2,088 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-28 10:25:10 +0200
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-06-11 04:02:13 +0200
## Comment 11789
Date: 2009-05-28 10:25:10 +0200
From: Wouter Alink <<alink>>
When running
$ mclient -lsql -d<some-database> -D create a dump
mclient seems to cache all data during the dump, causing huge memory usage. (more than 100GB observerd)
This is the accompanying mail conversation:
The log message for that line was (yes, just that single line):
"Fix a potential deadlock.
Suppose you have a largish file with SQL queries and that those
queries are sent to the server in 8K (or so) chunks (as is done in the
doFile function). Also suppose that many of those SQL queries produce
a significant number of rows. What could happen in this situation is
that the first SQL query to produce lots of output is executed. Only
the first 100 or 10000 (depending on the age of your mclient) rows are
produced. The server then continues on with the next query and
produces its results (or the first 100/10000 rows). mclient consumes
the rows of the first query and when at the end of the 100/10000 rows
it needs to ask the server for more results for the query. This means
that mclient has to read all results until it gets to a server prompt
so that it can send the appropriate X command (X-export). However,
chances are that the last part of the query set that mclient had sent
ends in the middle of a query. This means that the server at this
stage needs to read more of a query and cannot cope with an X
command. mclient at the same time is somewhere deep in the Mapi
library reading output from the server and it cannot send the rest of
the queries that the server craves.
The solution is to not limit the output of the server to only the
first 100/10000 rows of each query but to let the server send it all
so that the client doesn't have to send X-export commands."
So I'm not going to change that the way you suggest.
- Tekst uit oorspronkelijke bericht niet weergeven -
Wouter Alink wrote:
> Hello,
>
> I had a look at the code just now... looking for why so much memory
> was used (i think mclient was using 100GB of memory in the end).
>
> I am not familiar with the mapiclient, but perhaps is the following
> diff a solution?
>
> Index: src/mapiclient/MapiClient.mx
> ===================================================================
> RCS file: /cvsroot/monetdb/clients/src/mapiclient/MapiClient.mx,v
> retrieving revision 1.141
> diff -u -r1.141 MapiClient.mx
> --- src/mapiclient/MapiClient.mx 19 May 2009 12:02:59 -0000 1.141
> +++ src/mapiclient/MapiClient.mx 27 May 2009 22:25:24 -0000
> @@ -2048,7 +2048,7 @@
> fprintf(stderr,"%s\n",mapi_error_str(mid));
> exit(2);
> }
> - mapi_cache_limit(mid, -1);
> + /* mapi_cache_limit(mid, -1); */
> if (dump) {
> if (mode == SQL) {
> dump_tables(mid, toConsole, 0);
>
>
> This seems to work for me, (at least the moment mclient's memory
> consumption remains constant), but I can't oversee the consequences.
> Could somebody perhaps say something sensible about it?
> Reasoning behind it: This call to mapi_cache_limit makes rowlimit==-1,
> and this together with cacheall=0, makes mapi_extend_cache (in
> Mapi.mx) allocate more memory each time it is called (so the cache
> becomes as large as the largest table).
> Without this call "mapi_cache_limit(mid, -1);" the default for the
> rowlimit has been set to 100 lines, so with this change the cache will
> get flushed every 100 lines.
>
> I think I should have filed a bug :)
> Wouter
>
> p.s. while investigating this issue i tried to limit the amount of
> memory that mclient would get using "ulimit -v $((256*1024))". This
> revealed that there are a number of places in Mapi.mx where a
> (m)alloc-call goes unchecked. I don't know the MonetDB coding policy
> here, but perhaps they should all at least have an accompanying
> assert? The following one-liner in the clients package reveals some
> issues:
> $ grep "alloc(" -A2 src/mapilib/Mapi.mx
>
>
> 2009/5/25 Wouter Alink <wouter.alink@gmail.com>:
>> Hello,
>>
>> Question: is there any reason for mclient to use (large) amounts of
>> memory during a dump of a sql database?
>>
>> syntax used:
>> $ mclient -lsql -D -dsomedatabase > dump.sql
>>
>> I observe >12 GB of resident memory use when dumping a 2GB (in dump
>> text format) database (it steadily grows), using the May2009 stable
>> branch (of last week)
>>
>> Top shows:
>> 28371 walink 16 0 12.2g 12g 2944 R 87 4.0 10:48.58 mclient
>>
>> I haven't investigated it any further, but I was first of all
>> wondering whether it actually needs these amounts of memory?
>>
>> Greetings,
>> Wouter
>>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> Monetdb-developers mailing list
> Monetdb-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-developers
--
Sjoerd Mullender
## Comment 11790
Date: 2009-06-04 14:07:03 +0200
From: @sjoerdmullender
I have fixed this slightly differently.
When the cache is full, mapi_extend_cache is called. We now first remove all already read items from the cache before resorting to realloc.
Can you check whether this indeed fixes the problem?
## Comment 11791
Date: 2009-06-11 16:02:13 +0200
From: @sjoerdmullender
Closing.
I can't really think of a way to test this in the testweb, so there is no test.
## Comment 11792
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2797767 at http://sourceforge.net/support/tracker.php?aid=2797767
| mclient --dump caches dump | https://api.github.com/repos/MonetDB/MonetDB/issues/2087/comments | 0 | 2020-11-30T10:20:50Z | 2024-06-27T11:39:54Z | https://github.com/MonetDB/MonetDB/issues/2087 | 753,348,749 | 2,087 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-24 01:23:52 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-28 09:55:47 +0200
## Comment 11786
Date: 2009-05-24 01:23:52 +0200
From: @skinkie
(gdb) bt
0 0x0000000000750077 in ?? ()
1 0x00007ffff751df51 in ATOMlen (t=255, src=0x12ae7c8)
at ../../../src/gdk/gdk_atoms.mx:960
2 0x00007ffff751e4fc in ATOMdup (t=255, p=0x12ae7c8)
at ../../../src/gdk/gdk_atoms.mx:1064
3 0x00007fffe33f0330 in res_col_create (tr=0xe57718, t=0x12aceb8,
tn=0x128bcd8 "sys.way_nds", name=0x128bd08 "to_node",
typename=0x128bd28 "int", digi1970-01-01 01:00:32 +0100, scale=0, mtype=255, val=0x12ae7c8)
at ../../../../src/storage/bat/res_table.mx:88
4 0x00007fffe33746b5 in mvc_result_value (m=0x1229578,
tn=0x128bcd8 "sys.way_nds", name=0x128bd08 "to_node",
typename=0x128bd28 "int", digi1970-01-01 01:00:32 +0100, scale=0, p=0x12ae7c8, mtype=255)
at ../../../../src/backends/monet5/sql_result.mx:1215
5 0x00007fffe332a906 in mvc_result_value_wrap (cntxt=0x604a20, mb=0x1291128,
stk=0x12ae0d8, pci=0x12b2ca8)
at ../../../../src/backends/monet5/sql.mx:2063
6 0x00007ffff7cf9275 in runMALsequence (cntxt=0x604a20, mb=0x1291128,
startpc=1, stoppc=0, stk=0x12ae0d8, env=0x0, pcicaller=0x0)
at ../../../src/mal/mal_interpreter.mx:1783
7 0x00007ffff7cf1220 in callMAL (cntxt=0x604a20, mb=0x1291128,
env=0x7fffe2cfbda8, argv=0x7fffe2cfbdf0, debug=0 '\0')
at ../../../src/mal/mal_interpreter.mx:435
8 0x00007fffe336374f in SQLexecutePrepared (c=0x604a20, be=0x126d948,
---Type <return> to continue, or q <return> to quit---
q=0x1278d18) at ../../../../src/backends/monet5/sql_scenario.mx:1190
9 0x00007fffe33639be in SQLengineIntern (c=0x604a20, be=0x126d948)
at ../../../../src/backends/monet5/sql_scenario.mx:1243
10 0x00007fffe3363e88 in SQLengine (c=0x604a20)
at ../../../../src/backends/monet5/sql_scenario.mx:1353
11 0x00007ffff7d31ed2 in runPhase (c=0x604a20, phase=4)
at ../../../src/mal/mal_scenario.mx:602
12 0x00007ffff7d3205f in runScenarioBody (c=0x604a20)
at ../../../src/mal/mal_scenario.mx:647
13 0x00007ffff7d321f6 in runScenario (c=0x604a20)
at ../../../src/mal/mal_scenario.mx:672
14 0x00007ffff7cef124 in MSserveClient (dummy=0x604a20)
at ../../../src/mal/mal_session.mx:492
15 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
16 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
Query:
select to_node from way_tags, way_nds where k = 'amenity' and v = 'bus_station' and way_nds.way = way_tags.way group by way_nds.way, way_nds.to_node having min(to_node);
CREATE TABLE "sys"."way_tags" (
"way" int,
"k" varchar(255),
"v" varchar(1024)
);
CREATE TABLE "sys"."way_nds" (
"way" int,
"idx" int,
"to_node" int
);
But because I don't want to show an active denial of cooperation I also provide a trivial example:
select schema_id from tables group by schema_id having min(schema_id);
## Comment 11787
Date: 2009-05-28 21:55:47 +0200
From: @njnes
properly check types of having. Added test having_min_crash.SF-2795951.sql
## Comment 11788
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2795951 at http://sourceforge.net/support/tracker.php?aid=2795951
## Comment 18230
Date: 2012-12-03 11:27:24 +0100
From: @sjoerdmullender
Changeset [0c080bdaef58](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=0c080bdaef58) 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=0c080bdaef58](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=0c080bdaef58)
Changeset description:
Fix crash in test for bug #2086 (SF 2795951) on systems with many cores.
Not to be propagated.
| Segmentation fault on having min(...) | https://api.github.com/repos/MonetDB/MonetDB/issues/2086/comments | 0 | 2020-11-30T10:20:47Z | 2024-06-27T11:39:53Z | https://github.com/MonetDB/MonetDB/issues/2086 | 753,348,706 | 2,086 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-24 01:19:50 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-28 10:17:52 +0200
## Comment 11783
Date: 2009-05-24 01:19:50 +0200
From: @skinkie
(gdb) bt
0 0x0000000000000000 in ?? ()
1 0x00007fffe33de7ad in insert_types (tr=0x1085828, systype=0x108e618)
at ../../../src/storage/store.mx:972
2 0x00007fffe33e029f in store_init (debug=0, store=store_ro,
logdir=0x627bb0 "sql_logs", dbname=0x627a98 "osm-benelux", stk=0)
at ../../../src/storage/store.mx:1359
3 0x00007fffe33a5660 in mvc_init (debug=0, store=store_ro, stk=0)
at ../../../src/server/sql_mvc.mx:275
4 0x00007fffe3360d1c in SQLinit (c=0x604a20)
at ../../../../src/backends/monet5/sql_scenario.mx:235
5 0x00007ffff7d31008 in initScenario (c=0x604a20, s=0x7ffff7f4f5f0)
at ../../../src/mal/mal_scenario.mx:260
6 0x00007ffff7d31c52 in setScenario (c=0x604a20, nme=0xe2d4d8 "sql")
at ../../../src/mal/mal_scenario.mx:505
7 0x00007ffff7ceed31 in MSscheduleClient (command=0xe2d498 "LIT",
challenge=0x7fffe387eee0 "AP0vmWdfrzg", fin=0xe25e90, fout=0xe25df0)
at ../../../src/mal/mal_session.mx:371
8 0x00007fffe5f87dcd in doChallenge (cmd=0x0, in=0xe25cb0, out=0xe25c30)
at ../../../../src/modules/mal/mal_mapi.mx:479
9 0x00007fffe5f88095 in SERVERlistenThread (Sock=0xd47ba8)
at ../../../../src/modules/mal/mal_mapi.mx:562
10 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
11 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
Database can be found on capella; /export/data1/konink/dbfarm/osm-benelux
## Comment 11784
Date: 2009-05-28 22:17:52 +0200
From: @njnes
we cannot debug this bug. Next time we need the steps leading up to this buggy db.
## Comment 11785
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2795950 at http://sourceforge.net/support/tracker.php?aid=2795950
| Segmentation fault upon start | https://api.github.com/repos/MonetDB/MonetDB/issues/2085/comments | 0 | 2020-11-30T10:20:43Z | 2024-06-28T07:25:30Z | https://github.com/MonetDB/MonetDB/issues/2085 | 753,348,681 | 2,085 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-21 06:04:58 +0200
From: @swingbit
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2011-04-28 16:38:57 +0200
## Comment 11781
Date: 2009-05-21 18:04:58 +0200
From: @swingbit
I am trying to index in PF/Tijah chunks of documents,
where each chunk consists of a subsequence taken from a document list that looks like this:
<docs>
<doc>/net/skadi/export/scratch0/roberto/lhm/alexandria/EP/000000/70/03/70/EP-0700370-B1.xml</doc>
<doc>/net/skadi/export/scratch0/roberto/lhm/alexandria/EP/000000/70/03/80/EP-0700380-B1.xml</doc>
...
</docs>
When doing that, the PF/Tijah index results incorrect if these 3 conditions hold at the same time:
- a stemmer is given as options to tijah:create-ft-index
- a tag whitelist is given as options to tijah:create-ft-index
- the queries for the different chunks are issued in separate mclient sessions
When one of these conditions does not hold, it seems to work fine.
When they all hold, the PF/Tijah index seems to contain only the first chunk (plus some little junk).
Two queries follow, for the indexing of two consecutive chunks, each 10 documents long.
chunk1.xq:
let $path := "/net/skadi/export/scratch0/roberto/lhm/"
let $opt := <TijahOptions stemmer="snowball-english" whitelist="abstract description claim"/>
return (
tijah:create-ft-index(("alexandria"), $opt),
for $i in subsequence(doc(concat($path,"alexandria_doclist_net.xml"))//doc, 1, 10)
return pf:add-doc($i,$i,"alexandria")
)
chunk2.xq:
let $path := "/net/skadi/export/scratch0/roberto/lhm/"
return (
for $i in subsequence(doc(concat($path,"alexandria_doclist_net.xml"))//doc, 11, 10)
return pf:add-doc($i,$i,"alexandria")
)
Now we run them using two separate mclient sessions, and look at the tid bat's size.
The second chunk seems to add only a few tuples (whose content doesn't make much sense anyway)
$ mclient -lxq < chunk1.xq
$ mclient -lmil -fraw
mil>bat("tj_DFLT_FT_INDEX_tid1").count().print();
[ 49788 ]
$ mclient -lxq < chunk2.xq
$ mclient -lmil -fraw
mil>bat("tj_DFLT_FT_INDEX_tid1").count().print();
[ 49798 ]
## Comment 11782
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2794890 at http://sourceforge.net/support/tracker.php?aid=2794890
## Comment 15766
Date: 2011-04-28 16:38:57 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PFTIJAH: incremental indexing issue | https://api.github.com/repos/MonetDB/MonetDB/issues/2084/comments | 0 | 2020-11-30T10:20:40Z | 2024-06-28T07:25:30Z | https://github.com/MonetDB/MonetDB/issues/2084 | 753,348,636 | 2,084 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-21 02:29:31 +0200
From: @skinkie
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-06-03 11:36:57 +0200
## Comment 11774
Date: 2009-05-21 14:29:31 +0200
From: @skinkie
1) A user wants to change his monetdb password
2) The default case doesn't work:
alter user monetdb with password 'nietveilig';
!InvalidCredentialsException:setPassword:The administrator cannot set its own password, use changePassword instead
3) At this point a person must Google for the correct syntax, finding out that the documented mentioned in a mailinglist returns:
clients.changePassword("monetdb", "nietveilig");
!syntax error, unexpected IDENT in: "clients"
4) Another way pointed out using mclient -lmal returns
mal>clients.changePassword("monetdb", "nietveilig");
MAPI = monetdb@localhost:50000
QUERY = clients.changePassword("monetdb", "nietveilig");
ERROR = !MALException:verifyPassword:password is not 128 chars long, is it a hex representation of a SHA-2 512-bits password hash?
function user.main():void;
clients.changePassword("monetdb","nietveilig");
end main;
Since the following doesn't work:
explain alter user rullzer with password 'test';
and...
MAPI = monetdb@localhost:50000
QUERY = auth.AUTHSHA2Sum("test", 4, 512);
ERROR = !TypeException:user.main[1]:'auth.AUTHSHA2Sum' undefined in: _1:any := auth.AUTHSHA2Sum(_2:str, _3:int, _4:int)
mal>AUTHSHA2Sum("test", 512);
MAPI = monetdb@localhost:50000
QUERY = AUTHSHA2Sum("test", 512);
ERROR = !TypeException:user.main[1]:'user.AUTHSHA2Sum' undefined in: _1:any := user.AUTHSHA2Sum(_2:str, _3:int)
mal>sha2sum("test", 512);
MAPI = monetdb@localhost:50000
QUERY = sha2sum("test", 512);
ERROR = !TypeException:user.main[1]:'user.sha2sum' undefined in: _1:any := user.sha2sum(_2:str, _3:int)
mal>authorize.sha2sum("test", 512);
MAPI = monetdb@localhost:50000
QUERY = authorize.sha2sum("test", 512);
ERROR = !TypeException:user.main[1]:'authorize.sha2sum' undefined in: _1:any := authorize.sha2sum(_2:str, _3:int)
I wonder what is expected from the user to gets its password from inside MonetDB, without using external tools.
## Comment 11775
Date: 2009-05-21 17:12:14 +0200
From: @grobian
thanks for the report!
how about this? I agree the error message that comes from the backend isn't too clear. I'll see if I can trap it.
(pegasus:stable/sql/src) fabian% $INSTALL_DIR/bin/mclient -lsql -dcapesea
sql>alter user monetdb with password 'nietveilig';
!InvalidCredentialsException:setPassword:The administrator cannot set its own password, use changePassword instead
0 tuples
sql>alter user set password 'nietveilig' using old password 'monetdb';
0 tuples
sql>
## Comment 11776
Date: 2009-05-21 17:16:46 +0200
From: @skinkie
You're welcome :)
Could you add this very deep 'expert knowledge' also to <http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/Client-Authorization.html> ?
## Comment 11777
Date: 2009-05-21 17:34:23 +0200
From: @grobian
I'll try my best to figure out where that piece of "documentation" comes from.
The error message now looks like this:
(pegasus:stable/sql/src) fabian% $INSTALL_DIR/bin/mclient -lsql -ddemo
sql>alter user monetdb with password 'nietveilig';
!ALTER USER: use 'ALTER USER SET [ ENCRYPTED ] PASSWORD xxx USING OLD PASSWORD yyy' when changing your own password
0 tuples
sql>
## Comment 11778
Date: 2009-05-21 18:09:11 +0200
From: @grobian
documentation also updated, needs to be set live once the release gets released, hence Pending state.
## Comment 11779
Date: 2009-06-03 11:36:57 +0200
From: @grobian
released in may2009
## Comment 11780
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2794792 at http://sourceforge.net/support/tracker.php?aid=2794792
| Changing 'monetdb' password; very undocumented | https://api.github.com/repos/MonetDB/MonetDB/issues/2083/comments | 0 | 2020-11-30T10:20:37Z | 2024-06-27T11:39:50Z | https://github.com/MonetDB/MonetDB/issues/2083 | 753,348,595 | 2,083 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-21 12:43:02 +0200
From: @gmodena
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-05-27 03:54:55 +0200
## Comment 11765
Date: 2009-05-21 00:43:02 +0200
From: @gmodena
If I try to run mserver5 stable (20/5 snapshot) I get the following error:
dyld: lazy symbol binding failed: Symbol not found: _SHA512
Referenced from: /opt/monetdb/lib/libmonetdb5.5.dylib
Expected in: flat namespace
dyld: Symbol not found: _SHA512
Referenced from: /opt/monetdb/lib/libmonetdb5.5.dylib
Expected in: flat namespace
Trace/BPT trap
and the process terminates.
The code has been built on MacOSX 10.5.5 (Darwin 9.5.2, root:xnu-1228.8.59~2/RELEASE_I386) with gcc 4.0.1 (shipped by apple).
autoconf 2.61, automake 1.10 and cctools-667.3 (libtool), libssl 0.9.7 (shipped by apple).
## Comment 11766
Date: 2009-05-21 09:42:06 +0200
From: @grobian
does this happen immediately upon startup?
What do the following commands return?
echo /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.*
otool -L /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.*
## Comment 11767
Date: 2009-05-21 12:02:44 +0200
From: @drstmane
Maybe these help a bit further:
===================================================================
2009/05/21 - stmane: buildtools/conf/MonetDB.m4,1.118.2.8
MonetDB5/configure.ag,1.113.2.1
when bailing out on missing requirement PCRE or OpenSSL,
make MonetDB5 configure reveal why (a suitable) PCRE or OpenSSL
was not found
===================================================================
2009/05/21 - stmane: MonetDB5/configure.ag,1.113.2.2
fixed typo: use variable "$have_openssl" instead of string literal "have_openssl"
===================================================================
Could you please `cvs update` your sources and try again?
## Comment 11768
Date: 2009-05-21 12:27:55 +0200
From: @grobian
> fixed typo: use variable "$have_openssl" instead of string literal
> "have_openssl"
that one will probably fix it, compilation might have picked up a header from somewhere else (MacPorts?)
Seems we/libtool ignore(s) undefined symbols hence compilation didn't fail.
## Comment 11769
Date: 2009-05-21 12:49:14 +0200
From: @drstmane
Compilation did fail with testing tonight
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.GNU.32.32.d.1-Darwin9.7.0..2009.05.21_00-09-03/make-k.out.html
which triggered my investigation ;-)
Anyway, testing and informative bug reports as this one by Gabriele help us to fix and improve our code base (here: configure script and checks).
## Comment 11770
Date: 2009-05-22 19:35:47 +0200
From: @gmodena
delirio:~ gm$ echo /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.*
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.12.0.dylib /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.dylib /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.dylib /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.la
delirio:~ gm$ otool -L /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.*
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.12.0.dylib:
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.dylib (compatibility version 18.0.0, current version 18.0.0)
/opt/monetdb/lib/libmonetdb5.5.dylib (compatibility version 18.0.0, current version 18.0.0)
/opt/monetdb/lib/libmutils.1.dylib (compatibility version 32.0.0, current version 32.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.4)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.2)
/opt/monetdb/lib/libbat.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/opt/monetdb/lib/libstream.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/opt/monetdb/lib/libMapi.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.dylib:
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.dylib (compatibility version 18.0.0, current version 18.0.0)
/opt/monetdb/lib/libmonetdb5.5.dylib (compatibility version 18.0.0, current version 18.0.0)
/opt/monetdb/lib/libmutils.1.dylib (compatibility version 32.0.0, current version 32.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.4)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.2)
/opt/monetdb/lib/libbat.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/opt/monetdb/lib/libstream.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/opt/monetdb/lib/libMapi.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.dylib:
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.5.dylib (compatibility version 18.0.0, current version 18.0.0)
/opt/monetdb/lib/libmonetdb5.5.dylib (compatibility version 18.0.0, current version 18.0.0)
/opt/monetdb/lib/libmutils.1.dylib (compatibility version 32.0.0, current version 32.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.4)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.2)
/opt/monetdb/lib/libbat.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/opt/monetdb/lib/libstream.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/opt/monetdb/lib/libMapi.1.dylib (compatibility version 32.0.0, current version 32.0.0)
/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
/opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.la: is not an object file
This with the 20/5 snapshot. The fault happens immediately after startup.
I'm compiling/testing a more recent version right now.
## Comment 11771
Date: 2009-05-22 20:27:10 +0200
From: @grobian
This is a terrible sight. I hate libtool for doing this to you.
I hope the configure check fixed by Stefan now just tells you it is not going to work.
## Comment 11772
Date: 2009-05-27 15:54:55 +0200
From: @grobian
configure now correctly detects an outdated openssl
## Comment 11773
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2794626 at http://sourceforge.net/support/tracker.php?aid=2794626
| dyld: lazy symbol binding failed: Symbol not found: _SHA512 | https://api.github.com/repos/MonetDB/MonetDB/issues/2082/comments | 0 | 2020-11-30T10:20:33Z | 2024-06-27T11:39:49Z | https://github.com/MonetDB/MonetDB/issues/2082 | 753,348,544 | 2,082 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-18 12:40:24 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-28 02:55:45 +0200
## Comment 11762
Date: 2009-05-18 12:40:24 +0200
From: @skinkie
sql>create temporary table testpk (hello int, primary key(hello));
!CONSTRAINT: constraints on temporary tables are not supported
0 tuples
Timer 0.731 msec 0 rows
sql>\d testpk
Table sys.testpk does not exist.
sql>create temporary table testpk (hello int, primary key(hello));
!CREATE TABLE: name 'testpk' already in use
0 tuples
Timer 0.136 msec 0 rows
## Comment 11763
Date: 2009-05-28 14:55:42 +0200
From: @njnes
fixed in stable. Added test temp_table_fail_leaves_data.SF-2793286.sql
## Comment 11764
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2793286 at http://sourceforge.net/support/tracker.php?aid=2793286
| temporary table with primarykey fails, but creates something | https://api.github.com/repos/MonetDB/MonetDB/issues/2081/comments | 0 | 2020-11-30T10:20:29Z | 2024-06-27T11:39:48Z | https://github.com/MonetDB/MonetDB/issues/2081 | 753,348,516 | 2,081 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-15 04:56:30 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-11-15 04:18:13 +0100
## Comment 11756
Date: 2009-05-15 16:56:30 +0200
From: Jan Rittinger <<jan.rittinger>>
I analyzed the failing NFI query (nfi05.xq) and detected the error in a leftjoin in PROC add_content. To me it seems that some properties (the BATjoin relies on) are set incorrectly.
Attached you find the annotated MIL script.
In the following you see the information and the content of the input BAT of add_content (as well as for the join) and the incorrect output (without matches for the string "0").
-------------------------------------------------
h t name
str str type
-------------------------------------------------
[ "batId", "tmp_2053" ]
[ "batCacheid", "1067" ]
[ "hparentid", "0" ]
[ "tparentid", "-766" ]
[ "batSharecnt", "0" ]
[ "batCount", "50" ]
[ "batCapacity", "50" ]
[ "head", "void" ]
[ "tail", "str" ]
[ "batPersistence", "transient" ]
[ "batRestricted", "read-only" ]
[ "batRefcnt", "1" ]
[ "batLRefcnt", "1" ]
[ "batDirty", "dirty" ]
[ "batSet", "0" ]
[ "hsorted", "65" ]
[ "hident", "h" ]
[ "hdense", "1" ]
[ "hseqbase", "0@0" ]
[ "hkey", "1" ]
[ "hvarsized", "1" ]
[ "halign", "2295944" ]
[ "hnosorted", "0" ]
[ "hnosorted_rev", "0" ]
[ "hnodense", "0" ]
[ "hnokey[0]", "0" ]
[ "hnokey[1]", "0" ]
[ "hnonil", "1" ]
[ "hnil", "0" ]
[ "tident", "t" ]
[ "tdense", "0" ]
[ "tseqbase", "0@0" ]
[ "tsorted", "0" ]
[ "tkey", "0" ]
[ "tvarsized", "1" ]
[ "talign", "2295952" ]
[ "tnosorted", "0" ]
[ "tnosorted_rev", "0" ]
[ "tnodense", "0" ]
[ "tnokey[0]", "0" ]
[ "tnokey[1]", "0" ]
[ "tnonil", "0" ]
[ "tnil", "0" ]
[ "batInserted", "0" ]
[ "batDeleted", "0" ]
[ "batFirst", "0" ]
[ "htop", "0" ]
[ "ttop", "200" ]
[ "batStamp", "-1104" ]
[ "lastUsed", "10355727" ]
[ "curStamp", "1108" ]
[ "batCopiedtodisk", "0" ]
[ "batDirtydesc", "dirty" ]
[ "H->heap.dirty", "clean" ]
[ "T->heap.dirty", "clean" ]
[ "head.free", "0" ]
[ "head.size", "0" ]
[ "head.maxsize", "0" ]
[ "head.storage", "absent" ]
[ "head.newstorage", "malloced" ]
[ "head.filename", "no file" ]
[ "tail.free", "200" ]
[ "tail.size", "200" ]
[ "tail.maxsize", "200" ]
[ "tail.storage", "malloced" ]
[ "tail.newstorage", "malloced" ]
[ "tail.filename", "13/1376.tail" ]
[ "H->vheap->dirty", "clean" ]
[ "T->vheap->dirty", "clean" ]
[ "theap.free", "2074" ]
[ "theap.size", "4096" ]
[ "theap.maxsize", "4096" ]
[ "theap.storage", "malloced" ]
[ "theap.newstorage", "malloced" ]
[ "theap.filename", "13/1376.theap" ]
-------------------------
h t name
void str type
-------------------------
[ 0@0, "601998" ]
[ 1@0, "0" ]
[ 2@0, "0" ]
[ 3@0, "0" ]
[ 4@0, "0" ]
[ 5@0, "0" ]
[ 6@0, "0" ]
[ 7@0, "0" ]
[ 8@0, "0" ]
[ 9@0, "0" ]
[ 10@0, "0" ]
[ 11@0, "0" ]
[ 12@0, "0" ]
[ 13@0, "0" ]
[ 14@0, "0" ]
[ 15@0, "0" ]
[ 16@0, "0" ]
[ 17@0, "0" ]
[ 18@0, "0" ]
[ 19@0, "0" ]
[ 20@0, "0" ]
[ 21@0, "0" ]
[ 22@0, "0" ]
[ 23@0, "0" ]
[ 24@0, "0" ]
[ 25@0, "0" ]
[ 26@0, "0" ]
[ 27@0, "0" ]
[ 28@0, "0" ]
[ 29@0, "0" ]
[ 30@0, "0" ]
[ 31@0, "0" ]
[ 32@0, "0" ]
[ 33@0, "0" ]
[ 34@0, "0" ]
[ 35@0, "0" ]
[ 36@0, "0" ]
[ 37@0, "0" ]
[ 38@0, "0" ]
[ 39@0, "0" ]
[ 40@0, "0" ]
[ 41@0, "0" ]
[ 42@0, "0" ]
[ 43@0, "0" ]
[ 44@0, "0" ]
[ 45@0, "0" ]
[ 46@0, "0" ]
[ 47@0, "0" ]
[ 48@0, "0" ]
[ 49@0, "0" ]
-----------------
h t name
void oid type
-----------------
[ 0@0, 3@0 ]
## Comment 11757
Date: 2009-06-11 16:29:19 +0200
From: @sjoerdmullender
What is the expected output of your script? When I run it, I get three times two bats. The first is a 50 element void-str bat where all tail values are the string "0", and the second is a void-oid bat where all tail values are 0@0. And this repeated three times.
This is on an up-to-date stable version.
## Comment 11758
Date: 2009-06-12 16:07:32 +0200
From: Jan Rittinger <<jan.rittinger>>
As you observed correctly the script prints 3 times 2 BATs. The two BATs are input and output to the PROC add_content() that adds strings to the text container and returns the references for all strings.
In my up-to-date stable version the first and the second iteration provide an incorrect single line output (see the void-oid BAT in the initial report). The third iteration provides (on my machine) the expected result (a BAT with void head starting from 0@0 and 49 times 0@0 and 1 time 3@0 in the tail).
## Comment 11759
Date: 2009-11-12 10:25:19 +0100
From: @peterboncz
The script produces input that differs at
[ 0@0, "601998" ]
it has there
[ 0@0, "0" ]
so it seems something is wrong with this report..
## Comment 11760
Date: 2009-11-15 16:18:13 +0100
From: Jan Rittinger <<jan.rittinger>>
The described (buggy) behavior is not observable anymore.
## Comment 11761
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2792307 at http://sourceforge.net/support/tracker.php?aid=2792307
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: BATjoin on strings incorrect. | https://api.github.com/repos/MonetDB/MonetDB/issues/2080/comments | 0 | 2020-11-30T10:20:26Z | 2024-06-28T07:25:29Z | https://github.com/MonetDB/MonetDB/issues/2080 | 753,348,468 | 2,080 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-14 02:51:17 +0200
From: Floris Ouwendijk <<floris233>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-05-20 04:44:48 +0200
## Comment 11751
Date: 2009-05-14 14:51:17 +0200
From: Floris Ouwendijk <<floris233>>
Given the following code, I'd assume to get an empty b element (for a database not containing the given document).
if (doc-available('asdasda'))
then doc('asdasda')
else element b{}
The result happens to be
QUERY = if (doc-available('asdasda'))
ERROR = !ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
!ERROR: [shred_url]: first error was:
!ERROR: shred: cannot stat `asdasda': No such file or directory
!ERROR: CMDshred_url: operation failed.
!ERROR: interpret_params: leftfetchjoin(param 2): evaluation error.
If I do
if (doc-available('asdasda'))
then element a{}
else element b{}
Then i get b.
## Comment 11752
Date: 2009-05-14 16:33:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Hmmm...
I have no good solution for that but I can explain the problem: The algebraic optimizer detected that the if-, then-, and else-branches are independent of each other. Therefore all three expressions (also containing the doc() call) are evaluated in parallel and their respective interaction is only resolved later.
## Comment 11753
Date: 2009-05-14 17:44:50 +0200
From: Jan Rittinger <<jan.rittinger>>
The only clean solution I see is to mimic the side effects in the algebra and remove the error from the doc_tbl MIL proc.
## Comment 11754
Date: 2009-05-20 16:44:48 +0200
From: Jan Rittinger <<jan.rittinger>>
I implemented the side effect for fn:doc (as proposed before) in the algebra:
An error is now only triggered whenever the condition chooses the branch with the non-exisiting document.
Added test (unuseable_doc-available.SF-2791704).
Note: The call to fn:doc (and all subsequent operations) in the then-branch are still evaluated...
## Comment 11755
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2791704 at http://sourceforge.net/support/tracker.php?aid=2791704
| Unuseable 'doc-available' test | https://api.github.com/repos/MonetDB/MonetDB/issues/2079/comments | 0 | 2020-11-30T10:20:23Z | 2024-06-27T11:39:46Z | https://github.com/MonetDB/MonetDB/issues/2079 | 753,348,437 | 2,079 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-13 09:28:26 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-11-11 07:52:21 +0100
## Comment 11740
Date: 2009-05-13 21:28:26 +0200
From: @skinkie
In a simple example the following works:
create table test2 (bla1 double, bla2 double);
insert into test2 values (1,1);
insert into test2 values (1,2);
insert into test2 values (1,3);
select case when (bla1 - bla2) > 0 then 1/(bla1 - bla2) else 0 end from test2;
select case when (bla1 - bla2) > 0 then 1/(bla1 - bla2) else 0 end from test2;
+------------------------+
| isnull_>_sql_sub_bla1 |
+========================+
| 0 |
| 1 |
| 0.5 |
+------------------------+
3 tuples
According to Martin the following example creates a division by zero because they are constants:
select case when (2 - 2) > 0 then (3 - 2)/(2 - 2) else 0 end as "test";
!MALException:calc./:Division by zero
Unlike in PostgreSQL where the output is 0; (Lazy evaluation)
Now in my original query:
select n1.lat, n1.long, n2.lat, n2.long, case when (n2.lat - n1.lat) > 0 then (n2.long - n1.long)/(n2.lat - n1.lat) else 0 end from nodes_legacy as n1, nodes_legacy as n2, segments where node1 = n1.id and node2 = n2.id limit 10;
Also returns division by zero.
But in this case: !ArithmeticException:batcalc./:Division by zero
CREATE TABLE "sys"."nodes_legacy" (
"id" int,
"long" double,
"lat" double,
"uid" int,
"timestamp" timestamptz(7)
);
CREATE TABLE "sys"."segments" (
"way" int,
"node1" int,
"node2" int
);
## Comment 11741
Date: 2009-05-24 03:06:24 +0200
From: @skinkie
https://sourceforge.net/tracker/?func=detail&aid=2593341&group_id=56967&atid=482468
The above problem was fixed by recognizing unsafe functions...
## Comment 11742
Date: 2009-06-07 16:47:21 +0200
From: @mlkersten
The effect is a result of dataflow execution. There is no dependency code between the two blocks that forces a sequential execution.
select case when (2 - 2) > 0 then (3 - 2)/(2 - 2) else 0 end as "test";
barrier _50 := language.dataflow();
_10 := calc.-(A0,A1);
_11 := calc.>(_10,A2);
_12 := calc.isnil(_11);
_14 := calc.ifthenelse(_12,false,_11);
_15 := calc.-(A3,A4);
_16 := calc.-(A5,A6);
_17 := calc./(_15,_16);
_18 := calc.ifthenelse(_14,_17,A7);
exit _50;
## Comment 11743
Date: 2009-06-07 17:01:23 +0200
From: @mlkersten
Unfortunately, the MAL plan can not prohibit such an exception to be raised
in sequential mode either
## Comment 11744
Date: 2009-06-08 10:54:41 +0200
From: @drstmane
A to-be-added test should also cover
ID: 2791356 "Floating point exception"
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2791356&group_id=56967
## Comment 11745
Date: 2009-08-06 16:25:43 +0200
From: @mlkersten
Patched batcalc.mx to take care of runtime division by zero, turning the result into a nil.
## Comment 11746
Date: 2009-08-11 13:11:46 +0200
From: @drstmane
added test for
ID: 2791356 "Floating point exception"
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2791356&group_id=56967
in Aug2009 release branch as
sql/src/test/BugTracker-2009/Tests/Floating_point_exception.SF-2791356.*
Appears to work fine.
## Comment 11747
Date: 2009-08-11 13:12:41 +0200
From: @drstmane
Added test for this bug report
in Aug2009 release branch as
sql/src/test/BugTracker-2009/Tests/Division_by_zero_error.SF-2791361.*
While the other queries work fine,
`select case when (2 - 2) > 0 then (3 - 2)/(2 - 2) else 0 end as "test";`
(still) produces a
"!MALException:calc./:Illegal argument Division by zero"
## Comment 11748
Date: 2009-08-14 14:08:58 +0200
From: @drstmane
tagged subject
## Comment 11749
Date: 2009-11-11 19:52:21 +0100
From: @njnes
the division by zero bug was fixed.
## Comment 11750
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2791361 at http://sourceforge.net/support/tracker.php?aid=2791361
| SQL: Division by zero error | https://api.github.com/repos/MonetDB/MonetDB/issues/2078/comments | 0 | 2020-11-30T10:20:20Z | 2024-06-27T11:39:45Z | https://github.com/MonetDB/MonetDB/issues/2078 | 753,348,394 | 2,078 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-13 09:19:51 +0200
From: @skinkie
To: @mlkersten
Version: -- development
Last updated: 2009-11-15 03:43:59 +0100
## Comment 11728
Date: 2009-05-13 21:19:51 +0200
From: @skinkie
create table test (bla1 int, bla2 int);
insert into test values (1,1);
select case when (bla1 - bla2) > 0 then 1/(bla1 - bla2) else 0 end from test;
Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0x7fffe24f8950 (LWP 9926)]
0x00007fffe888c0cc in CMDcstDIVbat_int_int_int (ret=0x125dfc8, cst=0x125dfb8, l=0x125df68)
at ../../../../src/modules/kernel/batcalc.mx:381
381 *o = c @2 *p;
(gdb) bt
0 0x00007fffe888c0cc in CMDcstDIVbat_int_int_int (ret=0x125dfc8, cst=0x125dfb8, l=0x125df68)
at ../../../../src/modules/kernel/batcalc.mx:381
1 0x00007ffff7d0bb9a in DFLOWstep (t=0x1290c90, fs=0x7fffe2cfb1c8) at ../../../src/mal/mal_interpreter.mx:1672
2 0x00007ffff7d1031b in runDFLOWworker (t=0x1290c90) at ../../../src/mal/mal_interpreter.mx:877
3 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
4 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
## Comment 11729
Date: 2009-06-07 17:10:43 +0200
From: @mlkersten
Added protective test in the code. Creates an exception without segfault.
For the remainder this error message relates to 2791361
## Comment 11730
Date: 2009-06-07 19:25:50 +0200
From: @drstmane
Re-opened to remind us that we should add a test for this bug report
(or at least give a reason why none can / need to be added).
## Comment 11731
Date: 2009-06-07 21:41:44 +0200
From: @mlkersten
As mentioned, any further testing should come from the related bug report.
## Comment 11732
Date: 2009-08-11 13:07:37 +0200
From: @drstmane
Added test in Aug2009 release branch as sql/src/test/BugTracker-2009/Tests/Floating_point_exception.SF-2791356.*
Appears to work fine.
## Comment 11733
Date: 2009-08-12 08:30:52 +0200
From: @mlkersten
Although the crash has been dealt with, there is still an outstanding issue that this behavior is questionable, because the user can avoid the division by zero using if-then constructs. This is not respected by the current code generator, which leads to a runtime error where it should not. A solution has to be found at the code generation level of SQL. So, it remains an open bug with lower priority.
## Comment 11734
Date: 2009-08-12 08:30:53 +0200
From: @mlkersten
Although the crash has been dealt with, there is still an outstanding issue that this behavior is questionable, because the user can avoid the division by zero using if-then constructs. This is not respected by the current code generator, which leads to a runtime error where it should not. A solution has to be found at the code generation level of SQL. So, it remains an open bug with lower priority.
## Comment 11735
Date: 2009-08-14 14:01:09 +0200
From: @drstmane
tagged subject
## Comment 11736
Date: 2009-08-14 14:15:45 +0200
From: @drstmane
Martin,
is your comment related to this "Floating point exception" bug or rather to the "Division by zero error" http://sourceforge.net/support/tracker.php?aid=2791361; cf.
https://sourceforge.net/tracker/?func=detail&aid=2791361&group_id=56967&atid=482468
?
## Comment 11737
Date: 2009-08-14 14:25:01 +0200
From: @mlkersten
It is also related to that one.
## Comment 11738
Date: 2009-11-15 15:43:59 +0100
From: @mlkersten
Covered by a test test/BugTracker-2009/Tests/Division_by_zero_error.SF-2791361
## Comment 11739
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2791356 at http://sourceforge.net/support/tracker.php?aid=2791356
| SQL: Floating point exception | https://api.github.com/repos/MonetDB/MonetDB/issues/2077/comments | 0 | 2020-11-30T10:20:16Z | 2024-06-27T11:39:44Z | https://github.com/MonetDB/MonetDB/issues/2077 | 753,348,357 | 2,077 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-12 04:10:18 +0200
From: Henning Rode <<hrode>>
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2011-04-28 16:38:58 +0200
## Comment 11723
Date: 2009-05-12 16:10:18 +0200
From: Henning Rode <<hrode>>
the following query was running fine a few month ago. however, in the current version it returns a strange error:
let $nexi := "[about(.//keyword, Musik)]"
let $offset := 0
let $limit := 20
let $query_v := concat("//video", $nexi)
let $opt := <TijahOptions ir-model="NLLR" returnNumber="{$limit + $offset}"/>
let $qid_v := tijah:queryall-id($query_v, $opt)
let $nodes_v := subsequence(tijah:nodes($qid_v), $offset, $limit)
let $query_s := concat(".//segment", $nexi)
let $qid_s := tijah:query-id($nodes_v, $query_s, $opt)
let $uri_s := tijah:nodes($qid_s)/@uri
return <results>
{for $rsc in $nodes_v
let $rsc_seg := $rsc//segment[@uri = $uri_s]
return <rsc uri="{$rsc/@uri}" score="{tijah:score($qid_v, $rsc)}">
{for $seg in $rsc_seg
return <seg uri="{$seg/@uri}" score="{tijah:score($qid_s, $seg)}"/>}
</rsc>}
</results>
henning@asbjorn:~/work/vitalas/testing> mclient -lx -p42911 test-vitalas-conceptSearchVideo2.xq
<results><rsc!ERROR: XML Generation: tmp_522 BAT does not have a 9 head.
MAPI = monetdb@localhost:42911
QUERY = let $nexi := "[about(.//keyword, Musik)]"
ERROR = !ERROR:
!ERROR: XML Generation: NULL BAT has a 9 head, but tail is NULL.
!ERROR:
!ERROR: xquery_print_result_main: operation failed.
i have not analysed whether it should be called a pathfinder or pf/tijah bug, but the involved tijah-queries run fine, when executed isolated. the error just occurs in the last part of the query when new elements are created showing the query results.
in order to run the query, one needs to index the attached tiny collection. for instance by using this indexing script modified by the path to the collection source:
let $collname := "vitalasCollection"
let $dir := "/ufs/henning/work/vitalas/collection/"
let $file := "vitalasIRT10h-normalized2_newh.xml"
return pf:add-doc(concat($dir,$file), $file ,$collname)
<>
let $collname := "vitalasCollection"
let $opt := <TijahOptions stemmer="porter-english"/>
return tijah:create-ft-index($collname, $opt)
## Comment 11724
Date: 2009-05-13 11:05:21 +0200
From: Henning Rode <<hrode>>
using peter's MIL logging script i created a log-file in order to see, where exactly the error occurs.
apparently, it happens very much at the end of the query execution during these lines:
if (not(isnil(a0002))) {
ERROR (a0002);
} else {
}
however, the output generated earlier seems corrupt as well.
## Comment 11725
Date: 2009-06-24 16:56:17 +0200
From: Henning Rode <<hrode>>
shortest query that leads to the same error message:
let $opt := <TijahOptions ir-model="NLLR"/>
let $qid_s := tijah:queryall-id("//segment[about(.//keyword, Musik)]", $opt)
let $nodes_s := tijah:nodes($qid_s)
return
for $rsc in $nodes_s
return <seg uri="{$rsc/@uri}"/>
## Comment 11726
Date: 2009-08-14 14:10:39 +0200
From: @drstmane
tagged subject
## Comment 11727
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2790689 at http://sourceforge.net/support/tracker.php?aid=2790689
## Comment 15769
Date: 2011-04-28 16:38:58 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PFtijah: complex scoring query | https://api.github.com/repos/MonetDB/MonetDB/issues/2076/comments | 0 | 2020-11-30T10:20:13Z | 2024-06-28T07:25:29Z | https://github.com/MonetDB/MonetDB/issues/2076 | 753,348,321 | 2,076 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-11 01:08:12 +0200
From: z lh <<zlh>>
To: @njnes
Version: -- development
Last updated: 2009-05-28 10:14:28 +0200
## Comment 11719
Date: 2009-05-11 13:08:12 +0200
From: z lh <<zlh>>
can not update column ,
update the same column several times, the column will always be the first 'update' after restart the server !!!!
if the uBAT is created using the log.* , it will replace the main BAT every time when the server starts .
server : MonetDB-Feb2009-SuperBall-SP2
step :
0. create table t2( a int ) ;
insert into t2 values( 1 ) ;
1. update t2 set a = 2 ;
2. -- stop and restart server
3. update t2 set a = 3 ;
-- update another talbe t1 ( change rows > 1000 )
-- waite untill the log.* is empty ( less than 30s )
-- stop the server
-- restart server
4. select a from t2 ;
-- the result is 2, but it should be 3
case :
-------------------------------------------------
drop table t2 ;
create table t2( a int ) ;
insert into t2 values( 1 ) ;
update t2 set a = 2 ;
-- stop the server(I use Ctrl+C), now , the log.* is not empty
-- [zlh@localhost sql]$ pwd
-- /home/zlh/MonetDB_Feb2009/MonetDB/var/MonetDB5/sql_logs/testdb/sql
--------------------------------------------------
-- restart server, now , the log.* is empty
update t2 set a = 3 ;
select * from t2 ;
drop table t1;
create table t1( a int ) ;
insert into t1 values( 1 ) ;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
insert into t1 select a from t1;
-- 2048 rows
-- waite untill the log.* is empty, !!!!!
-- then stop the server
----------------------------------------------------
-- restart server
select * from t2;
detail :
[zlh@localhost var]$ /home/zlh/MonetDB_Feb2009/MonetDB/bin/mserver5 --dbinit 'include sql; --dbname testdb
MonetDB server v5.10.4, based on kernel v1.28.4
Serving database 'testdb', using 2 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/zlh/MonetDB_Feb2009/MonetDB/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.28.4 loaded
[zlh@localhost ~]$ /home/zlh/MonetDB_Feb2009/MonetDB/bin/mclient -lsql -dtestdb
sql>drop table t2 ;
0 tuples
sql>create table t2( a int ) ;
0 tuples
sql>insert into t2 values( 1 ) ;
Rows affected 1
sql>update t2 set a = 2 ;
Rows affected 1
sql>
[zlh@localhost ~]$ /home/zlh/MonetDB_Feb2009/MonetDB/bin/mclient -lsql -dtestdb
sql>--restart server
0 tuples
sql>update t2 set a = 3 ;
Rows affected 1
sql>select * from t2 ;
+---+
| a |
+===+
| 3 |
+---+
1 tuple
sql>
0 tuples
sql>drop table t1;
0 tuples
sql>create table t1( a int ) ;
0 tuples
sql>insert into t1 values( 1 ) ;
Rows affected 1
sql>insert into t1 select a from t1;
Rows affected 1
sql>insert into t1 select a from t1;
Rows affected 2
sql>insert into t1 select a from t1;
Rows affected 4
sql>insert into t1 select a from t1;
Rows affected 8
sql>insert into t1 select a from t1;
Rows affected 16
sql>insert into t1 select a from t1;
Rows affected 32
sql>insert into t1 select a from t1;
Rows affected 64
sql>insert into t1 select a from t1;
Rows affected 128
sql>insert into t1 select a from t1;
Rows affected 256
sql>insert into t1 select a from t1;
Rows affected 512
sql>insert into t1 select a from t1;
Rows affected 1024
sql>-- 2048 rows
0 tuples
sql>
[zlh@localhost ~]$ /home/zlh/MonetDB_Feb2009/MonetDB/bin/mclient -lsql -dtestdb
sql>select * from t2;
+---+
| a |
+===+
| 2 |
+---+
1 tuple
sql>
[zlh@localhost sql]$ pwd
/home/zlh/MonetDB_Feb2009/MonetDB/var/MonetDB5/sql_logs/testdb/sql
[zlh@localhost sql]$ ll
total 148
-rw-rw-r-- 1 zlh zlh 10 May 11 15:58 log
-rw-rw-r-- 1 zlh zlh 131128 May 11 15:58 log.8
[zlh@localhost sql]$ ll
total 148
-rw-rw-r-- 1 zlh zlh 10 May 11 15:58 log
-rw-rw-r-- 1 zlh zlh 131128 May 11 15:58 log.8
[zlh@localhost sql]$ ll
total 12
-rw-rw-r-- 1 zlh zlh 10 May 11 15:59 log
-rw-rw-r-- 1 zlh zlh 0 May 11 15:59 log.9
## Comment 11720
Date: 2009-05-20 15:51:58 +0200
From: @sjoerdmullender
I can reproduce the problem.
Test added: src/test/BugTracker-2009 lost_update.SF-2790020
## Comment 11721
Date: 2009-05-28 22:14:28 +0200
From: @njnes
this bug is fixed. We now use the delta_log for updates.
## Comment 11722
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2790020 at http://sourceforge.net/support/tracker.php?aid=2790020
| uBAT&logger_manger: can not update column | https://api.github.com/repos/MonetDB/MonetDB/issues/2075/comments | 0 | 2020-11-30T10:20:09Z | 2024-06-27T11:39:42Z | https://github.com/MonetDB/MonetDB/issues/2075 | 753,348,283 | 2,075 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-11 11:07:36 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-28 10:07:14 +0200
## Comment 11715
Date: 2009-05-11 11:07:36 +0200
From: @skinkie
CREATE TABLE "sys"."segments" (
"way" int,
"node1" int,
"node2" int
);
sql>select count(*) from segments;
+-----------+
| L4 |
+===========+
| 343983657 |
+-----------+
CREATE TABLE "sys"."mytemp" (
"row" int,
"way" int,
"long1" double,
"lat1" double,
"long2" double,
"lat2" double
);
insert into mytemp select row_number() over (order by way) as row, way, n1.long, n1.lat, n2.long, n2.lat from nodes_legacy as n1, nodes_legacy as n2, segments where node1 = n1.id and node2 = n2.id;
!TypeException:user.s10_1[110]:'calc.mark_grp' undefined in: _300:any := calc.mark_grp(_298:int)
!TypeException:user.s10_1[111]:'bat.insert' undefined in: _301:any := bat.insert(_292:bat[:oid,:int], _297:oid, _300:any)
0 tuples
Rows affected 343980665
sql>select count(*) from mytemp;
+----+
| L3 |
+====+
| 0 |
+----+
1 tuple
I find the output curious, and the error is actually scary.
## Comment 11716
Date: 2009-05-13 12:57:04 +0200
From: @skinkie
CREATE TABLE "sys"."nodes_legacy" (
"id" int,
"long" double,
"lat" double,
"uid" int,
"timestamp" timestamptz(7)
);
## Comment 11717
Date: 2009-05-28 22:07:14 +0200
From: @njnes
Test added to insert_type_exception.SF-2789976.sql
## Comment 11718
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2789976 at http://sourceforge.net/support/tracker.php?aid=2789976
| TypeException upon insert | https://api.github.com/repos/MonetDB/MonetDB/issues/2074/comments | 0 | 2020-11-30T10:20:06Z | 2024-06-27T11:39:41Z | https://github.com/MonetDB/MonetDB/issues/2074 | 753,348,253 | 2,074 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-08 11:38:30 +0200
From: Bram [Cronos] <<vandabr>>
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @romulogoncalves, @njnes
Last updated: 2019-01-21 14:42:09 +0100
## Comment 11711
Date: 2009-05-08 11:38:30 +0200
From: Bram [Cronos] <<vandabr>>
[This is a repost of my message to the monetdb-users mailing list]
I'm experiencing some strange trigger behaviour. Not sure if I'm simply
missing something, or if I've run into a bug.
create table t1 (id serial, toggle boolean);
create table t2 (id serial, ref bigint);
insert into t1 (toggle) values (false);
insert into t1 (toggle) values (false);
create trigger updateMe
after update on t1 referencing new row new_row
for each row when new_row.toggle = true
insert into t2 (ref) values (new_row.id);
update t1 set toggle = true where id = 1;
After this update statement, I would expect to see *1* row in t2.
Instead, I see two rows:
+----+-----+
| id | ref |
+====+=====+
| 1 | 1 |
| 2 | 2 |
+----+-----+
The "when" clause seems to be ignored entirely -- I can change to "when
1 = 0" and it'll still work.
If I change the trigger to
create trigger updateMe
after update on t1 referencing new row new_row
for each row insert into t2 (ref) values (new_row.id);
something equally odd happens. Instead of doing an insert for each
UPDATED row, it inserts a row for each row present in t1. This seems a
bit odd to me, but again, I could just be misunderstand the way this is
supposed to work. Documentation on triggers is a bit sparse I'm afraid...
Any help on this issue would be more than welcome!
## Comment 11712
Date: 2009-05-13 22:40:04 +0200
From: @njnes
The when 'condition' code is missing as it seems. Implementation will take some time.
## Comment 11713
Date: 2009-08-14 13:57:54 +0200
From: @drstmane
tagged subject
## Comment 11714
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2788876 at http://sourceforge.net/support/tracker.php?aid=2788876
## Comment 15689
Date: 2011-03-28 17:36:34 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 16044
Date: 2011-07-29 11:00:08 +0200
From: @sjoerdmullender
Apr2011-SP2 has been released.
## Comment 16283
Date: 2011-09-16 15:10:42 +0200
From: @sjoerdmullender
The Aug2011 version has been released.
## Comment 17693
Date: 2012-08-24 14:56:06 +0200
From: @sjoerdmullender
Jul2012-SP1 has been released.
## Comment 18046
Date: 2012-11-27 12:58:45 +0100
From: @romulogoncalves
A test was added in the SQL module in the BugTracker_2012 directory.
The test is called:
conditions_when_for_triggers_do_not_work.Bug-2073
And the stable out and err were also added.
## Comment 26813
Date: 2019-01-21 14:42:09 +0100
From: @sjoerdmullender
This was fixed in the Jul2017 release.
| conditions (when) for triggers don't work | https://api.github.com/repos/MonetDB/MonetDB/issues/2073/comments | 0 | 2020-11-30T10:20:02Z | 2024-06-27T11:39:40Z | https://github.com/MonetDB/MonetDB/issues/2073 | 753,348,203 | 2,073 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-06 03:37:03 +0200
From: @arjenderijke
To: @njnes
Version: -- development
Last updated: 2009-05-13 04:27:53 +0200
## Comment 11705
Date: 2009-05-06 15:37:03 +0200
From: @arjenderijke
I use monetdb compiled using the cvs head code checked out today (2009-5-06) on a fedora 10 machine. After connecting to a new and empty database with mclient and sql enabled, i get the following result when running the "select * from tables;" query:
sql>select * from tables;
!TypeException:user.s0_1[16]:'sql.bind' undefined in: _262:bat[:oid,:sht] := sql.bind(_26:str, _3:str, _4:str, _5:int, _252:oid, _261:oid)
!TypeException:user.s0_1[17]:'sql.bind' undefined in: _264:bat[:oid,:sht] := sql.bind(_26:str, _3:str, _4:str, _5:int, _261:oid, _263:oid)
...
!TypeException:user.s0_1[180]:'sql.bind' undefined in: _346:bat[:oid,:sht] := sql.bind(_152:str, _144:str, _169:str, _146:int, _343:oid, _345:oid)
!TypeException:user.s0_1[181]:'sql.bind' undefined in: _348:bat[:oid,:sht] := sql.bind(_152:str, _144:str, _169:str, _146:int, _345:oid, _347:oid)
!MALException:algebra.kdiff:Cannot access descriptor
0 tuples
If i then do: set optimizer='off'; i get the normal results. When i set the optimizers on again, the exceptions return.
## Comment 11706
Date: 2009-05-06 16:10:47 +0200
From: @lsidir
I am rising the priority because it makes sql not work in the development branch.
Also, maybe related, is that pressing tab for auto completion in mclient -lsql will result to the following message:
MAPI = monetdb@localhost:50000
QUERY = SELECT name FROM tables
## Comment 11707
Date: 2009-05-06 16:48:20 +0200
From: @drstmane
Appears to occur only on 64-bit Linux; cf., http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/index_short.html
Seems to appears only after yesterday's (Tue May 5 2009) checkins.
## Comment 11708
Date: 2009-05-06 16:53:36 +0200
From: @mlkersten
yes, the mitosis optimizer has changed and the testweb is not validated against it yet.
If it can not be resolved shortly, this optimizer will be turned off.
## Comment 11709
Date: 2009-05-13 16:27:53 +0200
From: @njnes
in the current version this is fixed. Not sure which optimizer was respondsible though. There are many tests for this in the current test set already.
## Comment 11710
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2787855 at http://sourceforge.net/support/tracker.php?aid=2787855
| Type exception with optimizer on | https://api.github.com/repos/MonetDB/MonetDB/issues/2072/comments | 0 | 2020-11-30T10:19:59Z | 2024-06-27T11:39:39Z | https://github.com/MonetDB/MonetDB/issues/2072 | 753,348,169 | 2,072 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-06 02:21:41 +0200
From: Wouter Alink <<alink>>
To: clients devs <<bugs-clients>>
Version: -- development
Last updated: 2009-07-20 09:48:32 +0200
## Comment 11699
Date: 2009-05-06 14:21:41 +0200
From: Wouter Alink <<alink>>
It seems that there is a problem with both providing data via stdin and via the -s feature in mclient. (see example below).
A possible solution could perhaps be to forbid this use. Another solution would be to define a behaviour: either read the '-s' first or the stdin first. (perhaps this already is the case, but I couldn't find any documentation about it)
$ cat data.dat
1
2
3
4
5
$ N=4; head -n $N data.dat | mclient -lsql -p50151 -dtest -s "copy $N records into aap from STDIN;"
MAPI = monetdb@localhost:50151
QUERY = copy 4 records into aap from STDIN;
ERROR = !SQLException:sql:value ';' while parsing ';' from line 0 field 0 not inserted, expecting type int
!SQLException:importTable:failed to import table
## Comment 11700
Date: 2009-05-07 14:26:05 +0200
From: @sjoerdmullender
Where does it say that this is supported?
If it doesn't say anywhere, this is a feature request, not a bug.
## Comment 11701
Date: 2009-05-07 19:30:09 +0200
From: @drstmane
What about:
{ N=4 ; echo "copy $N records into aap from STDIN;" ; head -n $N data.dat ; } | mclient -lsql -p50151 -dtest
?
## Comment 11702
Date: 2009-05-07 21:55:37 +0200
From: Wouter Alink <<alink>>
as discussed on the monetdb-users list, using either the -s _or_ the stdin works fine (except for other reported/unreported bugs), but the combination fails. (stefan's example works fine).
I can very well imagine that using a combination should not be allowed (and should not even become a feature request), but I feel that the current message is not very helpful.
And, actually (I hadn't thought of this option before), if I would have specified "-i" then the documentation (mclient --help) says it reads from stdin _after_ reading the command line args, but it generates the same error.
After some more tests I discovered that:
- when using the command line args + stdin + mentioning '-i', the semi-colon after "copy $N records into aap from STDIN;" should be left out, so the following does work:
$ echo "1
2
3
4
5" | mclient -lsql -dtest -hskadi -p50151 -i -s "COPY 5 RECORDS INTO aap FROM STDIN"
(notice the omission of ';' after the COPY statement)
If I do exactly the same, but leave out the '-i', no error is displayed, but nothing gets inserted either.
If I use only stdin only:
$ echo "COPY 5 RECORDS INTO aap FROM STDIN;
1
2
3
4
5" | mclient -lsql -dtest -hskadi -p50151
then this works (only if the ';' after the COPY statement is present).
I don't know whether there are two different bugs mentioned in this explanation, but I think there definitely is something wrong.
by the way: the create statement for aap is: "CREATE TABLE aap (x int);"
## Comment 11703
Date: 2009-07-20 21:48:32 +0200
From: @mlkersten
Standard input is ignored in combination with -s.
Closing it as at best it can be considered a niche feature request.
## Comment 11704
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2787825 at http://sourceforge.net/support/tracker.php?aid=2787825
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-clients@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| mclient: stdin + statement | https://api.github.com/repos/MonetDB/MonetDB/issues/2071/comments | 0 | 2020-11-30T10:19:56Z | 2024-06-28T07:25:28Z | https://github.com/MonetDB/MonetDB/issues/2071 | 753,348,131 | 2,071 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-06 02:11:40 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-13 04:25:10 +0200
## Comment 11695
Date: 2009-05-06 14:11:40 +0200
From: @skinkie
sql>CREATE TABLE "sys"."way_nds_9" ( "way" int, "idx" int, "to_node" int);
0 tuples
sql>insert into way_nds_9 select * from way_nds limit 9;
Rows affected 9
sql>set optimizer='';
0 tuples
sql>select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
!MALException:opt.remap:no implementation present
0 tuples
Using optimizer='off' output is generated, and the message is gone.
## Comment 11696
Date: 2009-05-06 14:53:48 +0200
From: @drstmane
optimizer "multiplex" appears to be mandatory:
(with Feb2009-SP2 release:)
$ ( sleep 9 ; ( echo "select optimizer;" ; echo "select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx-1;" ) | mclient -lsql >&2 ) | mserver5 --dbinit='include sql;' --set monet_welcome=no ; for i in '' off history multiplex ; do echo $i ; ( sleep 9 ; ( echo "set optimizer='$i';" ; echo "select optimizer;" ; echo "select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx-1;" ) | mclient -lsql >&2 ) | mserver5 --dbinit='include sql;' --set monet_welcome=no ; done
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>% . table_name
% single_value name
% varchar type
% 173 length
[ "inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,constants,commonTerms,joinPath,accumulators,deadcode,reduce,garbageCollector,dataflow,history,multiplex" ]
% sys.t1, sys.t1, sys.t1, sys.t2, sys.t2, sys.t2 table_name
% way, idx, to_node, way, idx, to_node name
% int, int, int, int, int, int type
% 1, 1, 1, 1, 1, 1 length
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>% . table_name
% single_value name
% varchar type
% 0 length
[ "" ]
MAPI = monetdb@localhost:50000
QUERY = select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
ERROR = !MALException:opt.remap:no implementation present
off
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>% . table_name
% single_value name
% varchar type
% 17 length
[ "history,multiplex" ]
% sys.t1, sys.t1, sys.t1, sys.t2, sys.t2, sys.t2 table_name
% way, idx, to_node, way, idx, to_node name
% int, int, int, int, int, int type
% 2, 1, 9, 2, 1, 9 length
[ 35, 0, 200542, 35, 1, 274057218 ]
[ 35, 1, 274057218, 35, 2, 200550 ]
[ 35, 2, 200550, 35, 3, 200551 ]
[ 35, 3, 200551, 35, 4, 200553 ]
[ 37, 0, 200511, 37, 1, 177231081 ]
[ 37, 1, 177231081, 37, 2, 200513 ]
[ 37, 2, 200513, 37, 3, 177081428 ]
history
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>% . table_name
% single_value name
% varchar type
% 7 length
[ "history" ]
MAPI = monetdb@localhost:50000
QUERY = select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
ERROR = !MALException:opt.remap:no implementation present
multiplex
warning: please don't forget to set your vault key!
(see /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-debug_--enable-optimize_--disable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
>% . table_name
% single_value name
% varchar type
% 9 length
[ "multiplex" ]
% sys.t1, sys.t1, sys.t1, sys.t2, sys.t2, sys.t2 table_name
% way, idx, to_node, way, idx, to_node name
% int, int, int, int, int, int type
% 2, 1, 9, 2, 1, 9 length
[ 35, 0, 200542, 35, 1, 274057218 ]
[ 35, 1, 274057218, 35, 2, 200550 ]
[ 35, 2, 200550, 35, 3, 200551 ]
[ 35, 3, 200551, 35, 4, 200553 ]
[ 37, 0, 200511, 37, 1, 177231081 ]
[ 37, 1, 177231081, 37, 2, 200513 ]
[ 37, 2, 200513, 37, 3, 177081428 ]
## Comment 11697
Date: 2009-05-13 16:25:10 +0200
From: @njnes
indeed set optimizer='' empty or any optimizer sequence where the defaults miss (multiplex and history) will lead to problems. Sinds we plan to replace the way we enable/disable optimizers (using boolean switches) we will not fix this problem.
## Comment 11698
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2787821 at http://sourceforge.net/support/tracker.php?aid=2787821
| Removing all optimizers; 'remap: no implementation present' | https://api.github.com/repos/MonetDB/MonetDB/issues/2070/comments | 0 | 2020-11-30T10:19:52Z | 2024-06-28T07:25:28Z | https://github.com/MonetDB/MonetDB/issues/2070 | 753,348,093 | 2,070 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-06 03:28:10 +0200
From: winston <<wwinston>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-08-05 03:17:31 +0200
## Comment 11686
Date: 2009-05-06 03:28:10 +0200
From: winston <<wwinston>>
Sorry to bother you again, but I am having problems loading documents. I tried loading documents two different ways and I get two different errors.
BACKGROUND: After successfully loading several documents, monetDB crashed and damaged the database which is documented in bug report "crashes on shredding of large XML 1.2 GB XMark document - ID: 2785756"
ACTION TAKEN: So I decided to reload the same files that I previously loaded successfully. I took these steps:
(1) deleted all of the files and directories in %APPDATA%/monetDB,
(2) reran the DB4-XQuery 20090324 Installer to REPAIR the MonetDB4 installation,
(3) restarted MonetDB4 server per your instructions in Bug Report 2693363, and
(4) attempted to reload the same documents that loaded OK previously.
SERVER STARTUP:
C:\MonetDB\MonetDB4>mserver
MonetDB Server v4.28.2
based on GDK v1.28.2
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-pc-win32/32bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
MonetDB>module(mapi);
MonetDB>module(pf_support);
MonetDB>module(logger);
MonetDB>module(mkey);
MonetDB>module(xrpc_server);
MonetDB>module(xrpc_client);
MonetDB>module(pf_standoff);
MonetDB>module(pathfinder);
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.2 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
MonetDB>
=x=x=x=
This is the outcome for the FIRST ATTEMPT to load a document:
C:\MonetDB\MonetDB4>mclient -l xquery
xquery>pf:add-doc("C:\Projects\data\XMarkStandard\fact0.xml","fact0.xml","fact0")
more><>
MAPI = monetdb@localhost:50000
QUERY = pf:add-doc("C:\Projects\data\XMarkStandard\fact0.xml","fact0.xml","fact0")
ERROR = !ERROR: interpret: no matching MIL operator to 'ws_create(int)'.
xquery>
=x=x=x=
This is the outcome for the SECOND ATTEMPT via the ADD DOCUMENT button on the WEB SERVER on Port 50001:
!ERROR: "add-doc execution failed at the remote side"
!ERROR: HTTP/1.1 404
!ERROR: HTTP Response:
<?xml version="1.0" encoding="utf-8"?>
<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
<env:Body>
<env:Fault>
<env:Code>
<env:Value>env:Sender</env:Value>
</env:Code>
<env:Reason>
<env:Text xml:lang="en">Error occurred during execution.
!ERROR: interpret: no matching MIL operator to 'usec()'.
</env:Text>
</env:Reason>
</env:Fault>
</env:Body>
</env:Envelope>
=x=x=x=
Please advise.
## Comment 11687
Date: 2009-05-07 02:46:27 +0200
From: winston <<wwinston>>
I am able to load documents on the server side when I use the shred_doc() server command.
MonetDB>shred_doc("C:\Projects\data\XMarkStandard\fact0.xml","fact0.xml");
## Comment 11688
Date: 2009-05-07 02:48:01 +0200
From: winston <<wwinston>>
Correction: the server side needs to have the backslash escaped, ie, doubled, and a semi-colon is needed at the end of the line.
MonetDB>shred_doc("C:\\Projects\\data\\XMarkStandard\\fact0.xml","fact0.xml");
## Comment 11689
Date: 2009-05-07 03:03:40 +0200
From: winston <<wwinston>>
So, I am now able to load documents again from the server side, but when I issue queries from the client side, I get MIL errors.
C:\MonetDB\MonetDB4>mclient -t -lx q1.xq
MAPI = monetdb@localhost:50000
QUERY = let $auction := doc("fact0.xml") return for $b in $auction//open_auction//listitem return $b
ERROR = !ERROR: interpret: no matching MIL operator to 'usec()'.
Timer 34.586 msec
Press any key to continue . . .
## Comment 11690
Date: 2009-05-07 04:40:19 +0200
From: winston <<wwinston>>
The installation that I am having trouble with is a Dell laptop with Windows XP SP3, Intel Core 2.
ACTION TAKEN: I installed MonetDB on one of my older HP PCs with Win XP SP2, Intel Pentium 4.
RESULTS: The WinXP SP2 installation seems to be working OK. The problems I am encountering are all on the WinXP SP3 on the Dell.
## Comment 11691
Date: 2009-05-07 06:57:29 +0200
From: @drstmane
The problems are most probably triggered by / related to the order in which the modules are loaded.
Could you please try to load modules "mapi" as last one, i.e., only after loading module "pathfinder"?
(Sorry, my mistake when suggesting the work around for the failing loading of only module "pathfinder"...)
## Comment 11692
Date: 2009-05-07 16:25:30 +0200
From: @sjoerdmullender
The problem described here may well be a consequence of http://sourceforge.net/support/tracker.php?aid=2693363. I'm tempted to say, let's first try to resolve that before tackling this.
## Comment 11693
Date: 2009-08-05 15:17:31 +0200
From: @sjoerdmullender
I'm closing the bug since it seems to me to be a consequence of following incorrect instructions (not incorrectly following instructions ;-).
It may well be that there are other problems (such as http://sourceforge.net/support/tracker.php?aid=2693363), but the problem reported here about ws_create(int) not being found can be attributed to the incorrect order in which the modules were loaded.
## Comment 11694
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2787609 at http://sourceforge.net/support/tracker.php?aid=2787609
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.
| Error loading XML documents into new database | https://api.github.com/repos/MonetDB/MonetDB/issues/2069/comments | 0 | 2020-11-30T10:19:49Z | 2024-06-28T07:25:28Z | https://github.com/MonetDB/MonetDB/issues/2069 | 753,348,050 | 2,069 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-05 11:23:48 +0200
From: Alex <<alex_us01>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
CC: @sjoerdmullender
Duplicates: #2010
Last updated: 2010-06-17 15:44:49 +0200
## Comment 11682
Date: 2009-05-05 23:23:48 +0200
From: Alex <<alex_us01>>
I recently downloaded and installed MonetDB modules to Windows XP.
When I open Start->All Programs->MonetDB4->MonetDB XQuery Server
a command window opens and quickly closes.
I interpret this as the server not being able to start.
I also tried to connect to it by invoking Start->All Programs->MonetDB4->MonetDB XQuery Client
and it said:
"Setup connection failed
Press any key to continue . . ."
Please help and fix this soon. Thanks.
## Comment 11683
Date: 2009-05-05 23:48:40 +0200
From: @drstmane
Sorry for the inconveniences.
The problem has been reported before (see below), but we haven't managed to locate and fix the problem, yet.
For a work around, see
ID: 2693363 "PF: mserver does not start with pathfinder option on Windows"
https://sourceforge.net/tracker/index.php?func=detail&aid=2693363&group_id=56967&atid=482468
I consider this report a duplicate of the above mentioned bug report 2693363.
To avoid redundancy and confusion I close this report.
For updates, see report 2693363 and feel free to comment there.
## Comment 11684
Date: 2009-05-07 06:51:05 +0200
From: @drstmane
Alex,
which version of Windows XP are you using?
SP2 or SP3?
32-bit or 64-bit?
Could you please post your answer with ID: 2693363 at
https://sourceforge.net/tracker/index.php?func=detail&aid=2693363&group_id=56967&atid=482468 ?
Stefan
## Comment 11685
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2787535 at http://sourceforge.net/support/tracker.php?aid=2787535
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14115
Date: 2010-06-17 15:44:49 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #2010 ***
| XQuery Server doesn't start in Windows XP | https://api.github.com/repos/MonetDB/MonetDB/issues/2068/comments | 0 | 2020-11-30T10:19:46Z | 2024-06-28T07:25:27Z | https://github.com/MonetDB/MonetDB/issues/2068 | 753,348,020 | 2,068 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-05 08:52:10 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-28 10:12:16 +0200
## Comment 11677
Date: 2009-05-05 20:52:10 +0200
From: @skinkie
sql>select count(*) from way_tags, mytemp, mytemp2 where k= 'highway' and v = 'unclassified' and way_tags.way = mytemp2.way and mytemp2.segment = mytemp.row order by mytemp2.way, mytemp2.segment;
!SELECT: no such column 'mytemp2.way'
It took me some while to figure out that count(*) didn't like order by.
## Comment 11678
Date: 2009-05-05 23:23:04 +0200
From: @drstmane
AFAIR, the SQL standard required order by columns and/or expression to occur in the projection list (select clause) of the query.
Basically, consider order by working on a subset of the projection list (select clause) of the query.
A possible reason herefore is (IMHO) that otherwise (i.e., with not all order by columns present in the result, implicit duplicate elimination might drop tuples that have been used for sorting.
Then the error message is IMHO quite clear in your case: by the time order by get's its turn, all columns are already projected away.
(Let alone that using order by in a query that is supposed to return a single single-attribute tuple, i.e., a single value, does not seems to make much sense, anyway ... ;-))
## Comment 11679
Date: 2009-05-06 00:47:07 +0200
From: @skinkie
As you probably completely understand was the count(*) a debugging thing for *. So my suggestion would be to add some heuristics for keyboard/chair errors... "Hint: Cannot order on a single count(*)."
## Comment 11680
Date: 2009-05-28 22:12:16 +0200
From: @njnes
order by is defined on the result columns, ie if there are no columns (only an unnamed count(*)) the order by cannot find your columns mytemp2.way etc.
## Comment 11681
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2787448 at http://sourceforge.net/support/tracker.php?aid=2787448
| Better error message for count(*) vs order by | https://api.github.com/repos/MonetDB/MonetDB/issues/2067/comments | 0 | 2020-11-30T10:19:43Z | 2024-06-28T07:25:27Z | https://github.com/MonetDB/MonetDB/issues/2067 | 753,347,985 | 2,067 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-05-02 10:04:47 +0200
From: winston <<wwinston>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-11-12 10:52:50 +0100
## Comment 11663
Date: 2009-05-02 22:04:47 +0200
From: winston <<wwinston>>
xquery>pf:add-doc("D:\Projects_Data_2009\data\XMarkStandard\fact8.xml","fact8.xm
l","fact8")
more>
more><>
MAPI = monetdb@localhost:50000
QUERY = pf:add-doc("D:\Projects_Data_2009\data\XMarkStandard\fact8.xml","fact8.x
ml","fact8")
ERROR = !↕GDKmmap(193462272) fails, try to free up space [memory in use=1433139
34,virtual memory in use=1171783680]
GDKmmap(193462272) result [mem=143313934,vm=1171783680]
MAPI = monetdb@localhost:50000
QUERY = pf:add-doc("D:\Projects_Data_2009\data\XMarkStandard\fact8.xml","fact8.x
ml","fact8")
ERROR = !ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
!ERROR: [shred_url]: first error was:
!ERROR: HEAPextend: failed to extend to 193148746 for 10\1001theap
!ERROR: shredBAT_append_str: APPEND-STR[_prop_text](
!ERROR: tale cordelia sick terra wor crutch dates fie slee
p boarded avoid
!ERROR: arbour slippery yet sampson prove within dejected
graze clock
!ERROR: gentleman friendly brass best answering lord front
pitifully
!ERROR: forever expect cool halfpenny very gar post hinge
telling absence
!ERROR: affairs footed murderer author call key bent stran
ger
!ERROR: guildenstern yoke kneeling virtue diadem great cou
nterfeit
!ERROR: bootless cousin honestly councils troyans examinat
ion cruel
!ERROR: fearful chambermaids people prone conspirators lie
until oph
!ERROR: letting abortive appears purposed jour nod souther
ly dearest
!ERROR: vexation affairs theft preventions sparrow opinion
hue two
!ERROR: suddenly year mothers moon majesty tongue mortalit
y thereof
!ERROR: gratify march preventions harmless others intents
awhile alas
!ERROR: tweaks greek weeping renews penny masks shines bat
he pump choke
!ERROR: bawd gerard even beside load fall peeping ), BUNap
pend fails
!ERROR: CMDshred_url: operation failed.
xquery>
## Comment 11664
Date: 2009-05-02 22:19:59 +0200
From: @drstmane
The usual questions:
- Which version of MonetDB? (preferably the output of `Mserver --version`)
- Which OS? (The paths indicate Windows, but which version, and 32-bit or 64-bit?)
- What kind of hardware? (mainly how much main memory?)
- How much free disk space on the partition (or "drive") that your dbfarm is located on?
## Comment 11665
Date: 2009-05-03 08:24:44 +0200
From: @drstmane
I guess from your previous bug report that you are running on 32-bit Windows using the Feb2009 release of MonetDB.
I this case (32-bit Windows), you most probably simply hit the 2 GB (31-bit) address space limitation in combination with address space fragmentation on Win32: While loading that 1.2 GB document, Mserver grows to almost 1.2 GB (vm=1171783680) and then needs to allocate (memory map) an other almost 200 MB (GDKmmap(193462272)) apparently this fails, most probably because there is no single consecutive free range of 200 MB left in remaining <= 800 MB of the 2 GB address space, most probably due to address space fragmentation.
You might want to upgrade to the latest Feb2009-SP2 bug fix release --- we implemented some fixes in Feb2009-SP1 (and hence Feb2009-SP2) to better cope with the memory/address space limitations and fragmentation problems on Win32 --- and start your Mserver freshly only to load that 1.2 GB document.
If that does not help, either, I see only two solution:
1) Migrate to 32-bit Unix (e.g., Linux)
2) (better) migrate to a 64-bit OS using a 64-bit build of MonetDB
Stefan
## Comment 11666
Date: 2009-05-03 08:25:34 +0200
From: @drstmane
ps: it could of course also be that your disk has less than 200 MB free ...
## Comment 11667
Date: 2009-05-03 08:27:22 +0200
From: @drstmane
and: does your server indeed *crash*, or does it just fail to load that document, giving the reported error, but continue running?
## Comment 11668
Date: 2009-05-05 02:46:31 +0200
From: winston <<wwinston>>
Stefan,
Thank you for your assistance.
The 1.2 GB document load crashed the server (i.e. the server process exited and ended) and corrupted the dbfarm so that I can't run queries against the other collections. I will need to reload the dbfarm.
I am running the MonetDB4 20090324 release, the March 2009 release.
I have over 12 GB of disk space left.
I am running WinXP 32-bit on a Dell laptop. The laptop has 2GB ram and that is the maximum that can be installed, so as far as ram is concerned, I am stuck.
When loading the 1.2GB document, I am sure that there was less than 1 GB of ram available, as other Windows processes take up 800KB just after boot and I had a few other programs running too.
I will try to shut down as much as I can and load the document right after a cold boot.
However, I have a few questions:
(1) Does MonetDB always load the full document into RAM when loading?
(2) If I run xquery against the 1.2GB document in the database will MonetDB load the whole document into memory or will MonetDB load a small portion of the document into buffers even if the whole document needs to be scanned?
(3) Can I configure MonetDB to grab 1.2GB + 200KB = 1.5GB on startup via configuration so that the memory is grabbed in advance?
## Comment 11669
Date: 2009-05-05 08:48:38 +0200
From: @drstmane
Winston,
please note that MonetDB will (try to) use virtual memory (swap) and/or memory-mapped files once it runs out of available free physical memory. The problem on 32-bit systems, in particular on Windows, is the 32-bit address space limitation, i.e., the system and/or any process cannot address more than (in theory) 4 GB (2^32) --- in practice it's often as "little" as 3 GB or even 2 GB (2^31). You are most probably hitting this limit, combined with address space fragmentation as explained earlier.
That said, neither during loading nor during querying, MonetDB needs to have the whole document physically in memory, but it needs to have it accessible entirely in the address space --- though having it in physical memory will speed-up processing.
## Comment 11670
Date: 2009-06-05 13:18:45 +0200
From: @peterboncz
This appears to be a scalability problem. Please provide information on your OS, machine and the version of MonetDB you use.
Windoze 32-bits is limited by the 2GB virtual memory limit (no matter how much RAM you have), and there always is fragmentation, so a 1.2GB file won't shred. Use 64-bits windoze, and a 64-bits build.
## Comment 11671
Date: 2009-06-05 13:19:43 +0200
From: @peterboncz
http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/Scalability.htmlScalability
## Comment 11672
Date: 2009-06-05 13:21:12 +0200
From: @peterboncz
sorry, I missed the previous comments in the sf interface, so stefan had already commented about this. anyway, the documentation link describes how you could try to use 3GB on 32-bits windoze. You might just manage, maybe.
## Comment 11673
Date: 2009-08-05 14:54:28 +0200
From: @sjoerdmullender
I just tried shredding the scalefactor-10 XMark document on my 32 bit WIndows machine (2GB RAM, plenty of free disk).
As expected, this failed, but it seems to have failed in a pretty unspectacular way. The client reported an error, and the server just stayed alive. Memory use of the server went up during shredding until it tried to get more than was possible, and then went back to a pretty reasonable level.
The size of the document was 1172322349 bytes (on Linux, i.e. with just LF line endings--on Windows, it would need another 20393169 bytes for the CRs).
I tried this with the newly created stable branch for the upcoming August 2009 release.
I'd say, we can close this bug as Rejected since it involves going beyond the boundaries of what the platform can do.
However, the error message that I got is extremely unclear, so we may want to do something about that:
GDKmmap(278921216) fails, try to free up space [memory in use=146786972,virtual memory in use=1135542272]
GDKmmap(278921216) result [mem=134294220,vm=1121058816]
MAPI = monetdb@localhost:50000
QUERY = pf:add-doc('c:\Documents and Settings\sjoerd\My Documents\XMark-f10.xml','XMark-f10.xml')
ERROR = !ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
!ERROR: [shred_url]: first error was:
!ERROR: HEAPextend: failed to extend to 278712451 for 05\502theap
!ERROR: shredBAT_append_str: APPEND-STR[_prop_text](
!ERROR: ), BUNappend fails
!ERROR: CMDshred_url: operation failed.
## Comment 11674
Date: 2009-08-14 14:10:17 +0200
From: @drstmane
tagged subject
## Comment 11675
Date: 2009-11-12 10:52:50 +0100
From: @peterboncz
This is MXQ running out of memory on 32-bits windows. Nothing unusual, MXQ has scalability limits, certainly on 32-bits windows. Not a bug at all.
## Comment 11676
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2785756 at http://sourceforge.net/support/tracker.php?aid=2785756
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.
| XQ: crashes on shredding of large XML 1.2 GB XMark document | https://api.github.com/repos/MonetDB/MonetDB/issues/2066/comments | 0 | 2020-11-30T10:19:40Z | 2024-06-28T07:25:26Z | https://github.com/MonetDB/MonetDB/issues/2066 | 753,347,944 | 2,066 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-29 08:33:07 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-06 04:30:23 +0200
## Comment 11654
Date: 2009-04-29 08:33:07 +0200
From: @skinkie
CREATE TABLE "sys"."way_nds" (
"way" int,
"idx" int,
"to_node" int
);
[copy into]
sql>ALTER TABLE way_nds ADD CONSTRAINT pk_way_nds PRIMARY KEY (way, idx);
!SQLException:assert:UPDATE: PRIMARY KEY constraint 'way_nds.pk_way_nds' violated
0 tuples
sql>select count(way), way, idx from way_nds group by way, idx having count(way) > 1;
0 tuples
The above error seems to be impossible since the second query is a check for it.
## Comment 11655
Date: 2009-05-13 22:24:12 +0200
From: @skinkie
I am using 32bit oids, on a 64bit compilation.
CREATE TABLE way_nds (way integer, idx integer, to_node integer);
COPY 370896230 RECORDS INTO way_nds from '/export/data1/konink/way_nds.csv' USING DELIMITERS ',', '\n', '''';
## Comment 11656
Date: 2009-06-07 08:41:16 +0200
From: @mlkersten
A test has been added to the test suite.
It indicates that counting compound groups with NULLs leads to problems.
## Comment 11657
Date: 2009-06-07 20:07:58 +0200
From: @drstmane
Aha --- the key seems to be in the info that was lacking in the original bug report: the data contains NULL values!
I cannot recall it exactly from my head but we'd need to check in the SQL semantics for both key constraints and (grouped) counts;
I assume, the former does not allow NULLs --- in that case the error message would be to be expected;
while the latter does ignore / not distinguish NULLs --- in that case the result of the second query would be corrent, too.
In other words, I'm not sure that the given query is indeed a proper check for the primary key constraint, given SQL semantics ...
## Comment 11658
Date: 2009-06-07 20:09:09 +0200
From: @drstmane
ps: you find the respective test in sql/src/test/BugTracker-2009/Tests/primekeyconstraint.SF-2783425.*
## Comment 11659
Date: 2009-06-07 21:20:14 +0200
From: @skinkie
In the way_nds table I know almost beyond reasonable doubt that that table doesn't contain null values; because that file is generated and should have influenced the primary keys of the way table and node table...
## Comment 11660
Date: 2009-06-07 21:46:10 +0200
From: @mlkersten
As the new test illustrates, it at least uncovers an error in counting groups with NULLs.
NULLs are allowed here, because there is no enforced KEY constraint on the table.
The table may have contained nulls that have been produced 'unnoticed' by the table loader.
It may also be a partial correct administration of the failing ALTER,....
## Comment 11661
Date: 2009-08-06 16:30:23 +0200
From: @mlkersten
Seems under control in the test web
## Comment 11662
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2783425 at http://sourceforge.net/support/tracker.php?aid=2783425
| Invalid results for primary key check | https://api.github.com/repos/MonetDB/MonetDB/issues/2065/comments | 0 | 2020-11-30T10:19:35Z | 2024-06-27T11:39:32Z | https://github.com/MonetDB/MonetDB/issues/2065 | 753,347,891 | 2,065 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-29 07:50:10 +0200
From: @drstmane
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-05-27 03:56:19 +0200
## Comment 11649
Date: 2009-04-29 07:50:10 +0200
From: @drstmane
While working fine until Mon Apr 27 2009, compiling with Python fails on SunOS since Tue Apr 28 2009.
For details, look for "checking whether we can compile with Python" in buildtools/conf/MonetDB.m4 and in
/ufs/monet/Testing/Stable/MonetDB/.*-SunOS*..2009.04.2[789]/config.log
* 2009.04.27:
- pegasus/GNU:
configure:21088: checking whether we can compile with Python
configure:21111: gcc -c -g -O2 -D__EXTENSIONS__ -Wall -Wextra -std=c99 -I/net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/include/python2.6 conftest.c >&5
configure:21118: $? = 0
configure:21123: result: yes
- build-x86-sol10/GNU:
configure:29277: checking whether we can compile with Python
configure:29300: gcc -c -g -O2 -D__EXTENSIONS__ -Wall -Wextra -std=c99 -I/opt/csw/include/python2.5 conftest.c >&5
configure:29306: $? = 0
configure:29311: result: yes
- build-x86-sol10/Sun:
configure:29277: checking whether we can compile with Python
configure:29300: cc -c -g -D__EXTENSIONS__ -xc99 -I/opt/csw/include/python2.5 conftest.c >&5
configure:29306: $? = 0
configure:29311: result: yes
* 2009.04.28:
- pegasus/GNU:
configure:21369: checking whether we can compile with Python
configure:21392: gcc -c -g -O2 -Wall -Wextra -std=c99 -I/net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/include/python2.6 conftest.c >&5
In file included from /usr/include/limits.h:36,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/limits.h:122,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/syslimits.h:7,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/limits.h:11,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/include/python2.6/Python.h:19,
from conftest.c:66:
/net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/sys/feature_tests.h:362:2: error: error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001
configure:21399: $? = 1
- build-x86-sol10/GNU:
configure:29540: checking whether we can compile with Python
configure:29563: gcc -c -g -O2 -Wall -Wextra -std=c99 -I/opt/csw/include/python2.5 conftest.c >&5
In file included from /opt/csw/include/python2.5/Python.h:8,
from conftest.c:64:
/opt/csw/include/python2.5/pyconfig.h:941:1: warning: "_XOPEN_SOURCE" redefined
conftest.c:20:1: warning: this is the location of the previous definition
In file included from /opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/include/syslimits.h:45,
from /opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/include/limits.h:11,
from /opt/csw/include/python2.5/Python.h:18,
from conftest.c:64:
/usr/include/sys/feature_tests.h:353:2: error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications"
configure:29569: $? = 1
- build-x86-sol10/Sun:
configure:29540: checking whether we can compile with Python
configure:29563: cc -c -g -xc99 -I/opt/csw/include/python2.5 conftest.c >&5
"/opt/csw/include/python2.5/pyconfig.h", line 941: warning: macro redefined: _XOPEN_SOURCE
"/usr/include/sys/feature_tests.h", line 353: error: "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications"
cc: acomp failed for conftest.c
configure:29569: $? = 2
* 2009.04.29:
- pegasus/GNU:
configure:21459: checking whether we can compile with Python
configure:21482: gcc -c -g -O2 -Wall -Wextra -std=c99 -I/net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/include/python2.6 conftest.c >&5
In file included from /usr/include/limits.h:36,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/limits.h:122,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/syslimits.h:7,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/limits.h:11,
from /net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/include/python2.6/Python.h:19,
from conftest.c:66:
/net/pegasus.ins.cwi.nl/export/scratch/stripe/fabian/gentoo/prefix64/usr/lib/gcc/x86_64-pc-solaris2.11/4.3.2/include-fixed/sys/feature_tests.h:362:2: error: error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001
configure:21489: $? = 1
- build-x86-sol10/GNU:
configure:29626: checking whether we can compile with Python
configure:29649: gcc -c -g -O2 -Wall -Wextra -std=c99 -I/opt/csw/include/python2.5 conftest.c >&5
In file included from /opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/include/syslimits.h:45,
from /opt/csw/gcc3/lib/gcc/i386-pc-solaris2.8/3.4.5/include/limits.h:11,
from /opt/csw/include/python2.5/Python.h:18,
from conftest.c:63:
/usr/include/sys/feature_tests.h:353:2: error "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications"
configure:29655: $? = 1
-build-x86-sol10/Sun:
configure:29626: checking whether we can compile with Python
configure:29649: cc -c -g -xc99 -I/opt/csw/include/python2.5 conftest.c >&5
"/usr/include/sys/feature_tests.h", line 353: error: "Compiler or options invalid for pre-UNIX 03 X/Open applications and pre-2001 POSIX applications"
cc: acomp failed for conftest.c
configure:29655: $? = 2
## Comment 11650
Date: 2009-04-29 10:53:42 +0200
From: @grobian
Python is such a bunch of broken crap.... *sigh*
http://bugs.python.org/issue1759169
Will fix in Gentoo, and won't fix for the rest.
## Comment 11651
Date: 2009-04-29 11:19:32 +0200
From: @grobian
There is not much that we can do here, IMO.
## Comment 11652
Date: 2009-05-27 15:56:19 +0200
From: @grobian
soon we can ditch swig so we no longer need to compile against Python itself, so wontfix.
## Comment 11653
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2783413 at http://sourceforge.net/support/tracker.php?aid=2783413
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 fails to compile with Python on SunOS | https://api.github.com/repos/MonetDB/MonetDB/issues/2064/comments | 0 | 2020-11-30T10:19:32Z | 2024-06-28T07:25:26Z | https://github.com/MonetDB/MonetDB/issues/2064 | 753,347,848 | 2,064 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-29 05:13:16 +0200
From: @drstmane
To: @njnes
Version: -- development
Last updated: 2009-06-23 11:48:16 +0200
## Comment 11645
Date: 2009-04-29 05:13:16 +0200
From: @drstmane
With the CVS HEAD, prefixing a query with PLAN does not longer yields any output, neither on the server console nor on the clients.
## Comment 11646
Date: 2009-05-06 18:15:47 +0200
From: @sjoerdmullender
It does produce output if yoy use -fraw (\fraw).
All lines of output are prepended with so seen as comment and not displayed in the default formatting mode.
## Comment 11647
Date: 2009-06-23 11:48:15 +0200
From: @drstmane
In deed, PLAN does still work, but does produces its output as plain text comments as opposed to in table format.
Closing as "Invalid".
## Comment 11648
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2783362 at http://sourceforge.net/support/tracker.php?aid=2783362
| SQL: PLAN does not work anymore | https://api.github.com/repos/MonetDB/MonetDB/issues/2063/comments | 0 | 2020-11-30T10:19:29Z | 2024-06-28T07:25:26Z | https://github.com/MonetDB/MonetDB/issues/2063 | 753,347,816 | 2,063 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-29 12:33:03 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-13 07:58:06 +0200
## Comment 11633
Date: 2009-04-29 00:33:03 +0200
From: @skinkie
CREATE TABLE "sys"."way_nds" (
"way" int,
"idx" int,
"to_node" int
);
create table segments (way integer, node1 integer, node2 integer);
insert into segments select t1.way, t1.to_node, t2.to_node from way_nds as t1, way_nds as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
way_nds consists of 370896230 rows
The error on the server:
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
!ERROR: bunfastins: bat too large
Segmentation fault
(will try to run GDB, but currently have enabled optimize)
I am using 64bit/oid32.
## Comment 11634
Date: 2009-04-29 05:09:53 +0200
From: @drstmane
"bat too large" occurs only if there are BUN_MAX BUNs; with 32-bit OIDs, BUN_MAX is INT_MAX-1, i.e., 2^31-1-1 == 2147483646 >> 370896230.
I suspect that an intermediate result while calculating the (self-)join "explodes".
What is the primary key of table way_nds? (way), (idx), (to_node), (way,idx), ..., (way,idx,to_node)?
## Comment 11635
Date: 2009-04-29 08:10:12 +0200
From: @skinkie
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe2aa3950 (LWP 7736)]
0x00007fffe544a9c9 in ALGjoinPath ()
from /export/scratch1/konink/monetdb-head/lib/MonetDB5/lib/lib_optimizer.so
(gdb) bt
0 0x00007fffe544a9c9 in ALGjoinPath ()
from /export/scratch1/konink/monetdb-head/lib/MonetDB5/lib/lib_optimizer.so
1 0x00007ffff7d12975 in DFLOWstep ()
from /export/scratch1/konink/monetdb-head/lib/libmonetdb5.so.5
2 0x00007ffff7d14894 in runDFLOWworker ()
from /export/scratch1/konink/monetdb-head/lib/libmonetdb5.so.5
3 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
4 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
[I'll recompile with debugging enabled again]
Currently no primary key has been set. But if I set it, it would be (way, idx). But since my query makes an explicit relation between way and idx, would a primary key make any difference?
## Comment 11636
Date: 2009-04-29 08:46:10 +0200
From: @drstmane
My question about the primary key was not about to add one, but rather about which attribute (or combination of attributes) has unique values / value combinations (and hence would qualify as a primary key) --- this information would help to (roughly) estimate the join result size ...
... apart from that, ALGjoinPath() should of course not segfault, even if (a previous) inter mediate result "overflows", and hence triggers an exception/error ...
## Comment 11637
Date: 2009-04-29 09:45:30 +0200
From: @mlkersten
The sporadic segfault has been catched in the HEAD
## Comment 11638
Date: 2009-04-30 19:50:56 +0200
From: @drstmane
With the latest (April 30) CVS code base (Feb2009 branch or HEAD):
- does the "bat too large" error still occur?
- does the segfault still occur?
## Comment 11639
Date: 2009-04-30 20:06:52 +0200
From: @drstmane
With today's CVS code base (Feb2009 branch) plus the attached mkey.mx patch, I get the following on 64-bit Fedora 10, using 32-bit OIDs, configured with --enable-strict --disable-debug --enable-optimize --disable-assert --enable-oid32, compiled with gcc 4.3.2, server started with default `mserver5 --dbinit='include sql;'`:
sql>CREATE TABLE "sys"."way_nds" ( "way" int, "idx" int, "to_node" int );
0 tuples
sql>copy 370896230 records into way_nds from '/export/data1/konink/way_nds.csv' delimiters ',';
Rows affected 370896230
sql>select count(*) from way_nds;
+-----------+
| L1 |
+===========+
| 370896230 |
+-----------+
1 tuple
sql>select * from way_nds limit 9;
+-----+-----+-----------+
| way | idx | to_node |
+=====+=====+===========+
| 35 | 0 | 200542 |
| 35 | 1 | 274057218 |
| 35 | 2 | 200550 |
| 35 | 3 | 200551 |
| 35 | 4 | 200553 |
| 37 | 0 | 200511 |
| 37 | 1 | 177231081 |
| 37 | 2 | 200513 |
| 37 | 3 | 177081428 |
+-----+-----+-----------+
9 tuples
sql>select count(*) from way_nds as t1, way_nds as t2 where t1.way = t2.way and t1.idx = t2.idx;
+-----------+
| L2 |
+===========+
| 370896230 |
+-----------+
1 tuple
sql>select count(*) from way_nds as t1, way_nds as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
+----+
| L3 |
+====+
| 0 |
+----+
1 tuple
sql>select min(idx) from way_nds;
+----+
| L6 |
+====+
| 0 |
+----+
1 tuple
sql>select max(idx) from way_nds;
+-------+
| L4 |
+=======+
| 36168 |
+-------+
1 tuple
sql>select count(*) from way_nds as t1, way_nds as t2 where t2.idx > 0 and t1.way = t2.way and t1.idx = t2.idx-1;
+-----------+
| L5 |
+===========+
| 343983657 |
+-----------+
1 tuple
... I suspect that there are (still?) (despite or due to my patch??) some problems with the multi-column join, possibly releated to or caused by potential bugs in bulk_rotate_xor_hash() of module mkey, in particular when hashing negaitve numbers and using a 32-bit left shift as done by the SQL code generation ...
## Comment 11640
Date: 2009-04-30 22:11:56 +0200
From: @drstmane
Without my patch,
select count(*) from way_nds as t1, way_nds as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
seems to trigger a segfault.
## Comment 11641
Date: 2009-04-30 22:23:09 +0200
From: @drstmane
avoiding the multi-column join (with arithmetic term) seems to work fine:
sql>select min(idx), max(idx), min(way), max(way) from way_nds;
+-----+-------+-----+----------+
| L11 | L12 | L13 | L14 |
+=====+=======+=====+==========+
| 0 | 36168 | 35 | 33244337 |
+-----+-------+-----+----------+
1 tuple
sql>select count(*) from way_nds as t1, way_nds as t2 where ((t1.way * 100000) + t1.idx) = ((t2.way * 100000) + t2.idx);
+-----------+
| L7 |
+===========+
| 370896230 |
+-----------+
1 tuple
sql>select count(*) from way_nds as t1, way_nds as t2 where ((t1.way * 100000) + t1.idx) = ((t2.way * 100000) + (t2.idx-1));
+-----------+
| L10 |
+===========+
| 343983657 |
+-----------+
1 tuple
## Comment 11642
Date: 2009-04-30 23:08:27 +0200
From: @drstmane
A simplified test reveals (still same setup as before), both with and without my mkey patch:
sql>CREATE TABLE "sys"."way_nds_9" ( "way" int, "idx" int, "to_node" int );
0 tuples
sql>insert into way_nds_9 select * from way_nds limit 9;
Rows affected 9
sql>select * from way_nds_9;
+-----+-----+-----------+
| way | idx | to_node |
+=====+=====+===========+
| 35 | 0 | 200542 |
| 35 | 1 | 274057218 |
| 35 | 2 | 200550 |
| 35 | 3 | 200551 |
| 35 | 4 | 200553 |
| 37 | 0 | 200511 |
| 37 | 1 | 177231081 |
| 37 | 2 | 200513 |
| 37 | 3 | 177081428 |
+-----+-----+-----------+
9 tuples
sql>select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx;
+-----+-----+-----------+-----+-----+-----------+
| way | idx | to_node | way | idx | to_node |
+=====+=====+===========+=====+=====+===========+
| 35 | 0 | 200542 | 35 | 0 | 200542 |
| 35 | 1 | 274057218 | 35 | 1 | 274057218 |
| 35 | 2 | 200550 | 35 | 2 | 200550 |
| 35 | 3 | 200551 | 35 | 3 | 200551 |
| 35 | 4 | 200553 | 35 | 4 | 200553 |
| 37 | 0 | 200511 | 37 | 0 | 200511 |
| 37 | 1 | 177231081 | 37 | 1 | 177231081 |
| 37 | 2 | 200513 | 37 | 2 | 200513 |
| 37 | 3 | 177081428 | 37 | 3 | 177081428 |
+-----+-----+-----------+-----+-----+-----------+
9 tuples
sql>select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t1.idx = t2.idx-1;
0 tuples
sql>select * from way_nds_9 as t1, way_nds_9 as t2 where t1.way = t2.way and t2.idx-1 = t1.idx;
0 tuples
sql>select * from way_nds_9 as t1, way_nds_9 as t2 where t1.idx = t2.idx-1 and t1.way = t2.way;
+-----+-----+-----------+-----+-----+-----------+
| way | idx | to_node | way | idx | to_node |
+=====+=====+===========+=====+=====+===========+
| 35 | 0 | 200542 | 35 | 1 | 274057218 |
| 35 | 1 | 274057218 | 35 | 2 | 200550 |
| 35 | 2 | 200550 | 35 | 3 | 200551 |
| 35 | 3 | 200551 | 35 | 4 | 200553 |
| 37 | 0 | 200511 | 37 | 1 | 177231081 |
| 37 | 1 | 177231081 | 37 | 2 | 200513 |
| 37 | 2 | 200513 | 37 | 3 | 177081428 |
+-----+-----+-----------+-----+-----+-----------+
7 tuples
sql>select * from way_nds_9 as t1, way_nds_9 as t2 where t2.idx-1 = t1.idx and t1.way = t2.way;
+-----+-----+-----------+-----+-----+-----------+
| way | idx | to_node | way | idx | to_node |
+=====+=====+===========+=====+=====+===========+
| 35 | 0 | 200542 | 35 | 1 | 274057218 |
| 35 | 1 | 274057218 | 35 | 2 | 200550 |
| 35 | 2 | 200550 | 35 | 3 | 200551 |
| 35 | 3 | 200551 | 35 | 4 | 200553 |
| 37 | 0 | 200511 | 37 | 1 | 177231081 |
| 37 | 1 | 177231081 | 37 | 2 | 200513 |
| 37 | 2 | 200513 | 37 | 3 | 177081428 |
+-----+-----+-----------+-----+-----+-----------+
7 tuples
Hence, there seems to be a bug in the generated plan and/or MAL code for multi-column joins in case the second term of the conjunctive where clause contains an (arithmetic) expression (as opposed to just column references) ...
... detailed analysis of generated plan and MAL code pending ...
## Comment 11643
Date: 2009-05-13 19:58:06 +0200
From: @drstmane
fixed in CVS by
===================================================================
2009/04/29 - stmane: MonetDB5/src/modules/mal/mkey.mx,1.8.2.1
do not try to dereference a pointer to a 32-bit int or flt
as (potentially) 64-bit wrd ---
--- you might not get what you expect ...
===================================================================
2009/04/29 - stmane: MonetDB5/src/modules/mal/mkey.mx,1.8.2.2
since hash value shave been wrd for more than half a year, now,
let's also use type wrd for the hash mask
===================================================================
2009/05/13 - stmane: MonetDB5/src/modules/mal/mkey.mx,1.8.2.3
make sure we use a "reasonable" 64-bit mask when left-shifting 1 by >= 32 bit
(on 64-bit systems)
===================================================================
2009/05/13 - stmane: MonetDB5/src/modules/mal/mkey.mx,1.8.2.4
make sure that bulk_rotate_xor_hash() is side-effect free, i.e.,
produces a new result BAT instead of modifying its first input in place
===================================================================
test added in sql/src/test/BugTracker-2009/Tests/multi-column_join_with_expression.SF-2783279.*
## Comment 11644
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2783279 at http://sourceforge.net/support/tracker.php?aid=2783279
| multi-column join with expression fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2062/comments | 0 | 2020-11-30T10:19:25Z | 2024-06-27T11:39:29Z | https://github.com/MonetDB/MonetDB/issues/2062 | 753,347,769 | 2,062 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-28 01:33:26 +0200
From: @drstmane
To: Gabriele Modena <<gabriele_modena>>
Version: -- development
Last updated: 2009-05-06 01:46:10 +0200
## Comment 11629
Date: 2009-04-28 01:33:26 +0200
From: @drstmane
For clients, ./bootstrap fails with
[...]
/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/clients/src/ruby
Traceback (most recent call last):
File "/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/buildtools/.GNU.32.32.d.1-Fedora10/bin/autogen.py", line 164, in <module>
(InstallList, DocList, OutList) = main(topdir, topdir, automake, [])
File "/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/buildtools/.GNU.32.32.d.1-Fedora10/bin/autogen.py", line 147, in main
main(d, topdir, automake, incdirsmap, conditional + cond)
File "/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/buildtools/.GNU.32.32.d.1-Fedora10/bin/autogen.py", line 147, in main
main(d, topdir, automake, incdirsmap, conditional + cond)
File "/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/buildtools/.GNU.32.32.d.1-Fedora10/bin/autogen.py", line 132, in main
read_makefile(p, cwd)
File "/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/buildtools/.GNU.32.32.d.1-Fedora10/bin/autogen.py", line 93, in read_makefile
for line in fileinput.input(os.path.join(cwd, 'Makefile.ag')):
File "/usr/lib64/python2.5/fileinput.py", line 253, in next
line = self.readline()
File "/usr/lib64/python2.5/fileinput.py", line 345, in readline
self._file = open(self._filename, self._mode)
IOError: [Errno 2] No such file or directory: '/export/scratch0/manegold/manegold.GNU.32.32.d.1.426/clients/src/ruby/Makefile.ag'
It seems that of the new ruby interface, only one file (clients/src/ruby/README) has been checked in so far ...
## Comment 11630
Date: 2009-05-06 13:38:11 +0200
From: @grobian
appears to be fix0rzed?
## Comment 11631
Date: 2009-05-06 13:46:10 +0200
From: @drstmane
Thanks for the reminder.
Yes this has been fixed by Gabriele by removing ruby (which doesn't require any compilation any more) from clients/src/Makefile.ag .
## Comment 11632
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2782529 at http://sourceforge.net/support/tracker.php?aid=2782529
| clients: ./bootstrap fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2061/comments | 0 | 2020-11-30T10:19:22Z | 2024-06-27T11:39:28Z | https://github.com/MonetDB/MonetDB/issues/2061 | 753,347,731 | 2,061 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-27 05:05:19 +0200
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2009-06-11 07:06:32 +0200
## Comment 11625
Date: 2009-04-27 17:05:19 +0200
From: @swingbit
When properly using a user and a schema, rather than 'monetdb' user and the 'sys' schema,
the dump and restore functionality becomes unusable.
In principle, a user should be able to dump and restore all the data he's allowed to manage, but this isn't possible at the moment.
assume you have an empty database 'test' running
executes mclient as admin
$ MCLIENT_SQL_ROOT="mclient -lsql -dtest"
executes mclient as user 'lhm
$ MCLIENT_SQL_LHM="mclient -lsql -dtest -ulhm -Plhm"
as admin, create a user 'lhm', and a schema 'lhm' (default for the user)
$ echo "CREATE USER \"lhm\" WITH PASSWORD 'lhm' NAME 'LHM user' SCHEMA \"sys\";" | $MCLIENT_SQL_ROOT
$ echo "CREATE SCHEMA \"lhm\" AUTHORIZATION \"lhm\";" | $MCLIENT_SQL_ROOT
$ echo "ALTER USER \"lhm\" SET SCHEMA \"lhm\";" | $MCLIENT_SQL_ROOT
here the user may create and populate tables..
dump the database as admin
Restoring this dump, the admin can recreate the original database, user, and schema
$ $MCLIENT_SQL_ROOT --dump
START TRANSACTION;
CREATE USER "lhm" WITH PASSWORD '<cannot be dumped>' NAME 'LHM user' SCHEMA "sys";
CREATE SCHEMA "lhm" AUTHORIZATION "lhm";
ALTER USER "lhm" SET SCHEMA "lhm";
COMMIT;
dump the database as user 'lhm'
Restoring this dump fails
Problem n. 1: incomplete dump. The user was apparently not allowed to dump all the necessary information
Problem n. 2: the user would not be allowed to recreate the schema 'lhm' anyway
$ $MCLIENT_SQL_LHM --dump
START TRANSACTION;
CREATE SCHEMA lhm;
SET SCHEMA lhm;
COMMIT;
## Comment 11626
Date: 2009-05-13 22:48:28 +0200
From: @njnes
the output of the dump is different. I guess this is related to the dump library, ie reassigning to sjoerd.
## Comment 11627
Date: 2009-06-11 19:06:32 +0200
From: @sjoerdmullender
When you replay the scenario given in the bug report, you now get as output to the last dump:
START TRANSACTION;
SET SCHEMA "lhm";
COMMIT;
This dump *can** be executed by the user (if the user was already created etc.).
This issue is covered by test sql/src/test/UserDump create.
(Also, the admin dump now dumps the password in such a way that it can be restored without in any way revealing the password.)
Closing as fixed.
## Comment 11628
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2782202 at http://sourceforge.net/support/tracker.php?aid=2782202
| SQL: dump&restore fully usable only by admin | https://api.github.com/repos/MonetDB/MonetDB/issues/2060/comments | 0 | 2020-11-30T10:19:19Z | 2024-06-27T11:39:27Z | https://github.com/MonetDB/MonetDB/issues/2060 | 753,347,682 | 2,060 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-24 02:11:08 +0200
From: @swingbit
To: @njnes
Version: -- development
Duplicates: #2058
Last updated: 2010-07-01 16:16:48 +0200
## Comment 11622
Date: 2009-04-24 14:11:08 +0200
From: @swingbit
In my database I have a table named "tf" (very common in IR..)
When I try to dump the database, one of the queries uses "tf" as a name for a temporary relation, and this clashes with mine.
Probably a safer name should be used there..
sql>\D
MAPI = lhm@localhost:50151
QUERY = WITH "tf" AS (SELECT "s"."name" AS "sname", "f"."name" AS "name", "f"."id" AS "id", "f"."func" AS "func" FROM "sys"."schemas" "s", "sys"."functions" "f" WHERE "f"."sql" = TRUE AND "s"."id" = "f"."schema_id" UNION SELECT "s"."name" AS "sname", "t"."name" AS "name", "t"."id" AS "id", CAST(NULL AS VARCHAR(8196)) AS "func" FROM "sys"."schemas" "s", "sys"."_tables" "t" WHERE "t"."type" BETWEEN 0 AND 1 AND "t"."system" = FALSE AND "s"."id" = "t"."schema_id" UNION SELECT "s"."name" AS "sname", "tr"."name" AS "name", "tr"."id" AS "id", "tr"."statement" AS "func" FROM "sys"."triggers" "tr", "sys"."schemas" "s", "sys"."_tables" "t" WHERE "s"."id" = "t"."schema_id" AND "t"."id" = "tr"."table_id") SELECT * FROM "tf" ORDER BY "tf"."id"
## Comment 11623
Date: 2009-04-24 14:14:02 +0200
From: @swingbit
Sorry, a "back" in my browser re-submitted http://sourceforge.net/support/tracker.php?aid=2780395
Deleting this duplicate bug report
## Comment 11624
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2780409 at http://sourceforge.net/support/tracker.php?aid=2780409
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14166
Date: 2010-07-01 16:16:48 +0200
From: @njnes
*** This bug has been marked as a duplicate of bug #2058 ***
| SQL: query for dump uses a (too) common table name | https://api.github.com/repos/MonetDB/MonetDB/issues/2059/comments | 0 | 2020-11-30T10:19:15Z | 2024-06-28T07:25:25Z | https://github.com/MonetDB/MonetDB/issues/2059 | 753,347,640 | 2,059 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-24 01:52:47 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: 11.3.3 (Apr2011-SP1) [obsolete]
Last updated: 2011-07-29 10:52:46 +0200
## Comment 11615
Date: 2009-04-24 13:52:47 +0200
From: @swingbit
In my database I have a table named "tf" (very common in IR..)
When I try to dump the database, one of the queries uses "tf" as a name for a temporary relation, and this clashes with mine.
Probably a safer name should be used there..
sql>\D
MAPI = lhm@localhost:50151
QUERY = WITH "tf" AS (SELECT "s"."name" AS "sname", "f"."name" AS "name", "f"."id" AS "id", "f"."func" AS "func" FROM "sys"."schemas" "s", "sys"."functions" "f" WHERE "f"."sql" = TRUE AND "s"."id" = "f"."schema_id" UNION SELECT "s"."name" AS "sname", "t"."name" AS "name", "t"."id" AS "id", CAST(NULL AS VARCHAR(8196)) AS "func" FROM "sys"."schemas" "s", "sys"."_tables" "t" WHERE "t"."type" BETWEEN 0 AND 1 AND "t"."system" = FALSE AND "s"."id" = "t"."schema_id" UNION SELECT "s"."name" AS "sname", "tr"."name" AS "name", "tr"."id" AS "id", "tr"."statement" AS "func" FROM "sys"."triggers" "tr", "sys"."schemas" "s", "sys"."_tables" "t" WHERE "s"."id" = "t"."schema_id" AND "t"."id" = "tr"."table_id") SELECT * FROM "tf" ORDER BY "tf"."id"
## Comment 11616
Date: 2009-04-24 16:03:18 +0200
From: @sjoerdmullender
Looks like a scoping problem.
This is very similar to having a function with a parameter name which happens to be the same as the name of a column of one of the tables that is used in the function. There too you get a complaint about ambiguous names.
I have solved the problem in dump for now by using a less likely name, but I think the scoping problem should be looked at before we close this bug.
## Comment 11617
Date: 2009-04-25 19:19:54 +0200
From: @drstmane
Fixed by Sjoerd in MonetDB-clients as of Feb2009-SP2 release (candidate).
Test added in sql/src/test/BugTracker-2009/Tests/name_clash_with_dump.SF-2780395.sql
## Comment 11618
Date: 2009-04-25 20:43:33 +0200
From: @sjoerdmullender
Reopened. I didn't "fix" the bug, I worked around it. First I want a pronouncement on the scoping issue, both in the with statement and in functions.
## Comment 11619
Date: 2009-08-06 17:14:06 +0200
From: @sjoerdmullender
Niels, can you pronounce?
## Comment 11620
Date: 2009-08-06 23:23:01 +0200
From: @njnes
indeed there is a bug in the scoping of functions and with.
## Comment 11621
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2780395 at http://sourceforge.net/support/tracker.php?aid=2780395
## Comment 14167
Date: 2010-07-01 16:16:48 +0200
From: @njnes
*** Bug #2059 has been marked as a duplicate of this bug. ***
## Comment 15690
Date: 2011-03-28 17:36:34 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15947
Date: 2011-07-15 16:55:26 +0200
From: @sjoerdmullender
A lot has changed since this bug was originally opened, but it's still not right. Now we have:
sql>create table foo (i int);
operation successful
sql>with foo as (select * from tables) select * from foo;
+---+
| i |
+===+
+---+
0 tuples (1.529ms)
I would expect the select to return the contents of tables, not foo.
## Comment 15948
Date: 2011-07-16 11:59:35 +0200
From: @njnes
Changeset [b86b9b374542](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=b86b9b374542) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b86b9b374542](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=b86b9b374542)
Changeset description:
look in the 'with' scope before table scope (solves bug #2058).
## Comment 15949
Date: 2011-07-17 10:16:58 +0200
From: @njnes
Changeset [dc2fa5f7d754](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=dc2fa5f7d754) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=dc2fa5f7d754](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=dc2fa5f7d754)
Changeset description:
look in the 'with' scope before table scope (solves bug #2058).
(transplanted from b86b9b374542300acf62fadc46465cdcb266b8be)
## Comment 15950
Date: 2011-07-17 10:43:54 +0200
From: @sjoerdmullender
Changeset [36e9bbbf02ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=36e9bbbf02ba) 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=36e9bbbf02ba](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=36e9bbbf02ba)
Changeset description:
Added test for bug #2058.
## Comment 15951
Date: 2011-07-17 10:45:21 +0200
From: @sjoerdmullender
Seems to be fixed.
## Comment 16011
Date: 2011-07-29 10:52:46 +0200
From: @sjoerdmullender
The Apr2011-SP2 bugfix release is out.
| scoping issue of functions and with | https://api.github.com/repos/MonetDB/MonetDB/issues/2058/comments | 0 | 2020-11-30T10:19:12Z | 2024-06-27T11:39:25Z | https://github.com/MonetDB/MonetDB/issues/2058 | 753,347,613 | 2,058 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-24 03:08:29 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-28 10:24:01 +0200
## Comment 11610
Date: 2009-04-24 03:08:29 +0200
From: @skinkie
Running the following combination of queries:
CREATE TABLE node_tags (node integer, k varchar(255), v varchar(1024));
COPY 825352907 RECORDS INTO node_tags from '/export/data1/konink/node_tags.csv' USING DELIMITERS ',', '\n', '''';
at the same time {
select * from node_tags where k = 'name' and lower(v) = lower('London');
PLAN select * from node_tags where k = 'name' and lower(v) = lower('London');
}
I manage to get the server into a segmentation fault, using the release candidate, hence no debugging symbols.
[Switching to Thread 0x7fffe3068950 (LWP 3816)]
0x00007ffff76ced54 in GDKqsort_void_direct_int () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
(gdb) bt
0 0x00007ffff76ced54 in GDKqsort_void_direct_int () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
1 0x00007ffff76fe166 in GDKqsort () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
2 0x00007ffff7631f58 in BBPtrim () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
3 0x00007ffff7696f00 in GDKmemchk () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
4 0x00007ffff7698785 in GDKmallocmax () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
5 0x00007ffff769894f in GDKmalloc () from /export/scratch1/konink/monetdb-rc/lib/libbat.so.1
6 0x00007fffe99daa74 in strLower () from /export/scratch1/konink/monetdb-rc/lib/MonetDB5/lib/lib_str.so
7 0x00007fffe85d2d2c in STRbatLower () from /export/scratch1/konink/monetdb-rc/lib/MonetDB5/lib/lib_batstr.so
8 0x00007ffff7d1f0f2 in DFLOWstep () from /export/scratch1/konink/monetdb-rc/lib/libmonetdb5.so.5
9 0x00007ffff7d20180 in runDFLOWworker () from /export/scratch1/konink/monetdb-rc/lib/libmonetdb5.so.5
10 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
11 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
## Comment 11611
Date: 2009-04-25 18:27:40 +0200
From: @drstmane
FYI: just like all MonetDB CVS sources and tarballs, also the release candidate (either tarball or CVS tag) can be configured with --enable-debug to get debugging sysmbols.
## Comment 11612
Date: 2009-05-13 21:36:27 +0200
From: @skinkie
(works on current)
## Comment 11613
Date: 2009-05-28 22:24:01 +0200
From: @njnes
failed to repeat the problem.
## Comment 11614
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2780039 at http://sourceforge.net/support/tracker.php?aid=2780039
| SIGSEGV upon PLAN | https://api.github.com/repos/MonetDB/MonetDB/issues/2057/comments | 0 | 2020-11-30T10:19:09Z | 2024-06-28T07:25:25Z | https://github.com/MonetDB/MonetDB/issues/2057 | 753,347,582 | 2,057 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-23 07:09:53 +0200
From: @swingbit
To: SQL devs <<bugs-sql>>
Version: -- development
CC: @njnes
Last updated: 2010-12-20 09:14:34 +0100
## Comment 11600
Date: 2009-04-23 19:09:53 +0200
From: @swingbit
I'm loading a table from disk. The data seems OK until I shut down the db.
If I do that, then the data is corrupted.
It shouldn't be related to the bug about parallel bulk load, because I'm using gdk_threads=1
create a clean database
$ monetdb create test
successfully created database 'test'
$ monetdb start test
starting database 'test'... done
Load a table from file 'ne_doc' (140377 tuples)
This table is too large to be an attachment to this bug report.
It can be found here: /ufs/roberto/ne_doc
$ echo "CREATE TABLE ne_doc (neID int, predicate VARCHAR(30), docID int);" | mclient -lsql -d test
$ echo "COPY 140377 RECORDS INTO ne_doc FROM '/ufs/roberto/ne_doc';" | mclient -lsql -d test
[ 140377 ]
Ask for the unique 'predicates'
$ echo "select predicate from ne_doc group by predicate;" | mclient -lsql -d test
% sys.ne_doc table_name
% predicate name
% varchar type
% 21 length
[ "ep-contracting-states" ]
[ "inventor_of" ]
[ "assignee_of" ]
Stop and start the database
$ monetdb stop test
stopping database 'test'... done
$ monetdb start test
starting database 'test'... done
Ask for the unique 'predicates'
$ echo "select predicate from ne_doc group by predicate;" | mclient -lsql -d test
% sys.ne_doc table_name
% predicate name
% varchar type
% 21 length
[ "ep-contracting-states" ]
[ "inventor_of" ]
[ "" ]
It seems corrupted after the sutdown
## Comment 11601
Date: 2009-04-26 10:38:06 +0200
From: @drstmane
Just to be sure:
I suppose you are using
--set gdk_nr_threads=1
^^^^
not
--set gdk_threads=1
^
right?
## Comment 11602
Date: 2009-04-27 10:56:39 +0200
From: @swingbit
Indeed, I do use the correct keyword,in monetdb5.conf:
gdk_nr_threads=1
## Comment 11603
Date: 2009-04-27 11:21:51 +0200
From: @drstmane
On my 64-bit Fedora 10 desktop, I cannot reproduce the problem, neither with the Feb2009 SP2 code base, nor with this mornings CVS HEAD code base ...
What I see, though, with the Feb2009 SP2 code base, when starting `mserver5 --dbinit='include sql;'` by hand and then bulk-loading the data with `COPY INTO ...` is the following error on the mserver5 console:
>!ERROR: GDKsave: failed name=10/1073, ext=tail, mode 0
I don't see this when loading single threaded nor with the CVS HEAD code base.
## Comment 11604
Date: 2009-04-27 19:02:51 +0200
From: @drstmane
Strangely, after having lunch and after cleaning (revoming) all legacy databases and while Roberto was watching, I could (and still can) reproduce the problem with the Feb2009-SP2 code base (didn't try any other, yet)
In fact, when loading the data multi-threaded (default on multi-CPU/-core machines), it works fine, and I get the following both directly after loading as well as after restarting the server:
$ echo "select predicate, count(*) from ne_doc group by predicate;" | mclient -lsql -d test
% sys.ne_doc, sys.ne_doc table_name
% predicate, L1 name
% varchar, wrd type
% 21, 5 length
[ "ep-contracting-states", 67386 ]
[ "inventor_of", 51596 ]
[ "assignee_of", 21395 ]
However, when loading the data single-threaded(!) (gdk_nr_threads=1), I get the above only in the very mserver5 that loaded the data; after restarting the server, I get:
$ echo "select predicate, count(*) from ne_doc group by predicate;" | mclient -lsql -d test
% sys.ne_doc, sys.ne_doc table_name
% predicate, L1 name
% varchar, wrd type
% 21, 5 length
[ "ep-contracting-states", 67386 ]
[ "inventor_of", 51596 ]
[ "", 21395 ]
... very strange --- further analysis pending ...
## Comment 11605
Date: 2009-06-05 17:00:39 +0200
From: @drstmane
I just tried this with the May2009 release, and it appears to work fine now, both using 4 threads on my quad core desktop as well as using only one thread (ghk_nr_threads=1) --- note, though, that parallel bulk loading has been disabled recently as the code appeared to be incorrect for many cases ---.
Roberto,
could I use your data to add a test to CVS?
Or is that data not meant to be public?
Stefan
## Comment 11606
Date: 2009-08-06 16:33:34 +0200
From: @mlkersten
no additional information to disagree with the implicit solution provided.
## Comment 11607
Date: 2009-08-11 11:54:40 +0200
From: @drstmane
Roberto,
could I use your data to add a test to CVS?
Or is that data not meant to be public?
## Comment 11608
Date: 2010-03-17 19:56:35 +0100
From: @mlkersten
Can this bug report be closed?
## Comment 11609
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2779702 at http://sourceforge.net/support/tracker.php?aid=2779702
## Comment 15288
Date: 2010-12-05 14:12:54 +0100
From: @njnes
fixed some time ago. Many copy into (parallel loading) tests exists
| SQL COPY INTO, data corrupted after shutdown | https://api.github.com/repos/MonetDB/MonetDB/issues/2056/comments | 0 | 2020-11-30T10:19:04Z | 2024-06-27T11:39:23Z | https://github.com/MonetDB/MonetDB/issues/2056 | 753,347,519 | 2,056 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-23 02:30:32 +0200
From: Wouter Alink <<alink>>
To: SQL devs <<bugs-sql>>
Version: -- development
Last updated: 2010-08-31 13:58:55 +0200
## Comment 11592
Date: 2009-04-23 14:30:32 +0200
From: Wouter Alink <<alink>>
Using todays CVS head.
The following sql statements give wrong results (both SELECT yield 1 row with number '10'). Note that without setting the optimizers, it works fine.
start transaction;
set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,deadcode,constants,commonTerms,reorder,joinPath,deadcode,recycle,reduce,garbageCollector,dataflow,history,multiplex';
CREATE TABLE y (x int);
INSERT INTO y VALUES (10);
SELECT * FROM y;
rollback;
start transaction;
CREATE TABLE y (x int);
INSERT INTO y VALUES (13);
SELECT * FROM y;
rollback;
## Comment 11593
Date: 2009-04-23 14:47:03 +0200
From: Wouter Alink <<alink>>
the 'recycle' optimizer caused the problems.
This optimizer has been switched off a while ago apparently. I don't know whether it will be enabled again any time soon, but if so, i assume this bug should stay open. If not, this bug could be postponed or closed.
Martin/Milena, could you comment?
## Comment 11594
Date: 2009-04-23 14:57:40 +0200
From: @drstmane
re-assigned to Mrs. "recycler" --- Milena ;-)
## Comment 11595
Date: 2009-04-27 11:36:24 +0200
From: @drstmane
I can reproduce this one, both with the Feb2009-SP2 code base and with this mornings CVS HEAD:
It works by default, i.e., with the following optimizers activated:
Feb2009-SP2:
sql>select optimizer;
0 tuples
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| single_value |
+===============================================================================================================================================================================+
| inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,constants,commonTerms,joinPath,accumulators,deadcode,reduce,garbageCollector,dataflow,history,multiplex |
+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
CVS HEAD:
sql>select optimizer;
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| single_value |
+===================================================================================================================================================================================+
| inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex |
+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
but fails as reported when recycle is activated (between deadcode & reduce), i.e.,
Feb2009-SP2:
sql>set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,aliases,mergetable,constants,commonTerms,joinPath,accumulators,deadcode,recycle,reduce,garbageCollector,dataflow,history,multiplex';
CVS HEAD:
sql>set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,deadcode,constants,commonTerms,joinPath,deadcode,recycle,reduce,garbageCollector,dataflow,history,multiplex';
This looks as if recycle is too eager caching/recycling update operations (even) across transaction boundaries...
## Comment 11596
Date: 2009-08-11 00:15:30 +0200
From: Wouter Alink <<alink>>
added test as:
sql/src/test/BugTracker-2009/Tests/table-leftovers.SF-2779462.sql
with hand-crafted output (it still fails)
## Comment 11597
Date: 2009-11-07 16:59:35 +0100
From: @drstmane
The test still fails as reported on Darwin (MacOS X), Debia, 32-bit Fedora 10, SunOS (Solaris) & Windows:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Darwin9.8.0/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-Debian4.0/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-Fedora10/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-SunOS5.10/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.32.d.1-SunOS5.10/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-SunOS5.10/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-SunOS5.11/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.32.32.d.1-Windows5.1/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.32.d.1-Windows6.0/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Windows6.0/src_test_BugTracker-2009/table-leftovers.SF-2779462.out.00.html
On 64-bit Fedora 10, Fedora 11 & Gentoo, the test (now?) produced the expected results, but (also) triggers a "weird" or empty error message:
weird:
ERROR = !ERROR: Optimizer '`Ú–?' does not exist, use default pipe instead
empty:
ERROR = !
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.32.d.1-Fedora10/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.0-Fedora10/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.32.d.1-Fedora10/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora10/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-Fedora11/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Gentoo2.0.1/src_test_BugTracker-2009/table-leftovers.SF-2779462.err.00.html
## Comment 11598
Date: 2009-11-17 00:02:46 +0100
From: @drstmane
test has been disabled by
===================================================================
2009/11/09 - nielsnes: sql/src/test/BugTracker-2009/Tests/All,1.51.2.6
more python tests and some more time
===================================================================
## Comment 11599
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2779462 at http://sourceforge.net/support/tracker.php?aid=2779462
## Comment 14870
Date: 2010-08-31 13:58:55 +0200
From: @sjoerdmullender
The test is working, so I guess the bug has been fixed.
| SQL: table leftovers | https://api.github.com/repos/MonetDB/MonetDB/issues/2055/comments | 0 | 2020-11-30T10:19:01Z | 2024-06-27T11:39:22Z | https://github.com/MonetDB/MonetDB/issues/2055 | 753,347,480 | 2,055 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-23 02:10:04 +0200
From: Wouter Alink <<alink>>
To: @njnes
Version: -- development
Last updated: 2009-05-13 07:15:38 +0200
## Comment 11586
Date: 2009-04-23 14:10:04 +0200
From: Wouter Alink <<alink>>
It may be related to previous bug-reports. (using todays CVS head)
The following works fine (can be run many times):
start transaction;
CREATE TEMPORARY TABLE y (x int);
INSERT INTO y VALUES (13);
SELECT * FROM y;
DROP TABLE y;
rollback;
The following doesn't work multiple times (the only difference is that the drop table statement is omitted which shouldn't be necessary for temporary tables):
start transaction;
CREATE TEMPORARY TABLE y (x int);
INSERT INTO y VALUES (13);
SELECT * FROM y;
rollback;
## Comment 11587
Date: 2009-04-23 14:16:31 +0200
From: Wouter Alink <<alink>>
Additional info:
The following works fine:
start transaction;
CREATE TABLE y (x int);
INSERT INTO y VALUES (10);
SELECT * FROM y;
rollback;
SELECT * FROM y;
While the code below doesn't: (it still knows about y after the rollback)
start transaction;
CREATE TEMPORARY TABLE y (x int);
INSERT INTO y VALUES (10);
SELECT * FROM y;
rollback;
SELECT * FROM y;
## Comment 11588
Date: 2009-04-23 14:19:29 +0200
From: Wouter Alink <<alink>>
Additional info:
Running the following query multiple times in separate sessions fails:
CREATE TEMPORARY TABLE y (x int);
INSERT INTO y VALUES (10);
SELECT * FROM y;
The table is already known. There are however no records in table y. SELECT * FROM y; yields an empty table.
## Comment 11589
Date: 2009-04-25 19:34:53 +0200
From: @drstmane
See also
ID: 2734713 "Temporary table is semi-persistent when transaction fails"
https://sourceforge.net/tracker/?func=detail&aid=2734713&group_id=56967&atid=482468
## Comment 11590
Date: 2009-05-13 19:15:38 +0200
From: @njnes
Fixed bug. The temporary schema was handled differently in the reset (mvc) code. This is still the case but it first goes through the
normal code. Added a test for this bug in src/test/BugTracker-2009/temporary_table_leftover
## Comment 11591
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2779437 at http://sourceforge.net/support/tracker.php?aid=2779437
| SQL: Temporary table leftovers | https://api.github.com/repos/MonetDB/MonetDB/issues/2054/comments | 0 | 2020-11-30T10:18:57Z | 2024-06-27T11:39:21Z | https://github.com/MonetDB/MonetDB/issues/2054 | 753,347,421 | 2,054 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-22 06:03:40 +0200
From: @drstmane
To: Stratos Idreos <<idreos>>
Version: -- development
Last updated: 2009-04-26 05:09:07 +0200
## Comment 11583
Date: 2009-04-22 18:03:40 +0200
From: @drstmane
With the Microsoft Visual Studio compiler, the crackers code fails to compile on 64-bit Windows with 64-bit OIDs:
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'int', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
src\modules\mal\crackers\crackers_core_unordered.mx(677) : warning C4267: '=' : conversion from 'size_t' to 'date', possible loss of data
cf.
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.Mic.64.64.d.1-Windows5.2/make-k.out.html
## Comment 11584
Date: 2009-04-26 17:09:07 +0200
From: @drstmane
Fixed by Stratos.
Thanks!
## Comment 11585
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2778729 at http://sourceforge.net/support/tracker.php?aid=2778729
| M5: crackers fails to compile on Win64 with 64-bit OIDs | https://api.github.com/repos/MonetDB/MonetDB/issues/2053/comments | 0 | 2020-11-30T10:18:54Z | 2024-06-27T11:39:20Z | https://github.com/MonetDB/MonetDB/issues/2053 | 753,347,386 | 2,053 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-21 03:45:34 +0200
From: @swingbit
To: Roberto Cornacchia <<roberto.cornacchia>>
Version: -- development
Last updated: 2009-04-27 12:23:45 +0200
## Comment 11574
Date: 2009-04-21 15:45:34 +0200
From: @swingbit
MonetDB server v4.29.0 (64-bit), based on kernel v1.29.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/roberto/servers/MonetDB
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)
Compiled by: roberto@skadi.ins.cwi.nl
Compilation: gcc -O2 -Wall -Wextra -std=c99 -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -ftree-vectorize -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : ld -IPA -m elf_x86_64
/export/scratch0/roberto/lhm/alexandria_doclist.xml contains a list of nodes with xml file names. E.g.:
<docs>
<doc>/export/scratch0/roberto/lhm/alexandria/D/1991/EP-0409358-A1.xml</doc>,
<doc>/export/scratch0/roberto/lhm/alexandria/D/1991/EP-0412453-A1.xml</doc>
<doc>/export/scratch0/roberto/lhm/alexandria/D/1991/EP-0453965-A2.xml</doc>
<doc>/export/scratch0/roberto/lhm/alexandria/D/1991/EP-0423091-A2.xml</doc>
</docs>
This used to work (a week ago? I'm not very sure about this).
[roberto@skadi] ~/lhm_code/HyServer/console
$ echo 'for $i in subsequence(doc("/export/scratch0/roberto/lhm/alexandria_doclist.xml")//doc, 1, 50) return pf:add-doc($i,$i,"alexandria")' | mclient -p 50141 -lxq -d test
[roberto@skadi] ~/lhm_code/HyServer/console
$ echo 'for $i in subsequence(doc("/export/scratch0/roberto/lhm/alexandria_doclist.xml")//doc, 51, 50) return pf:add-doc($i,$i,"alexandria")' | mclient -p 50141 -lxq -d test
MAPI = monetdb@localhost:50141
QUERY = for $i in subsequence(doc("/export/scratch0/roberto/lhm/alexandria_doclist.xml")//doc, 51, 50) return pf:add-doc($i,$i,"alexandria")
ERROR = !ERROR: BATfetchjoin(tmpr_444,tmp_423) does not hit always (|bn|=0 != 50=|l|) => can't use fetchjoin.
!ERROR: CMDleftfetchjoin: operation failed.
!ERROR: interpret_params: shred_doc_base(param 4): evaluation error.
The subsequence call is NOT the proble, it works fine if I just return the $i variable.
## Comment 11575
Date: 2009-04-21 20:43:22 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi Roberto,
did you try todays' HEAD version? I changed some parts of the physical plan generation yesterday.
Jan
## Comment 11576
Date: 2009-04-24 00:29:31 +0200
From: @swingbit
Hi Jan,
I was indeed using the head version. I don't remember precisely if it was from the day before the bug report, but sure not more than a few days. It could have very well been the day before.
## Comment 11577
Date: 2009-04-24 08:30:20 +0200
From: Jan Rittinger <<jan.rittinger>>
And does the error still occur? -- If not please close the bug report.
Otherwise please point out where (in the file system) your data set is to reproduce the problem :)
## Comment 11578
Date: 2009-04-24 10:42:52 +0200
From: @swingbit
Yes, it still occurs (on the HEAD from yesterday, 23 Apr 2009)
Jan, please read my email (coming) about the data
## Comment 11579
Date: 2009-04-24 12:15:45 +0200
From: Jan Rittinger <<jan.rittinger>>
Fixed MIL code generation of the slice operator (to reset the resulting head oids).
Test can be achieved with a call to subsequence and any arbitrary document (content does not matter).
Roberto can you check (after propagation) if everything works as expected again...
## Comment 11580
Date: 2009-04-27 12:23:45 +0200
From: @swingbit
The problem reported seems indeed fixed.
I close this bug report.
## Comment 11581
Date: 2009-04-27 14:59:24 +0200
From: @drstmane
Would this (have) be(en) reproducile with a small(er) data set to add a test?
## Comment 11582
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2777473 at http://sourceforge.net/support/tracker.php?aid=2777473
| PF: incremental shredding broken | https://api.github.com/repos/MonetDB/MonetDB/issues/2052/comments | 0 | 2020-11-30T10:18:50Z | 2024-06-27T11:39:19Z | https://github.com/MonetDB/MonetDB/issues/2052 | 753,347,336 | 2,052 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-21 03:15:27 +0200
From: @drstmane
To: Gijs Molenaar <<gijs>>
Version: -- development
Last updated: 2009-07-09 11:09:22 +0200
## Comment 11568
Date: 2009-04-21 15:15:27 +0200
From: @drstmane
After yesterday's removal of the "old" python interface, the following tests fail.
If possible, these tests should be updated to use the new python interface.
MonetDB4/src/mapi/Tests/manyMapiClients.MIL.py:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/src_mapi/manyMapiClients.err.00.html
sql/src/test/BugTracker/Tests/python_escape.SF-1916844.SQL.py:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/python_escape.SF-1916844.err.00.html
sql/src/test/concurrent/Tests/crash_on_concurrent_use.SF-1411926.SQL.py:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/crash_on_concurrent_use.SF-1411926.err.00.html
sql/src/test/concurrent/Tests/simple_select.SQL.py:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/simple_select.err.00.html
sql/src/test/mapi/Tests/python_dbapi.SQL.sh,
sql/src/test/mapi/Tests/python_dbapi.SQL.bat:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_dbapi.out.00.html
## Comment 11569
Date: 2009-06-05 10:57:53 +0200
From: @drstmane
While most of the python test now work (mostly updated/fixed by Sjoerd); cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/src_mapi/manyMapiClients.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora10/src_mapi/manyMapiClients.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/crash_on_concurrent_use.SF-1411926.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/crash_on_concurrent_use.SF-1411926.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/simple_select.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/simple_select.err.00.html
Some still fail in the May2009 release; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/python_escape.SF-1916844.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_dbapi.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_dbapi_embedded.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_dbapi_embedded.err.00.html
including the new unit test(s) for the new native Python interface; cf.,
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
Could you please check, what the problem(s) is/are, and whether you could fix it/them?
Thanks!
## Comment 11570
Date: 2009-06-18 15:04:49 +0200
From: @gijzelaerr
I think all tests are working now.
## Comment 11571
Date: 2009-06-18 16:32:42 +0200
From: @drstmane
... well, unfortunately not quite ...
Two tests show different output than before:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/crash_on_concurrent_use.SF-1411926.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_concurrent/simple_select.out.00.html
In case this new output is correct and intended, it should be approved accordingly;
otherwise, the test and/or code should be checked an fixed to produce the correct output.
Two tests produce errors:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker/python_escape.SF-1916844.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_mapi/python_dbapi.err.00.html
## Comment 11572
Date: 2009-07-09 11:09:22 +0200
From: @gijzelaerr
Ok, this time everything should be working. If there all stiff differences between output the target output should be adjusted to the current.
## Comment 11573
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2777428 at http://sourceforge.net/support/tracker.php?aid=2777428
| Tests fail after removal of "old" python interface | https://api.github.com/repos/MonetDB/MonetDB/issues/2051/comments | 0 | 2020-11-30T10:18:47Z | 2024-06-28T07:25:24Z | https://github.com/MonetDB/MonetDB/issues/2051 | 753,347,295 | 2,051 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-21 01:54:11 +0200
From: @skinkie
To: @mlkersten
Version: -- development
Last updated: 2009-11-15 03:32:41 +0100
## Comment 11557
Date: 2009-04-21 01:54:11 +0200
From: @skinkie
sql>\d
+--------------+
| name |
+==============+
| args |
| auths |
| columns |
| db_user_info |
| functions |
| idxs |
| keycolumns |
| node_tags |
| nodes_legacy |
| privileges |
| relations |
| schemas |
| sequences |
| tables |
| triggers |
| types |
| user_role |
| users |
| way_nds |
| way_tags |
| ways |
+--------------+
21 tuples
sql>\d triggers
Table sys.triggers does not exist.
[Latest CVS]
When started a new database \d args works, while \d args hangs for me after type_scale.
sql>\d args
CREATE TABLE "sys"."args" (
"id" int,
"func_id" int,
"name" varchar(256),
"type" varchar(1024),
"type_digits" int,
"type_scale" int,
"number" int
);
sql>bash-3.2$ /export/scratch1/konink/monetdb-head/bin/mclient -H -lsql -p 50005
sql>\d args
CREATE TABLE "sys"."args" (
"id" int,
"func_id" int,
"name" varchar(256),
"type" varchar(1024),
"type_digits" int,
"type_scale" int,
Disabling reorder seems to fix the issue.
## Comment 11558
Date: 2009-04-21 12:34:36 +0200
From: @skinkie
With reorder off \d results in 'nothing'. For the affected database.
## Comment 11559
Date: 2009-04-22 16:48:19 +0200
From: @skinkie
Probably related:
sql>create table node_tags (id integer);
0 tuples
sql>select * from node_tags;
0 tuples
0 tuples
sql>insert into node_tags values (1);
0 tuples
Rows affected 1
sql>select * from node_tags;
0 tuples
+----+
| id |
+====+
| 1 |
+----+
1 tuple
## Comment 11560
Date: 2009-04-24 17:42:22 +0200
From: @skinkie
Traced back to the --performance flag.
## Comment 11561
Date: 2009-04-25 18:40:09 +0200
From: @drstmane
added test in sql/src/test/BugTracker-2009/Tests/Attic/dumping_tables.SF-2776908* in three variants:
1) mserver5 started withou further options (default)
(did and does work fine)
2) mserver5 started with --performance
(works fine with post Feb2009-SP2 CVS code base)
3) mserver5 srated with --optimizers
(still fails as reported)
(did not test any other mserver5 commandline options)
## Comment 11562
Date: 2009-07-20 20:24:09 +0200
From: @mlkersten
Given the fact that reorder seems to be the cause, this bug is related to 2770608
## Comment 11563
Date: 2009-08-13 19:32:21 +0200
From: @drstmane
re-opened as the respective test still fails; cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/dumping_tables.SF-2776908--optimizers.out.00.html
the reorder optimizer is no longer activated by default; hence, that cannot be the problem.
In case "\d" is not supposed to work with --optimizers given on the mserver5 command line, then we should document that, possibly add a notification and approve the expected output as "correct".
## Comment 11564
Date: 2009-11-15 15:32:40 +0100
From: @mlkersten
\d should not cause problems (anymore). It is firing an ordinary SQL query.
The test output has been checked (it seems), all green.
Closing without new test.
## Comment 11565
Date: 2009-11-15 15:49:32 +0100
From: @drstmane
for the records:
the test was failing until it was disabled (on the Nov2009 branch, only):
$ cvs log -Nr1.51.2.5 sql/src/test/BugTracker-2009/Tests/All
RCS file: /cvsroot/monetdb/sql/src/test/BugTracker-2009/Tests/All,v
Working file: sql/src/test/BugTracker-2009/Tests/All
head: 1.58
branch:
locks: strict
access list:
keyword substitution: kv
total revisions: 162; selected revisions: 1
description:
----------------------------
revision 1.51.2.5
date: 2009/11/09 22:22:38; author: nielsnes; state: Exp; lines: +2 -2
disable a few more test (no propagation)
=============================================================================
$ cvs diff -r1.51.2.{4,5} sql/src/test/BugTracker-2009/Tests/All
Index: sql/src/test/BugTracker-2009/Tests/All
===================================================================
RCS file: /cvsroot/monetdb/sql/src/test/BugTracker-2009/Tests/All,v
retrieving revision 1.51.2.4
retrieving revision 1.51.2.5
diff -u -r1.51.2.4 -r1.51.2.5
--- sql/src/test/BugTracker-2009/Tests/All 8 Nov 2009 20:11:51 -0000 1.51.2.4
+++ sql/src/test/BugTracker-2009/Tests/All 9 Nov 2009 22:22:38 -0000 1.51.2.5
@@ -58,9 +58,9 @@
missing_column_name.SF-2776100
dumping_tables.SF-2776908
dumping_tables.SF-2776908--performance
-dumping_tables.SF-2776908--optimizers
+dumping_tables.SF-2776908--optimizers
name_clash_with_dump.SF-2780395
-temporary_table_leftover.SF-2779437
+temporary_table_leftover.SF-2779437
temporary_table_leftover.SF-2734713
multi-column_join_with_expression.SF-2783279
BOM.SF-2787813
## Comment 11566
Date: 2009-11-16 10:44:42 +0100
From: @drstmane
for the records:
the related test is still active in the Current development trunk and fails there:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/dumping_tables.SF-2776908--optimizers.out.00.html
## Comment 11567
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2776908 at http://sourceforge.net/support/tracker.php?aid=2776908
| \d <table> doesn't work with `mserver5 --optimizers` | https://api.github.com/repos/MonetDB/MonetDB/issues/2050/comments | 0 | 2020-11-30T10:18:43Z | 2024-06-28T07:25:23Z | https://github.com/MonetDB/MonetDB/issues/2050 | 753,347,255 | 2,050 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-20 02:23:04 +0200
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-04-21 02:20:43 +0200
## Comment 11554
Date: 2009-04-20 14:23:04 +0200
From: @grobian
Stopping a database using monetdb on Linux never returns and makes merovingian unresponsive to any further commands.
## Comment 11555
Date: 2009-04-21 14:20:43 +0200
From: @grobian
this bug is a regression introduced by the original fix for http://sourceforge.net/support/tracker.php?aid=2747661 which was reverted
## Comment 11556
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2776145 at http://sourceforge.net/support/tracker.php?aid=2776145
| Merovingian: monetdb stop hangs on Linux | https://api.github.com/repos/MonetDB/MonetDB/issues/2049/comments | 0 | 2020-11-30T10:18:40Z | 2024-06-28T07:37:12Z | https://github.com/MonetDB/MonetDB/issues/2049 | 753,347,205 | 2,049 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-20 02:00:32 +0200
From: @swingbit
To: @njnes
Version: -- development
Last updated: 2009-04-20 09:12:18 +0200
## Comment 11551
Date: 2009-04-20 14:00:32 +0200
From: @swingbit
sql>create view x as select 1;
MAPI = monetdb@localhost:50151
ACTION= read_line
QUERY = create view x as select 1;
ERROR = Connection terminated
from merovingian.log:
ERR test[1474]: called table_insert(_columns) with wrong number of args (9,1)
ERR test[1474]: mserver5: /export/scratch0/roberto/MonetDB/src/sql/src/storage/bat/bat_table.mx:213: table_insert: Assertion `0' failed.
## Comment 11552
Date: 2009-04-20 21:12:18 +0200
From: @njnes
fixed missing column name, test added to src/test/BugTracker-2009/missing_column_name.SF-2776100
## Comment 11553
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2776100 at http://sourceforge.net/support/tracker.php?aid=2776100
| SQL: "CREATE VIEW AS SELECT 1;" fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2048/comments | 0 | 2020-11-30T10:18:36Z | 2024-06-27T11:39:15Z | https://github.com/MonetDB/MonetDB/issues/2048 | 753,347,156 | 2,048 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-20 05:19:51 +0200
From: Syeed Mansur <<smansur>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-20 08:17:38 +0200
## Comment 11548
Date: 2009-04-20 05:19:51 +0200
From: Syeed Mansur <<smansur>>
I am using SunOS opensolaris 5.11 64-bit, and my builds are failing. I downloaded all the sources from the CVS repository, and used bootstrap to setup the build. This produced a configure script in the MonetDB package directory, which when invoked produced the following error:
configure: error: need GCC version >=3.X for 64 bits
However, I am using gcc version 3.4.3:
gcc --version
gcc (GCC) 3.4.3
So, to work-through the problem, I used aclocal and autoconf to rebuild the configure script, which produced the following errors:
aclocal
/usr/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE
/usr/share/aclocal/audiofile.m4:12: run info '(automake)Extending aclocal'
/usr/share/aclocal/audiofile.m4:12: or see http://sources.redhat.com/automake/automake.htmlExtending-aclocal
configure.in:63: warning: macro `AM_MONETDB_XQ_VARS_1' not found in library
configure.in:66: warning: macro `AM_MONETDB_DEFAULTS' not found in library
configure.in:69: warning: macro `AM_MONETDB_COMPILER' not found in library
configure.in:70: warning: macro `AM_MONETDB_TOOLS' not found in library
configure.in:71: warning: macro `AM_MONETDB_OPTIONS' not found in library
configure.in:72: warning: macro `AM_MONETDB_UTILS' not found in library
configure.in:85: warning: macro `AM_MONETDB_LIBS' not found in library
configure.in:103: warning: macro `AM_MONETDB_XQ_VARS_2' not found in library
autoconf -f
configure.in:63: error: possibly undefined macro: AM_MONETDB_XQ_VARS_1
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:66: error: possibly undefined macro: AM_MONETDB_DEFAULTS
configure.in:69: error: possibly undefined macro: AM_MONETDB_COMPILER
configure.in:70: error: possibly undefined macro: AM_MONETDB_TOOLS
configure.in:71: error: possibly undefined macro: AM_MONETDB_OPTIONS
configure.in:72: error: possibly undefined macro: AM_MONETDB_UTILS
configure.in:85: error: possibly undefined macro: AM_MONETDB_LIBS
configure.in:103: error: possibly undefined macro: AM_MONETDB_XQ_VARS_2
A configure script did get produced, and when I invoked this script, I received the following errors:
configure --prefix=/root/makemonet/bin --enable-bi1970-01-01 01:01:04 +0100 --enable-debug=no --enable-assert=no --enable-optimize=yes
/root/sourcemonet/MonetDB/configure: line 19267: syntax error at line 19887: `>' unexpected
I must be doing something wrong, but after several days of reviewing, I can't seem to figure out the problem. Any help would be greatly appreciated.
Thanks,
Sid
## Comment 11549
Date: 2009-04-20 08:17:38 +0200
From: @grobian
dupe of 2774951.
## Comment 11550
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2775422 at http://sourceforge.net/support/tracker.php?aid=2775422
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| Build Fails on OpenSolaris 64-Bit | https://api.github.com/repos/MonetDB/MonetDB/issues/2047/comments | 0 | 2020-11-30T10:18:33Z | 2024-06-28T07:37:12Z | https://github.com/MonetDB/MonetDB/issues/2047 | 753,347,114 | 2,047 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-19 11:18:38 +0200
From: Syeed Mansur <<smansur>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-05-27 03:57:48 +0200
## Comment 11520
Date: 2009-04-19 23:18:38 +0200
From: Syeed Mansur <<smansur>>
I am using SunOS opensolaris 5.11 64-bit, and my builds are failing. I downloaded all the sources from the CVS repository, and used bootstrap to setup the build. This produced a configure script in the MonetDB package directory, which when invoked produced the following error:
configure: error: need GCC version >=3.X for 64 bits
However, I am using gcc version 3.4.3:
gcc --version
gcc (GCC) 3.4.3
So, to work-through the problem, I used aclocal and autoconf to rebuild the configure script, which produced the following errors:
aclocal
/usr/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE
/usr/share/aclocal/audiofile.m4:12: run info '(automake)Extending aclocal'
/usr/share/aclocal/audiofile.m4:12: or see http://sources.redhat.com/automake/automake.htmlExtending-aclocal
configure.in:63: warning: macro `AM_MONETDB_XQ_VARS_1' not found in library
configure.in:66: warning: macro `AM_MONETDB_DEFAULTS' not found in library
configure.in:69: warning: macro `AM_MONETDB_COMPILER' not found in library
configure.in:70: warning: macro `AM_MONETDB_TOOLS' not found in library
configure.in:71: warning: macro `AM_MONETDB_OPTIONS' not found in library
configure.in:72: warning: macro `AM_MONETDB_UTILS' not found in library
configure.in:85: warning: macro `AM_MONETDB_LIBS' not found in library
configure.in:103: warning: macro `AM_MONETDB_XQ_VARS_2' not found in library
autoconf -f
configure.in:63: error: possibly undefined macro: AM_MONETDB_XQ_VARS_1
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.in:66: error: possibly undefined macro: AM_MONETDB_DEFAULTS
configure.in:69: error: possibly undefined macro: AM_MONETDB_COMPILER
configure.in:70: error: possibly undefined macro: AM_MONETDB_TOOLS
configure.in:71: error: possibly undefined macro: AM_MONETDB_OPTIONS
configure.in:72: error: possibly undefined macro: AM_MONETDB_UTILS
configure.in:85: error: possibly undefined macro: AM_MONETDB_LIBS
configure.in:103: error: possibly undefined macro: AM_MONETDB_XQ_VARS_2
A configure script did get produced, and when I invoked this script, I received the following errors:
configure --prefix=/root/makemonet/bin --enable-bi1970-01-01 01:01:04 +0100 --enable-debug=no --enable-assert=no --enable-optimize=yes
/root/sourcemonet/MonetDB/configure: line 19267: syntax error at line 19887: `>' unexpected
I must be doing something wrong, but after several days of reviewing, I can't seem to figure out the problem. Any help would be greatly appreciated.
Thanks,
Sid
## Comment 11521
Date: 2009-04-20 08:16:26 +0200
From: @grobian
Is it possible to use pre-bootstrapped sources, like e.g. the monetdb-install.sh script does?
If you have to use CVS sources, does monetdb-install.sh --cvs produce the same autoconf errors? It seems to me you have an order problem.
Last suggestion, don't use --enable-bits, but use export CC="gcc -m64" CXX="g++ -m64" instead. Be aware that the shipped compiler is quite old, and uses Sun ld though.
## Comment 11522
Date: 2009-04-20 08:28:23 +0200
From: @drstmane
Fabian:
Internally (i.e., in buildtools/conf/MonetDB.m4), --enable-bi1970-01-01 01:00:00 +0100<bits> is translated into CC="$CC -m<bits>"; hence, I don't see much of a difference...
Syeed:
Could you please undo/remove all your modification to checked-out and/or generated file,
patch your checked-out buildtools/conf/MonetDB.m4 as follows:
--------
Index: buildtools/conf/MonetDB.m4
===================================================================
RCS file: /cvsroot/monetdb/buildtools/conf/MonetDB.m4,v
retrieving revision 1.108.2.2
diff -u -r1.108.2.2 MonetDB.m4
--- buildtools/conf/MonetDB.m4 14 Apr 2009 11:36:50 -0000 1.108.2.2
+++ buildtools/conf/MonetDB.m4 20 Apr 2009 06:24:04 -0000
@@ -586,7 +586,7 @@
*-*-*-*-$native_bits)
;;
yes-*-solaris*-*-*)
- case `$bits-$CC -v 2>&1` in
+ case "$bits-`$CC -v 2>&1`" in
32-*|*-*'gcc version '[[34]]'.'*) ;;
*) AC_MSG_ERROR([need GCC version >=3.X for 64 bits]);;
esac
--------
and then try to compile & install buildtools & MonetDB from scratch, again,
and report what happens?
Also, could you please send us the output of `gcc -v` on your systems?
## Comment 11523
Date: 2009-04-21 03:51:44 +0200
From: Syeed Mansur <<smansur>>
Fabian & Stefan: Thanks for your quick responses. Fabian, the reason I'm not using the pre-bootstrapped install.sh command is that I've already tried it, and on OpenSolaris 64-bit it seems to produce binaries that are 32-bit, which is not good enough for me to load up a 530GB table.
Stefan: I implemented your suggestion, and the build process got past the original error, but not it looks like its getting caught in a different problem. configure seems to complete successfully, and then when I issue the gmake command, the process finishes as follows:
gmake[5]: Leaving directory `/root/makemonet/src/gdk'
gmake[4]: Leaving directory `/root/makemonet/src/gdk'
gmake[4]: Entering directory `/root/makemonet/src'
gmake[4]: Nothing to be done for `all-am'.
gmake[4]: Leaving directory `/root/makemonet/src'
gmake[3]: Leaving directory `/root/makemonet/src'
gmake[2]: Leaving directory `/root/makemonet/src'
Making all in conf
gmake[2]: Entering directory `/root/makemonet/conf'
/usr/sfw/bin/gmake all-am
gmake[3]: Entering directory `/root/makemonet/conf'
gmake[3]: Nothing to be done for `all-am'.
gmake[3]: Leaving directory `/root/makemonet/conf'
gmake[2]: Leaving directory `/root/makemonet/conf'
gmake[2]: Entering directory `/root/makemonet'
gmake[2]: Leaving directory `/root/makemonet'
gmake[1]: Leaving directory `/root/makemonet'
I went ahead and invoked the "gmake install" command, and that (as expected) did not install any binaries. For reference, during the bootstrap, I recieved the following errors:
Remember to add `AC_PROG_LIBTOOL' to `configure.in'.
You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'.
Putting files in AC_CONFIG_AUX_DIR, `conf'.
/usr/share/aclocal/audiofile.m4:12: warning: underquoted definition of AM_PATH_AUDIOFILE
/usr/share/aclocal/audiofile.m4:12: run info '(automake)Extending aclocal'
/usr/share/aclocal/audiofile.m4:12: or see http://sources.redhat.com/automake/automake.htmlExtending-aclocal
Looks like a unified context diff.
Hunk 1 failed at line 6386.
1 out of 1 hunks failed: saving rejects to aclocal.m4.rej
done
configure.in:33: installing `conf/missing'
configure.in:33: installing `conf/install-sh'
By the way, the gcc -v command returns the following:
l gcc -v
Reading specs from /usr/sfw/lib/gcc/i386-pc-solaris2.11/3.4.3/specs
Configured with: /builds2/sfwnv-gate/usr/src/cmd/gcc/gcc-3.4.3/configure --prefix=/usr/sfw --with-as=/usr/sfw/bin/gas --with-gnu-as --with-ld=/usr/ccs/bin/ld --without-gnu-ld --enable-languages=c,c++,f77,objc --enable-shared
Thread model: posix
gcc version 3.4.3 (csl-sol210-3_4-20050802)
## Comment 11524
Date: 2009-04-21 08:07:32 +0200
From: @drstmane
Syeed,
after applying my patch, did you recompile everything from srcatch, i.e., remove your complete build director(y|ies) and install prefix, and then start with ./bootstrap in buildtools?
If so, could you please provide us with the exact configure call you used as well as the complete output of ./bootstrap, configure, make & make install for buildtools & MonetDB?
Alternatively, did you try the pre-bootstrapped super sourceball with
export CC='gcc -m64' ; ./monetdb-install.sh ...
?
Stefan
## Comment 11525
Date: 2009-04-21 09:12:12 +0200
From: Syeed Mansur <<smansur>>
Stefan,
I did indeed try the pre-bootstrapped sourceball with 'gcc -m64'; monetdb-install.sh. That compiles fine, and then when I try to load my data (using COPY command for 1.5Billion rows), I get the following error:
mclient -lsql --database=syscodb < /root/load_xactions.sql
MAPI = monetdb@localhost:50000
QUERY = copy 1500000000 records into transactions
ERROR = !SQLException:importTable:failed to import table
!ERROR: HEAPextend: failed to extend to 3000000000 for 20/2060tail
!ERROR: TABLETcreate_bats: Failed to create bat of size 1500000000
!ERROR: TABLETload_file:could not allocate bats
Note, this failure occurs on OpenSolaris, but this does not occur on Linux (Fedora 10). For reference, the results of 'mserver5 --version' is:
MonetDB server v5.11.0 (64-bit), based on kernel v1.29.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: /root/MonetDB
Libraries:
libpcre: 7.4 2007-09-21 (compiled with 7.4)
openssl: OpenSSL 0.9.8a 11 Oct 2005 (+ security patches to 2007-10-13) (compiled with OpenSSL 0.9.8a 11 Oct 2005 (+ security patches to 2007-10-13))
libxml2: 2.6.31 (compiled with 2.6.31)
Compiled by: @opensolaris
Compilation: gcc -m64 -m64 -I/usr/sfw/include -L/usr/sfw/lib -D__EXTENSIONS__ -std=c99 -O6 -fomit-frame-pointer -finline-functions -falign-loops=4 -falign-jumps=4 -falign-functions=4 -fexpensive-optimizations -funroll-loops -frerun-cse-after-loop -frerun-loop-opt
Linking : /usr/ccs/bin/ld -m64 -L/usr/sfw/lib -R/usr/sfw/lib
So, it looks like the 64-bit version of MonetDB has been picked up, so I'm not sure why my COPY is failing.
In an attempt to work-through this issue from scratch, I figured I'd try to download the sources directly from CVS and build everything afresh. That led me to the errors which caused me to open this bug report.
With respect to your other question below, I did recompile everything from scratch (I may have missed something, so I will re-do everything). I completely removed my build directory and install prefix directory. I'll let you know what happens. In the meantime, should I open a different bug report for the COPY failure above, or is that considered a part of this current bug report?
Regards,
Sid
## Comment 11526
Date: 2009-04-21 09:33:42 +0200
From: @drstmane
How much physical (RAM) and virtual (swap) memory do your OpenSolaris and Linux machines have?
How many CPUs/cores do your machines have? If the OpenSolaris has more than 1 CPU/core, could you please try to start the mserver5 in single-threaded mode (--set gdk_nr_threads=1) for loading the data via copy into?
(cf., https://sourceforge.net/tracker/?func=detail&aid=2771052&group_id=56967&atid=482468)
In case the above doesn't work, instead of using the source tarball of the development trunk, could you please try the latest Stable release
MonetDB-Feb2009-SuperBall-SP1.tar.{bz2,lzma} from http://monetdb.cwi.nl/downloads/sources/Feb2009-SP1/ ?
## Comment 11527
Date: 2009-04-21 09:45:00 +0200
From: Syeed Mansur <<smansur>>
The OpenSolaris and the Linux machine are identical (I installed MonetDB on the Linux machine last week, and then wiped Linux off that machine and installed OpenSolaris - my goal is to test the ZFS filesystem and see if I can get performance increases on Monetdb using the compression feature of ZFS). Anyway, the computer has 1 CPU, 2 cores, with 4GB of physical RAM and 4GB of swap.
I was remote-logged in to my machine and it froze after I tried to copy the records into MonetDB. I will have to try the reload in single-threaded mode (by the way, does MonetDB automatically recognize the number of cores and spawn multiple threads to coincide with the cores?) after I go into the office and reboot the machine (probably in 5 hours).
## Comment 11528
Date: 2009-04-21 10:01:59 +0200
From: @drstmane
MonetDB is indeed supposed to automatically detect the number of cores and parallelize query execution accordingly --- at least it does on Linux; on my quad-core CPU, it says:
$ mserver5
MonetDB server v5.10.4, based on kernel v1.28.3
Serving database 'demo', using 4 threads
I'm not completely sure, whether it also works on OpenSolaris --- please check the welcome message of your mserver5.
Did your OpenSolaris box freeze (right) after the error message you reported?
How big is your 1.5 billion rows table that you managed to load on the 4GB Linux box? 530GB as mentioned earlier? That would indeed be very impressive ...
## Comment 11529
Date: 2009-04-21 10:12:11 +0200
From: @grobian
I'd like to note that OpenSolaris 2008.05 (and I also think 2008.11) is unstable. I had it installed on my desktop and had crashes all the time. I updated to "SunOS 5.11 snv_101b i86pc i386 i86pc Solaris" and ever since never had to reboot for anything. I think you'll have to update your OpenSolaris system, or install Solaris 10 to get a stable system.
I use OpenSolaris 64-bits on a single core 2GB RAM machine with 32G swap. CPU/core detection of MonetDB works also on Solaris/OpenSolaris.
## Comment 11530
Date: 2009-04-22 23:34:41 +0200
From: Syeed Mansur <<smansur>>
Fabian: I recovered the server after it crashed, and updated the 2008.11 OpenSolaris install that I had running. I'm not sure why the whole system crashed, but it is back up and running now.
Stefan: I agree - I think it is quite impressive that MonetDB (without using X100) was able to bring up a 530GB table, and I was able to run a simple query in Linux. As for my OpenSolaris installation, I now have rebuilt MonetDB using the pre-bootstrapped code (via install.sh) and have set CC='gcc -m64'. I started mserver5 with a single thread, and I am happy to say that so far so good (thank you very much for your help). I started loading the 530GB table, and it will take another 23 hours to finish loading, but there are no failures thus far.
As a side note, I am trying to use MonetDB on OpenSolaris so that I can take advantage of the ZFS filesystem, which provides transparent compression. On the Linux deployment, I saw that I was very much I/O bound (CPU utilization was at 40-50%), and I'd like to cheat the I/O boundedness by using transparent compression. Hopefully, this will give me a noticeable performance boost. If I'm able to run my queries successfully in OpenSolaris, I think our team will want to switch there focus onto X100 and we will have to see if there is any way for us to get our hands on the X100 module.
I'll let you know tomorrow if the data upload successfully completes and if I'm able to successfully run a query.
Once again, thank you so much for your help thus far.
-Sid
p.s. Note, I do think that once we start playing with the MonetDB source code itself, we will still need to figure out how to get the non-pre-bootstrapped sources to compile.
## Comment 11531
Date: 2009-04-23 13:45:03 +0200
From: @drstmane
Sid,
thank you very much for keeping us posted --- loading a 1.5 billion rows 530GB table on a 64-bit system with "just" 4 GB RAM is something we hadn't tried (or heard of) before --- good to know that it works on Linux, and keeping my fingers crossed that it will also work on OpenSolaris ...
We are also very curious to learn about your experiences with using MonetDB on ZFS!
We are successfully compiling MonetDB from plain CVS sources every night in our testing environment (cf., http://monetdb.cwi.nl/Development/TestWeb/) on two different OpenSolaris installations (cf.,
http://monetdb.cwi.nl/Development/TestWeb/Platforms/):
1)
$ cat /etc/release
OpenSolaris 2008.11 snv_101b_rc2 X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 19 November 2008
64-bit on an Athlon 64 X2 3800+ using
Gentoo Prefix Base System version 1.12.5
2)
$ cat /etc/release
Solaris Express Community Edition snv_93 X86
Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
Use is subject to license terms.
Assembled 03 July 2008
32-bit on a Xeon E5405 (Quad-Core)
using the plain system tools.
Hence, I'm confident we will also be able to collaboratively sort-out and solve your problems with compiling from plain CVS source on your OpenSolaris installation (respectively an update or fix of that).
Stefan
## Comment 11532
Date: 2009-04-28 12:51:12 +0200
From: @grobian
Is this still an issue? I'm able to build MonetDB on my 64-bits OpenSolaris system for a while now.
Bootstrapping simply requires many (up-to-date) developement tools that you (may) have to install in some way.
## Comment 11533
Date: 2009-04-29 23:13:27 +0200
From: Syeed Mansur <<smansur>>
Fabian,
Sorry for the delay in posting my response. I have been attempting to upload my 517GB CSV file into a table on MonetDB over the last 3 days, and after 76 hours, the upload is still not finished. However, that 517GB CSV file is now consuming upwards of 1.1TB of space on MonetDB. I don't know if something has gone wrong - I suspect something fishy is happening on the ZFS filesystem in OpenSolaris, as I did not have this problem on Fedora 10.
With respect to the crux of this bug report, I believe I have installed all the up-to-date development tools (gcc, automake, autoheader, autoconfig, autoreconfig, m4, etc.). I may have to thoroughly start from scratch and see what happens. However, I am a bit surprised that you were able to bootstrap succcessfully on OpenSolaris 2008.11 - I could not make any progress without implementing the following change per Stefan's directions to the buildtools/conf/MonetDB.m4 file.
Should I go ahead and request closure of this bug report and try to begin bootstrapping MonetDB from a completely new and fresh install of OpenSolaris? Also, should I not worry about the 517GB CSV file upload taking 1.1TB in MonetDB (i.e., this is what you would expect).?
## Comment 11534
Date: 2009-04-29 23:15:55 +0200
From: Syeed Mansur <<smansur>>
Fabian & Stefan: A third question - the main reason that we are using OpenSolaris is because we are trying to "cheat" the I/O boundedness by using Gzip-1 compression on the filesystem (and that's giving us about 5.3x compression). Do you know what is the state of X100 development, and whether or not we can use it on Fedora10? If so, then I don't think we would continue to entertain OpenSolaris any further.
## Comment 11535
Date: 2009-04-29 23:35:40 +0200
From: @drstmane
Sid,
wrt. X100:
It is actively being developed, but not yet publicly available --- I'll ask the X100 developers, whether they could comment in more detail (publicly or privately).
wrt. bootstrapping on OpenSolaris:
The patch for buildtools/conf/MonetDB.m4 that I suggested is indeed a bug fix that I committed to the CVS repository on 2009/04/21.
wrt.ZFS:
did/could you try to load your 517 GB CSV on OpenSolaris with a non-comprssing file system to check whether the problems are indeed ZFS related, or rather OpenSolaris related? Or the combination of both --- I'm not sure how well OpenSolaris + ZFS can handle memory-mapped files ...
Stefan
## Comment 11536
Date: 2009-04-30 10:23:02 +0200
From: @grobian
Sid, I use a 64-bits compiler, e.g. x86_64-pc-solaris2.11-gcc. Hence, the trickery with --enable-bits or CC="gcc -m64" isn't necessary, and also the code path in the .m4 file isn't activated. I built this compiler myself (with some help of Portage actually), as it is not available on any *Solaris system.
How is your ZFS pool setup? mirror, stripe, raidz? How many disks does it contain? How did you measure the space usage? Note that zfs has some different metrics to report used diskspace, depending on your configuration.
## Comment 11537
Date: 2009-05-01 09:09:31 +0200
From: Syeed Mansur <<smansur>>
Fabian: The ZFS pool is setup as raid0 with 4 disks. I'm measuring space usage via the ZFS get all command. I'm also using du -h to measure disk utilization. As for your compiler, I was wondering if you can provide instructions on how to use specially configured compilers to get the head sources from CVS to compile on 64-bit opensolaris.
Stefan: I stopped mserver5, and started merovingian (although, I can't seem to figure out how to stop merovingian). I then truncated my 517GB CSV file down to 5.17GB and tried loading that into an uncompressed ZFS pool. I loaded it in, and the total disk utilization was 12.69GB. I ran a query, and successfully got a response in 14 seconds (compared to 348 seconds on Infobright for the same exact hardware setup but on Fedora). Once this completed, I changed ZFS to use Gzip-1 compression and then reloaded the 5.17GB file. In this scenario, I got 5.1x compression and used roughly 2.6GB of space. I resubmitted the same query as above, and my result came back in 8.7 seconds!
I just kicked off a load where I'll attempt to put 51.7GB of data into MonetDB - I'll let you know how that works out. However, given the incredible performance that we're already seeing with the 5GB file, we're quite eager to get our 500GB data set working. To that end, we're especially eager to hear your feedback from the X100 team (you or the X100 team can contact me directly at sm24@cornell.edu or syeed.mansur@sentrana.com).
One thing we can do to get around the excessive memory use problem on a single server is to go to a MPP setup. In one of Peter Boncz's papers, he mentions the possibility of partitioning a data set across a shared-nothing architecture of servers. The technical overview of MonetDB also delineates some information about partitioning BATS and using TCP/IP to configure multiple servers - but, its not clear from the literature how we can make this work.
Since my questions are going beyond the central crux of the original bug report, I would rather take this discussion offline and discuss over email/phone with your team. In the meantime, I would suggest we close this bug report once you or Fabian can suggest some details about how to successfully compile non pre-bootstrapped sources.
Last but not least, thanks to both you & Fabian for your earnest help and for contributing to the development of a rather amazing database engine (we have been evaluating Vertica, Greenplum, LucidDB, Infobright, etc, and have found MonetDB to be the richest in terms of intellectual thought-leadership and in terms of performance!). As a company, there is great interest from our team to become involved with MonetDB - and with respect to this, it may perhaps make sense to further the discussion offline and outside of this bug report.
Thanks,
Sid
## Comment 11538
Date: 2009-05-01 09:39:28 +0200
From: @grobian
Sid, since you ask for it, this is how I get my compiler, using the 64-bits instructions:
http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml
As for the ZFS configuration, I have both a mirror and a stripe, and I checked their usage (simply `zfs status` shows it) which align with what `df -h` reports. The only occasion when it will differ is when using raidz.
I don't know why your file on disk is twice the size of your CSV file, as it was on Linux, but with compression it seems you can cut it down to an amazing small size. I'm not sure how much storage size is an issue for you?
## Comment 11539
Date: 2009-05-01 10:01:19 +0200
From: Syeed Mansur <<smansur>>
Storage size is a rather important issue because we are trying to overcome the I/O boundedness of our queries by moving over to SSD Drives connected via PCI-E (such as the Fusion-IO Duo product). To minimize expense of the SSD devices, and be able to fit almost a terabyte of data into storage, we are eager to compress. Even if we don't use SSD (solid state disks), compression allows us to "cheat" I/O throughput from normal SAS drives (so, to that end, storage size is a significant issue for us --> Indeed, that is another reason for our interest in X100).
Thanks for the instructions - I'll attempt a compile of the non pre-bootstrapped sources over the weekend.
## Comment 11540
Date: 2009-05-03 07:16:19 +0200
From: Syeed Mansur <<smansur>>
After a bit more investigation on why my 517GB file was consuming more than 1.1TB of space on MonetDB (please see comment from 2009-04-29 17:13), it looks like I have to use the OFFSET command in order to load the file properly. I am not sure if this is a bug, but this is what I've discovered thus far:
1) If I perform "COPY 9999 RECORDS into mytable from data.txt", the copy works fine (9,999 rows are loaded).
2) If I perform "COPY 10000 RECORDS into mytable from data.txt", the copy seems aberrant (108,000 instead of 10,000 rows are loaded).
3) If I perform "COPY 10000 offset 100 RECORDS into mytable from data.txt", the copy works fine (10,000 rows as specified are loaded).
I've tested on both OpenSolaris 64-bit and Fedora 10 64-bit. In both scenarios the above behavior occurred. It seems that I MUST use "OFFSET" in order to get more than 9,999 records loaded properly. Is this a bug, or intentional design?
## Comment 11541
Date: 2009-05-03 08:08:30 +0200
From: @drstmane
Sid,
I assume you hit a bug in multi-threaded bulk-loading similar or identical to the one reported in
ID: 2771052 "M5/SQL: parallel bulk-load (copy into) incorrect"
https://sourceforge.net/tracker/?func=detail&aid=2771052&group_id=56967&atid=482468
For bulk-loading (COPY INTO), please start your mserver5 in single-threaded mode (using "--set gdk_nr_threads=1" on the command line) and try again.
Stefan
## Comment 11542
Date: 2009-05-03 08:13:09 +0200
From: Syeed Mansur <<smansur>>
If I use merovingian, is there a way to specify the number of threads? Or, must I use mserver5?
## Comment 11543
Date: 2009-05-03 08:31:23 +0200
From: @drstmane
look for "gdk_nr_threads=" in your monetdb5.conf ;
if it's there, change it to "gdk_nr_threads=1";
otherwise add a line "gdk_nr_threads=1" to your monetdb5.conf;
then stop and restart your server / database.
## Comment 11544
Date: 2009-05-03 08:46:09 +0200
From: Syeed Mansur <<smansur>>
Thanks Stefan - that worked like a charm. I revised my conf file and restarted merovingian.
I have not yet implemented Fabian's directions for bootstrapping on OpenSolaris - for now, I'll just go ahead and rely on the pre-bootstrapped build. Perhaps we should go ahead and route this bug for closure (incidentally, I am unable to download the pre-bootstrapped sources from monetdb.cwi.nl - is the webserver down?).
## Comment 11545
Date: 2009-05-03 08:55:05 +0200
From: @drstmane
Due to a reconnection of the main power supply, CWI is without power this weekend, and hence, the MonetDB web server is indeed down --- sorry for the inconveniences --- it should be back up by Monday (not before 9am CEST, though).
## Comment 11546
Date: 2009-05-27 15:57:48 +0200
From: @grobian
closing per comment 2009-05-03 08:46
## Comment 11547
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2774951 at http://sourceforge.net/support/tracker.php?aid=2774951
| Build Fails on OpenSolaris 64-Bit | https://api.github.com/repos/MonetDB/MonetDB/issues/2046/comments | 0 | 2020-11-30T10:18:28Z | 2024-06-27T11:39:12Z | https://github.com/MonetDB/MonetDB/issues/2046 | 753,347,065 | 2,046 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-18 10:05:00 +0200
From: @sjoerdmullender
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-28 01:04:18 +0200
## Comment 11515
Date: 2009-04-18 22:05:00 +0200
From: @sjoerdmullender
See summary.
I'll deal with it.
## Comment 11516
Date: 2009-04-28 12:52:01 +0200
From: @grobian
was this fixed in the last release? (Feb2009-SP2)
## Comment 11517
Date: 2009-04-28 12:58:26 +0200
From: @drstmane
there have been related checkins; however, I'm not aware whether it has been tested/verified yet --- any Ubuntu/Debian user(s) to volunteer?
## Comment 11518
Date: 2009-04-28 13:04:18 +0200
From: @sjoerdmullender
It's in the release now.
## Comment 11519
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2773049 at http://sourceforge.net/support/tracker.php?aid=2773049
| mclient missing from Debian/Ubuntu packaging | https://api.github.com/repos/MonetDB/MonetDB/issues/2045/comments | 0 | 2020-11-30T10:18:25Z | 2024-06-27T11:39:11Z | https://github.com/MonetDB/MonetDB/issues/2045 | 753,347,013 | 2,045 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-17 06:55:09 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2009-11-15 03:09:45 +0100
## Comment 11509
Date: 2009-04-17 18:55:09 +0200
From: @drstmane
With a simple CSV file containing 100000000 rows, each holding just a single '1', I get the following when running a (default) 4-threaded mserver5 on my 4-core machine:
$ mserver5 --dbinit='include sql;'
MonetDB server v5.10.3, based on kernel v1.28.3
Serving database 'demo', 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 /ufs/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.28.3 loaded
$ mclient -lsql
sql>create table i0 (a integer);
0 tuples
sql>create table i1 (a integer);
0 tuples
sql>create table i2 (a integer);
0 tuples
sql>create table i3 (a integer);
0 tuples
sql>create table i4 (a integer);
0 tuples
sql>create table i5 (a integer);
0 tuples
sql>create table i6 (a integer);
0 tuples
sql>create table i7 (a integer);
0 tuples
sql>create table i8 (a integer);
0 tuples
$ mclient -lsql
sql>copy 1 records into i0 from '/tmp/1.csv';
Rows affected 1
sql>copy 10 records into i1 from '/tmp/1.csv';
Rows affected 10
sql>copy 100 records into i2 from '/tmp/1.csv';
Rows affected 100
sql>copy 1000 records into i3 from '/tmp/1.csv';
Rows affected 1000
sql>copy 10000 records into i4 from '/tmp/1.csv';
Rows affected 40000
sql>copy 100000 records into i5 from '/tmp/1.csv';
Rows affected 400000
sql>copy 1000000 records into i6 from '/tmp/1.csv';
Rows affected 4000000
sql>copy 10000000 records into i7 from '/tmp/1.csv';
Rows affected 40000000
sql>copy 100000000 records into i8 from '/tmp/1.csv';
Rows affected 100000000
(Mind the '4's where '1's are expected.)
The problem is analogously reproducible with `mserver5 --set gdk_nr_threads=3` & `mserver5 --set gdk_nr_threads=2`;
bulk-loading works fine with `mserver5 --set gdk_nr_threads=1`.
## Comment 11510
Date: 2009-04-17 19:13:45 +0200
From: @drstmane
added test in sql/src/test/BugTracker-2009/Tests/parallel_bulk-load.SF-2771052.{unpack_csv,test}.*
(Feb2009 release branch)
## Comment 11511
Date: 2009-07-31 06:54:32 +0200
From: @drstmane
Clean-up:
This one is no longer relevant, as parallel bulk loading has been disabled due to inherent design flaws:
===================================================================
2009/05/25 - sjoerd: MonetDB5/src/modules/mal/tablet.mx,1.194.2.3
Set nway to 1 since parallel import *cannot* work with the current
implementation: there is an inherent bug when the number of records to
be imported is smaller than what is available in the file.
===================================================================
## Comment 11512
Date: 2009-08-09 13:15:24 +0200
From: @mlkersten
The bug should have been left open, as it is a BUG part of at least two releases and should be fixed.
## Comment 11513
Date: 2009-11-15 15:09:45 +0100
From: @mlkersten
The Nov2009 release contains a parallel loader operational since sept. Used on both SF100 and the air-traffic-benchmark without causing problems. Closing the bug.
There is no option to have good test cases.
## Comment 11514
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2771052 at http://sourceforge.net/support/tracker.php?aid=2771052
| M5/SQL: parallel bulk-load (copy into) incorrect | https://api.github.com/repos/MonetDB/MonetDB/issues/2044/comments | 0 | 2020-11-30T10:18:22Z | 2024-06-27T11:39:10Z | https://github.com/MonetDB/MonetDB/issues/2044 | 753,346,967 | 2,044 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-17 02:02:57 +0200
From: @swingbit
To: @mlkersten
Version: -- development
Last updated: 2009-11-15 03:58:54 +0100
## Comment 11499
Date: 2009-04-17 14:02:57 +0200
From: @swingbit
Many of my recent experiments showed wrong/unexpected behaviours when executed with the mitosis optimizer on (default in development).
However, it was always difficult to come up with a reproducible bug.
This one is very easy to reproduce.
It executes a primary key self-join on the system-table 'types'.
The expected result is the relation itself.
sql>select * from types t1, types t2 where t1.id = t2.id;
26 tuples
The count is indeed correct, but there is no output.
The EXPLAIN of this query is something fun to see, I won't paste it here as it is very long.
## Comment 11500
Date: 2009-06-07 17:28:52 +0200
From: @mlkersten
this particular example works on the current version. Given the overhaul of Mitosis (et.al.) it is closed until a better example is given.
## Comment 11501
Date: 2009-06-07 19:28:21 +0200
From: @drstmane
Re-opened to remind us that we should add a test for this bug report,
e.g., using the new features to set optimizers at server start-up
(or at least give a reason why none can / need to be added).
## Comment 11502
Date: 2009-06-07 20:45:08 +0200
From: @swingbit
It seems that my first bug report was not accurate.
At that time, the 'reorder' optimizer was still on by default in the development version. Only later it was discovered to be buggy and disabled.
The problem reported is still there, but it shows up only when mitosis and reorder are BOTH enabled. Disabling one of the two makes the problem disappear.
sql>set optimizer='inline,remap,evaluate,costModel,coercions,emptySet,mitosis,aliases,mergetable,deadcode,constants,commonTerms,reorder,joinPath,deadcode,reduce,garbageCollector,dataflow,history,multiplex';
0 tuples
sql>select * from types t1, types t2 where t1.id = t2.id;
26 tuples
## Comment 11503
Date: 2009-06-07 21:00:16 +0200
From: @swingbit
A comment about this bug report:
I do realize that the reorder optimizer is now known to be buggy and disabled.
This could mean the bug report can be closed, as it addresses 'experimental' code.
However, because it seems the problem isn't just in 'reorder' itself, but it is its interaction with mitosis that cause the problem, it may make sense to investigate this issue a bit further.
In addition, I consider the bug report valid as the experimental code it addresses is very well reachable (without any warning to the user) also in the stable version.
## Comment 11504
Date: 2009-06-07 21:24:39 +0200
From: @mlkersten
The monetdb.conf is extended with the Mitosis-mergetable-reorder-dataflow pipeline. It aims at better
locality and smaller partitions to improve processing.
The results of the SQL test run shows errors in the following tests:
ATIS/select-simple-join
wisconsin/wisconsin-select
test/marcin1
huge-expression
orderby-in-function
dependencies
## Comment 11505
Date: 2009-07-20 21:03:27 +0200
From: @mlkersten
Test file added BugTracker-2009/Tests/reorder.SF-2770608.sql
## Comment 11506
Date: 2009-07-20 21:03:29 +0200
From: @mlkersten
Test file added BugTracker-2009/Tests/reorder.SF-2770608.sql
## Comment 11507
Date: 2009-11-15 15:58:54 +0100
From: @mlkersten
There are about a dozen tests not working with mitosis+reorder
Closing this bug as it falls under the total QA for the pipelines.
Test availlable to trap it again.
## Comment 11508
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2770608 at http://sourceforge.net/support/tracker.php?aid=2770608
| SQL: mitosis+reorder (was 'mitosis') goes wild | https://api.github.com/repos/MonetDB/MonetDB/issues/2043/comments | 0 | 2020-11-30T10:18:18Z | 2024-06-28T07:37:11Z | https://github.com/MonetDB/MonetDB/issues/2043 | 753,346,905 | 2,043 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-14 11:30:35 +0200
From: @swingbit
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-14 07:27:55 +0200
## Comment 11495
Date: 2009-04-14 11:30:35 +0200
From: @swingbit
--enable-bi1970-01-01 01:01:04 +0100 --enable-optimize --disable-debug
cc1: warnings being treated as errors
/export/scratch0/roberto/MonetDB/src/sql/src/backends/monet5/sql.mx: In function ‘SQLnewAquarium’:
/export/scratch0/roberto/MonetDB/src/sql/src/backends/monet5/sql.mx:4082: error: implicit declaration of function ‘OCTOPUSworker’
/export/scratch0/roberto/MonetDB/src/sql/src/backends/monet5/sql.mx:4082: error: return makes pointer from integer without a cast
/export/scratch0/roberto/MonetDB/src/sql/src/backends/monet5/sql.mx: In function ‘SQLdropAquarium’:
/export/scratch0/roberto/MonetDB/src/sql/src/backends/monet5/sql.mx:4088: error: implicit declaration of function ‘OCTOPUSdrop’
/export/scratch0/roberto/MonetDB/src/sql/src/backends/monet5/sql.mx:4088: error: return makes pointer from integer without a cast
## Comment 11496
Date: 2009-04-14 16:50:34 +0200
From: @sjoerdmullender
Is this still a problem after Martin's fix of 11:40 this morning?
## Comment 11497
Date: 2009-04-14 19:27:55 +0200
From: @swingbit
It's fixed
## Comment 11498
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2761480 at http://sourceforge.net/support/tracker.php?aid=2761480
| compilation error | https://api.github.com/repos/MonetDB/MonetDB/issues/2042/comments | 0 | 2020-11-30T10:18:15Z | 2024-06-27T11:39:08Z | https://github.com/MonetDB/MonetDB/issues/2042 | 753,346,857 | 2,042 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-13 04:41:10 +0200
From: Christophe Galerne <<cgalerne100>>
To: @njnes
Version: -- development
Last updated: 2009-04-19 10:50:24 +0200
## Comment 11491
Date: 2009-04-13 16:41:10 +0200
From: Christophe Galerne <<cgalerne100>>
Setup:
MonetDB server v5.10.2, based on kernel v1.28.2
Compiled for i686-pc-win32/32bit with 32bit OIDs dynamically linked
MonetDB/SQL module v2.28.2 loaded
Given 2 tables with some columns having the same names.
An update statement to copy some data from one table to the other returns an incorrect result.
See the attachment for a reproducible test case.
## Comment 11492
Date: 2009-04-13 21:02:20 +0200
From: @njnes
Your column names are ambiguous. Thats why the query translates to a cross product. With fully specified columns the result should be as expected.
## Comment 11493
Date: 2009-04-19 10:50:24 +0200
From: Christophe Galerne <<cgalerne100>>
You are correct: adding TARGET.TOTO and TARGET.TITI
## Comment 11494
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2759061 at http://sourceforge.net/support/tracker.php?aid=2759061
| Incorrect update result for tables with same column names | https://api.github.com/repos/MonetDB/MonetDB/issues/2041/comments | 0 | 2020-11-30T10:18:12Z | 2024-06-28T07:37:11Z | https://github.com/MonetDB/MonetDB/issues/2041 | 753,346,825 | 2,041 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-13 06:12:53 +0200
From: John Rylander <<johnrylander>>
To: @njnes
Version: -- development
Last updated: 2009-04-18 01:57:07 +0200
## Comment 11475
Date: 2009-04-13 06:12:53 +0200
From: John Rylander <<johnrylander>>
I'm using the latest stable Windows Vista x64-compatible release 5.10.2 based on the 1.28.2 kernel.
On an table "biglist" with 51751608 records and just one field, a numeric 14,2 field called "rt", I executed the following:
UPDATE biglist SET rt=1.21;
(Rows affected 51751608)
Then I tried:
SELECT AVG(rt) FROM biglist;
And of course it reported 1.21--fine. :)
But then I tried:
SELECT AVG(SQRT(rt)) from biglist;
and instead of the expected 1.1, I got 0.64837467465745224. A wide variety of other SQRT aggregations also were wildly off the mark. (And I tried this earlier with a 7,2 numeric field--no joy.)
Any suggestions? My apologies if this has already been fixed, or if I'm doing something wrong--I'm entirely new to MonetDB, but think it's an amazing project--amazing! I hope this can be resolved soon, so I can rely on it. :)
Thanks to all the developers and testers! I hope to do some tiny part here with this report.
## Comment 11476
Date: 2009-04-13 15:39:57 +0200
From: John Rylander <<johnrylander>>
If others can confirm this bug, i.e., if I'm not just doing some wrong and this hasn't already been fixed in a developer build, then I think the priority of this bug should be raised significantly.
## Comment 11477
Date: 2009-04-13 21:46:14 +0200
From: @njnes
It seems the bug is already fixed or related to your db size. I tested with a small table and this works fine.
Could you try your query on a small table?
## Comment 11478
Date: 2009-04-13 22:01:46 +0200
From: @mlkersten
Don't forget that SQRT works on doubles and produces doubles.
This leads to rounding errors, but does not explain yours.
>create table tmp(rt decimal(10,2));
insert into tmp values(1.2);
insert into tmp values(1.2);
insert into tmp values(1.2);
insert into tmp values(1.2);
insert into tmp values(1.2);
select avg(rt), avg(sqrt(rt)) from tmp; &3
>&2 1 -1
>&2 1 -1
>&2 1 -1
>&2 1 -1
>&2 1 -1
>
&1 2 1 2 1
% sys., sys. table_name
% scale_down_L11, L12 name
% double, double type
% 22, 22 length
[ 1.2, 1.0954451560974121 ]
>select sqrt(1.2);
&1 0 1 1 1
% . table_name
% sqrt_single_value name
% real type
% 13 length
[ 1.09544516 ]
## Comment 11479
Date: 2009-04-13 22:29:38 +0200
From: John Rylander <<johnrylander>>
Agreed with both comments below.
At first I suspected a compound rounding error--and maybe the problem will still prove to be some variation on that theme--so I increased the precision from 7,2 to 14,2 with no change in results. (More precisely, I remember that the results were still way off; I do not recall if they were identical.)
And this is undoubtedly related to table size: small tables do not produce this error; to my mind, this doesn't seriously mitigate the concern. I am not sure where the line is drawn, and I'm not yet good enough at automating MonetDB to easily make up an iterative test case to find out. (I was hoping this would be easy for someone else out there. ;) ) BTW, I also implemented this BigList table and query in PostgreSQL 8.3.7, and it gave precisely correct answers to the queries. (Surprisingly precise, actually--I wonder if it uses quadruple-precision sometimes, but I don't know.)
I'll try to upload the BigList table in BZ2 form shortly here. It's certainly my personal record for compression efficacy: a 296 MB table compressed to 17KB. :) OF course, it's nothing but the same value about 51M times, created via:
copy select * from biglist INTO '....\\BigList.cpy' USING DELIMITERS ',', '\n' NULL AS ''
I hope I'm right in presuming it'll be easy for others to COPY INTO a table given the above information?
## Comment 11480
Date: 2009-04-13 23:10:18 +0200
From: John Rylander <<johnrylander>>
BTW, I created the uploaded BZ2 file using 7zip "Ultimate" compression with the Bzip2 format--I hope this is not too troublesome. If it is, let me know a better format, and I'll re-upload.
## Comment 11481
Date: 2009-04-14 00:14:48 +0200
From: John Rylander <<johnrylander>>
This is almost unreadable without a fixed-pitch typeface, so I'd suggest cutting and pasting what follows in this message into a text editor--I think the results are fascinating. Population a single-column table with only millions of instance of the number 1.21, one can see a pattern in the increasingly large scale aggregation. (The correct/ideal result in each case of the AVG(SQRT(RT)) is exactly 1.1, of course.)
Copied from an mclient session:
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L4 |
+========================+
| 1.0220502 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L7 |
+========================+
| 1.1831894000000001 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L12 |
+========================+
| 1.1184810666666667 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L15 |
+========================+
| 0.83886079999999996 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L20 |
+========================+
| 0.67108864000000001 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L23 |
+========================+
| 0.55924053333333335 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L26 |
+========================+
| 0.47934902857142858 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist limit 10000000;
Rows affected 10000000
sql>select avg(sqrt(rt)) from biglist2;
+------------------------+
| L31 |
+========================+
| 0.41943039999999998 |
+------------------------+
1 tuple
sql>select max(rt), min(rt) from biglist2;
+------------------+------------------+
| L34 | L35 |
+==================+==================+
| 1.21 | 1.21 |
+------------------+------------------+
1 tuple
sql>select count(rt) from biglist2;
+----------+
| L36 |
+==========+
| 80000000 |
+----------+
1 tuple
sql>
## Comment 11482
Date: 2009-04-14 00:27:49 +0200
From: John Rylander <<johnrylander>>
More fascinating still. I emptied BigList 2 and refilled and tested it as follows (same cut-and-paste into a fixed-pitch editor for this, too):
sql>insert into biglist2 select rt from biglist limit 10;
Rows affected 10
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1000000953674316 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 10
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1000001907348633 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 20
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0999998092651366 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 40
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0999991416931152 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 80
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1000008583068848 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 160
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.100003433227539 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 320
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0999964714050292 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 640
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0999860763549805 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 1280
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1000141143798827 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 2560
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1000558853149414 |
+------------------------+
1 tuple
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1000558853149414 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 5120
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0999435424804687 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 10240
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0997764587402343 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 20480
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1002252578735352 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 40960
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1008938789367675 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 81920
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0990918159484864 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 163840
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0964209556579589 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 327680
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1035164833068847 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 655360
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.1142581939697265 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 1310720
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0841147422790527 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 2621440
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.0420574188232421 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 5242880
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.021028709411621 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 10485760
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 1.221028709411621 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 20971520
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 0.80000000000000004 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 41943040
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 0.40000000000000002 |
+------------------------+
1 tuple
sql>insert into biglist2 select rt from biglist2;
Rows affected 83886080
sql>select avg(sqrt(rt)) as avg from biglist2;
+------------------------+
| avg |
+========================+
| 0.20000000000000001 |
+------------------------+
1 tuple
sql>
## Comment 11483
Date: 2009-04-14 08:19:16 +0200
From: @drstmane
With the Feb2009 CVS release branch version of Sat Arp 11 2009, i.e.,
$ mserver5 --version
MonetDB server v5.10.3 (64-bit), based on kernel v1.28.3 (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/manegold/_/scratch0/Monet/Testing/Stable/prefix.--enable-strict_--disable-optimize_--enable-debug_--enable-assert
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.3 (compiled with 2.7.3)
Compiled by: manegold@rig.ins.cwi.nl
Compilation: gcc -Wall -Wextra -std=c99 -g -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2
Linking : ld -IPA -m elf_x86_64
and the attached 1.21.zip (~700 KB; expands to ~500 MB; contains 100000000x "1.21"),
I get the following on my 64-bit Linux machine:
create table n1 (a numeric(14,2));
create table n8 (a numeric(14,2));
create table d1 (a double);
create table d8 (a double);
copy 10 records into n1 from '/tmp/1.21';
[ 10 ]
copy 10 records into d1 from '/tmp/1.21';
[ 10 ]
copy 100000000 records into n8 from '/tmp/1.21';
[ 100000000 ]
copy 100000000 records into d8 from '/tmp/1.21';
[ 100000000 ]
select 'count(n1) == 10', count(*), 'avg(n1) == 1.21', avg(a), 'avg(sqrt(n1)) == 1.1', avg(sqrt(a)) from n1;
% .L15, sys.n1, ., sys., ., sys. table_name
% L15, L16, single_value, scale_down_L17, single_value, L20 name
% char, wrd, char, double, char, double type
% 15, 2, 15, 22, 20, 22 length
[ "count(n1) == 10", 10, "avg(n1) == 1.21", 1.21, "avg(sqrt(n1)) == 1.1", 1.1000000238418579 ]
select 'count(d1) == 10', count(*), 'avg(d1) == 1.21', avg(a), 'avg(sqrt(d1)) == 1.1', avg(sqrt(a)) from d1;
% .L21, sys.d1, ., sys., ., sys. table_name
% L21, L22, single_value, L23, single_value, L24 name
% char, wrd, char, double, char, double type
% 15, 2, 15, 22, 20, 22 length
[ "count(d1) == 10", 10, "avg(d1) == 1.21", 1.2100000000000002, "avg(sqrt(d1)) == 1.1", 1.0999999999999999 ]
select 'avg(sqrt(n1)) == 1.1', avg(sqrt(a)) from n1;
% .L165, sys. table_name
% L165, L166 name
% char, double type
% 20, 22 length
[ "avg(sqrt(n1)) == 1.1", 1.1000000953674316 ]
select 'avg(sqrt(d1)) == 1.1', avg(sqrt(a)) from d1;
% .L171, sys. table_name
% L171, L172 name
% char, double type
% 20, 22 length
[ "avg(sqrt(d1)) == 1.1", 1.0999999999999999 ]
select 'count(n8) == 100000000', count(*), 'avg(n8) == 1.21', avg(a), 'avg(sqrt(n8)) == 1.1', avg(sqrt(a)) from n8;
% .L141, sys.n8, ., sys., ., sys. table_name
% L141, L142, single_value, scale_down_L143, single_value, L144 name
% char, wrd, char, double, char, double type
% 22, 9, 15, 22, 20, 22 length
[ "count(n8) == 100000000", 100000000, "avg(n8) == 1.21", 1.21, "avg(sqrt(n8)) == 1.1", 1.1000000238418579 ]
select 'count(d8) == 100000000', count(*), 'avg(d8) == 1.21', avg(a), 'avg(sqrt(d8)) == 1.1', avg(sqrt(a)) from d8;
% .L145, sys.d8, ., sys., ., sys. table_name
% L145, L146, single_value, L147, single_value, L150 name
% char, wrd, char, double, char, double type
% 22, 9, 15, 22, 20, 22 length
[ "count(d8) == 100000000", 100000000, "avg(d8) == 1.21", 1.2099999975113553, "avg(sqrt(d8)) == 1.1", 1.0999999983176105 ]
select 'avg(sqrt(n8)) == 1.1', avg(sqrt(a)) from n8;
% .L255, sys. table_name
% L255, L256 name
% char, double type
% 20, 22 length
[ "avg(sqrt(n8)) == 1.1", 0.33554432000000001 ]
select 'avg(sqrt(d8)) == 1.1', avg(sqrt(a)) from d8;
% .L261, sys. table_name
% L261, L262 name
% char, double type
% 20, 22 length
[ "avg(sqrt(d8)) == 1.1", 1.0999999983176105 ]
I.e., a significant rounding(?) error occurs with 100000000 tuples (only) with type numeric(14,2) and query
select 'avg(sqrt(n8)) == 1.1', avg(sqrt(a)) from n8;
but not with query
select 'count(n8) == 100000000', count(*), 'avg(n8) == 1.21', avg(a), 'avg(sqrt(n8)) == 1.1', avg(sqrt(a)) from n8;
and not with type double with either of the queries.
See attached sqrt.sql & sql.Feb2009.-n1.out for more details.
## Comment 11484
Date: 2009-04-14 08:25:16 +0200
From: @drstmane
Could not attach the ~700KB 1.21.zip, but you can download is from
http://homepages.cwi.nl/~manegold/Public/1.21.zip
(or simply create it yourself).
## Comment 11485
Date: 2009-04-15 12:52:38 +0200
From: John Rylander <<johnrylander>>
More strangeness, but hopefully revealing.
THis is the first stuff I tried in MonetDB this morning. Using the same version of MonetDB (stable release for Vista x64) and data format (numeric 14,2) as in the original bug report note, I tried converting my 167772160 "biglist2" table to single/real (32-bit floating point) precision, to see if that helped. (Stmane's fascinating results suggested that it might--in his Linux developer's build, aggregating on a double precision field show no issues, so maybe the problem was _only_ with NUMERIC/DECIMAL types, under some circumstanes.)
sql>create table big_s (rt real);
0 tuples
sql>insert into big_s select * from biglist2;
Rows affected 167772160
sql>select avg(rt) from big_s;
+------------------------+
| L1 |
+========================+
| 0.20000000000000001 |
+------------------------+
1 tuple
sql>select avg(rt), min(rt), max(rt) from big_s;
+------------------------+---------------+---------------+
| L4 | L5 | L6 |
+========================+===============+===============+
| 0.20000000000000001 | 1.21000004 | 1.21000004 |
+------------------------+---------------+---------------+
1 tuple
sql>select avg(rt), avg(sqrt(rt)), min(rt), max(rt) from big_s;
+----------------------+----------------------+---------------+---------------+
| L11 | L12 | L13 | L14 |
+======================+======================+===============+===============+
| 0.20000000000000001 | 0.20000000000000001 | 1.21000004 | 1.21000004 |
+----------------------+----------------------+---------------+---------------+
1 tuple
sql>
So the problem persists, perhaps even worse, with REAL precision as well as NUMERIC/DECIMAL. Just to be thorough, I tried a quick test of DOUBLE, as per Stmane's tests:
sql>create table big_d (rt double);
0 tuples
sql>insert into big_d select * from biglist2;
Rows affected 167772160
sql>select avg(rt) from big_d;
+------------------------+
| L21 |
+========================+
| 1.21000000091728 |
+------------------------+
1 tuple
sql>select avg(rt), min(rt), max(rt) from big_d;
+------------------------+------------------------+------------------------+
| L24 | L25 | L26 |
+========================+========================+========================+
| 1.21000000091728 | 1.21 | 1.21 |
+------------------------+------------------------+------------------------+
1 tuple
sql>select avg(rt), avg(sqrt(rt)), min(rt), max(rt) from big_d;
+------------------+------------------+-------------------+-------------------+
| L31 | L32 | L33 | L34 |
+==================+==================+===================+===================+
| 1.21000000091728 | 1.09999999658946 | 1.21 | 1.21 |
: : 69 : : :
+------------------+------------------+-------------------+-------------------+
1 tuple
Bottom line: no problems with DOUBLE--serious problems with REAL and NUMERIC/DECIMAL with large numbers of records, in these tests, anyway.
I'd think it has to be significant that the results of the averaging are halved every time I double the quantity of records past a certain point (see my previous comment).... And the nearly precise results (.8, then .4, then .2) may correlate with the number of records each time (41943040, 83886080, and finally 167772160).
## Comment 11486
Date: 2009-04-15 13:54:22 +0200
From: @sjoerdmullender
The problem is with the way the sum is done.
In order to calculate the result, the square root is calculated of each row (yielding the closest to 1.1 you can put into a C float, i.e. 1.10000002), and then the sum of the resulting column is calculated (and then of course, this sum is divided by the count).
The sum of a column of floats (flt internally) is calculated in a flt. And there is the problem.
I created a table with 2**19 rows, each with a single value of 1.21 (in a decimal(14,2)) and did the sum(avg()). The sum of the square roots was 575744.562, however, it should have been 576716.8. The difference is 972.238.
I can reproduce this exactly using a very simple C program:
float r = 0;
float s = sqrt(1.21);
int i;
for (i = 0; i < 524288; i++)
r += s;
printf("s = %f; r = %f (%f %f)\n", s, r, 524288*1.1, 524288*1.1 - r);
If I change the type of r above to double, the problem disappears.
I saw that the sum is done using the ALGsum_flt_flt implementation. Presumably if it were done with ALGsum_flt_dbl there would not be a problem.
## Comment 11487
Date: 2009-04-15 15:06:53 +0200
From: John Rylander <<johnrylander>>
Good catch, sjoerd. That explains everything nicely. (Presumably the same thing would happen with Double Precision eventually, but that would take so many records as to not be worth worrying about, right?)
## Comment 11488
Date: 2009-04-15 15:19:58 +0200
From: John Rylander <<johnrylander>>
BTW, should I presume that there will be no corrected Windows binaries available until the next stable release? Not quite techie enough to do my own compiles, I must confess. :[
## Comment 11489
Date: 2009-04-18 13:57:07 +0200
From: @drstmane
added test in
sql/src/test/BugTracker-2009/Tests/AVG_of_SQRT.SF-2757642.{unpack_csv,test}.*
(Feb2009 release branch)
Appears to work fine after Niels's fix to internally use type double as early as possible to avoid rounding/precision errors.
## Comment 11490
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2757642 at http://sourceforge.net/support/tracker.php?aid=2757642
| Inaccurate AVG of SQRT with 51M records | https://api.github.com/repos/MonetDB/MonetDB/issues/2040/comments | 0 | 2020-11-30T10:18:08Z | 2024-06-27T11:39:06Z | https://github.com/MonetDB/MonetDB/issues/2040 | 753,346,790 | 2,040 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-13 02:05:28 +0200
From: @peterboncz
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-04-14 10:07:47 +0200
## Comment 11472
Date: 2009-04-13 02:05:28 +0200
From: @peterboncz
Mtest runtime/xrpc/admin/add_del_doc crashes in pf cse..
(gdb) r
Starting program: /home/users/boncz/monet-gcc-DBGXPROF-64/bin/Mserver --config=/home/users/boncz/monet/etc/MonetDB.conf --debug=10 --set gdk_nr_threads=1 --set monet_mod_path=/home/users/boncz/monet/lib/MonetDB4:/home/users/boncz/monet/lib/MonetDB4/lib:/home/users/boncz/monet/lib/MonetDB4/bin --set gdk_dbfarm=/home/users/boncz/monet/var/MonetDB4/dbfarm --set xquery_logdir=xquery_logs --set mapi_open=true --set xrpc_open=true --set mapi_port=37159 --set xrpc_port=49991 --set monet_prompt= --trace --dbname=mTests_runtime_xrpc_admin --dbinit=\ module\(pathfinder\)\; /home/users/boncz/monet-gcc-DBGXPROF-64/mTests/runtime/xrpc/admin/add_del_doc.prologue
[Thread debugging using libthread_db enabled] [New Thread 0x7ffff5df47b0 (LWP 3075)] [New Thread 0x7fffeb90e950 (LWP 3086)] MonetDB Server v4.29.0
based on GDK v1.29.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
[New Thread 0x7fffe5ec4950 (LWP 3087)]
MonetDB/XQuery module v0.29.0 loaded (default back-end is 'algebra') XRPC administrative console at http://127.0.0.1:49991/admin [New Thread 0x7fffe4a63950 (LWP 3088)] [New Thread 0x7fffe4862950 (LWP 3089)] [New Thread 0x7fffe445f950 (LWP 3092)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe445f950 (LWP 3092)] 0x00007fffe733ca6d in la_cse (n=0x7fffdb2d14b0) at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2674
2674 for (unsigned int i = 0; i < temp->schema.count; i++) {
Missing separate debuginfos, use: debuginfo-install e2fsprogs-libs-1.41.4-4.fc10.x86_64 glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.78-1.fc10.x86_64 libxml2-2.7.3-1.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64 pcre-7.8-1.fc10.x86_64 zlib-1.2.3-18.fc9.x86_64
(gdb) bt
0 0x00007fffe733ca6d in la_cse (n=0x7fffdb2d14b0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2674
1 0x00007fffe733c867 in la_cse (n=0x7fffdb2d1630)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
2 0x00007fffe733c867 in la_cse (n=0x7fffdb2d1e40)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
3 0x00007fffe733c867 in la_cse (n=0x7fffdb2d1ff0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
4 0x00007fffe733c867 in la_cse (n=0x7fffdb2d2190)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
5 0x00007fffe733c867 in la_cse (n=0x7fffdb2d2d40)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
6 0x00007fffe733c867 in la_cse (n=0x7fffdb2d3080)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
7 0x00007fffe733c867 in la_cse (n=0x7fffdb2d3280)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
8 0x00007fffe733c867 in la_cse (n=0x7fffdb2d35e0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
9 0x00007fffe733c867 in la_cse (n=0x7fffdb2d39e0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
10 0x00007fffe733c867 in la_cse (n=0x7fffdb2d3b80)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
11 0x00007fffe733c867 in la_cse (n=0x7fffdb2d3d20)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
12 0x00007fffe733c867 in la_cse (n=0x7fffdb2d3ed0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
13 0x00007fffe733c867 in la_cse (n=0x7fffdb2d4070)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
14 0x00007fffe733c867 in la_cse (n=0x7fffdb2d4200)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
15 0x00007fffe733c867 in la_cse (n=0x7fffdb2d6e00)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
16 0x00007fffe733c867 in la_cse (n=0x7fffdb2d9a00)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
17 0x00007fffe733c867 in la_cse (n=0x7fffdb2dc600)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
18 0x00007fffe733c867 in la_cse (n=0x7fffdb2df200)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
19 0x00007fffe733c867 in la_cse (n=0x7fffdb2e2820)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
20 0x00007fffe733c867 in la_cse (n=0x7fffdb2e5420)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
21 0x00007fffe733c867 in la_cse (n=0x7fffdb2e8020)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
---Type <return> to continue, or q <return> to quit---
22 0x00007fffe733c867 in la_cse (n=0x7fffdb2eb9f0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
23 0x00007fffe733c867 in la_cse (n=0x7fffdb2ee5f0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
24 0x00007fffe733c867 in la_cse (n=0x7fffdb2f11f0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
25 0x00007fffe733c867 in la_cse (n=0x7fffdb332c30)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
26 0x00007fffe733c867 in la_cse (n=0x7fffdb336dc0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2637
27 0x00007fffe733cc66 in PFalgopt_cse (root=0x7fffdb336dc0)
at /home/users/boncz/src/pathfinder/compiler/algebra/opt/opt_algebra_cse.c:2751
28 0x00007fffe72b4eb6 in PFalgopt (root=0x7fffdb336dc0, timing=false, guide_list=0x0,
opt_args=0x7fffe73f9827 "ECSVR_OK_N}MT{JISI_GECSVR_}MT{JISI_OK_GECSVR_DC_GYP")
at /home/users/boncz/src/pathfinder/compiler/algebra/algopt.c:202
29 0x00007fffe723523d in PFcompile_MonetDB (
xquery=0x7fffe6499ec9 "import module namespace adm = \"http://monetdb.cwi.nl/XQuery/admin/\"\n", ' ' <repeats 24 times>, "at \"http://tscan:49991/admin/admin.xq\";\n(\ntext { \"
\"},\n<collections-after-add>{\n for $c in execute "...,
url=0x7fffe6499ec9 "import module namespace adm = \"http://monetdb.cwi.nl/XQuery/admin/\"\n", ' ' <repeats 24 times>, "at \"http://tscan:49991/admin/admin.xq\";\n(\ntext { \"
\"},\n<collections-after-add>{\n for $c in execute "...,
prologue=0x7fffe445e260, query=0x7fffe445dec8, epilogue=0x7fffe445e250, options=2, genType=0x7fffe66556c8 "mapi-xml")
at /home/users/boncz/src/pathfinder/compiler/compile.c:970
30 0x00007fffe722c0e4 in xquery_compile_exec (ctx=0x7fffe64e2078, options=2,
xquery=0x7fffe6499ec9 "import module namespace adm = \"http://monetdb.cwi.nl/XQuery/admin/\"\n", ' ' <repeats 24 times>, "at \"http://tscan:49991/admin/admin.xq\";\n(\ntext { \"
\"},\n<collections-after-add>{\n for $c in execute "..., is_url=0,
prologue=0x7fffe445e260, query=0x7fffe445e258, epilogue=0x7fffe445e250, module=0x0)
at /home/users/boncz/src/pathfinder/runtime/pathfinder.mx:4654
31 0x00007fffe723231e in xquery_prepare (ctx=0x7fffe64e2078, usec=37910405,
query=0x7fffe6499ec9 "import module namespace adm = \"http://monetdb.cwi.nl/XQuery/admin/\"\n", ' ' <repeats 24 times>, "at \"http://tscan:49991/admin/admin.xq\";\n(\ntext { \"
\"},\n<collections-after-add>{\n for $c in execute "...)
at /home/users/boncz/src/pathfinder/runtime/pathfinder.mx:6052
32 0x00007fffe7232948 in xquery_client_engine (mc=0x7fffe71c5188) at /home/users/boncz/src/pathfinder/runtime/pathfinder.mx:6207
33 0x00007fffe6fc080b in mapi_client_engine (FC=0x7fffe71c5188) at /home/users/boncz/src/MonetDB4/src/mapi/mapi.mx:502
34 0x00000039b50073da in start_thread () from /lib64/libpthread.so.0
35 0x00000039b44e62bd in clone () from /lib64/libc.so.6
(gdb)
## Comment 11473
Date: 2009-04-14 22:07:47 +0200
From: Jan Rittinger <<jan.rittinger>>
Fixed in CVS.
(Fix doesn't need to be propagated to stable branch as problem only occurs for XRPC queries not yet working in the algebra version of Feb2009 release.)
## Comment 11474
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2757113 at http://sourceforge.net/support/tracker.php?aid=2757113
| crash in la_cse | https://api.github.com/repos/MonetDB/MonetDB/issues/2039/comments | 0 | 2020-11-30T10:18:05Z | 2024-06-27T11:39:05Z | https://github.com/MonetDB/MonetDB/issues/2039 | 753,346,746 | 2,039 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-13 02:04:14 +0200
From: @peterboncz
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
CC: @sjoerdmullender
Last updated: 2010-07-09 16:30:56 +0200
## Comment 11466
Date: 2009-04-13 02:04:14 +0200
From: @peterboncz
many MTest benchmarks/XBench queries, among which for instance benchmarks/XBench/DC/SD/q10.xq
fail due to timeout.
It appears many queries now take ages to compile, with the routine 'plan_subexpression' being called in a very deep stack.
Is there a bug in the optimization algorithm, or has physical optimization by now become so ambitious we need a mechanism in the pf compiler to keep the search sapce under control (or stop searching after a time or effort limit).
## Comment 11467
Date: 2009-04-14 11:45:00 +0200
From: Jan Rittinger <<jan.rittinger>>
The physical plan generator was never designed to be especially intelligent. It (stupidly) enumerates all possible plans. In the past I tried to add some short-cuts to avoid too bad compilation performance.
With the recent optimization a lot of the ordering constraints, that forced the plan space to stay small, were moved out of the way. Furthermore the optimization option Y made the schemas of the operators much wider. Mainly the latter change causes routine better_or_equal() to run into serious performance problems as e.g., for query benchmarks/XBench/DC/SD/q10.xq two plans are compared with 2061256 and 1374170 different orderings!!
I would guess that the problem becomes less dramatic again with the MonetDB specific optimizations in place that restrict the schema width (see also http://sourceforge.net/support/tracker.php?aid=2757104).
## Comment 11468
Date: 2009-08-06 16:36:45 +0200
From: @mlkersten
It seems this has to wait for future improved versions.
## Comment 11469
Date: 2009-08-11 11:52:38 +0200
From: @drstmane
According to our TestWeb, no timeouts occur with any of the pathfinder/benchmark/XBench tests (anymore):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/index.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/index.html
## Comment 11470
Date: 2009-08-14 13:58:08 +0200
From: @drstmane
tagged subject
## Comment 11471
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2757110 at http://sourceforge.net/support/tracker.php?aid=2757110
## Comment 14346
Date: 2010-07-09 16:30:56 +0200
From: @sjoerdmullender
This doesn't seem to be an issue anymore.
| PF: plan_subexpression slow | https://api.github.com/repos/MonetDB/MonetDB/issues/2038/comments | 0 | 2020-11-30T10:18:02Z | 2024-06-28T07:37:11Z | https://github.com/MonetDB/MonetDB/issues/2038 | 753,346,702 | 2,038 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-13 02:01:21 +0200
From: @peterboncz
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2009-09-07 11:52:56 +0200
## Comment 11460
Date: 2009-04-13 02:01:21 +0200
From: @peterboncz
XIRAF test queries 5 and 8 fail now
http://wiki.pathfinder-xquery.org/wiki/index.php/XIRAF_testdata
this can be circumvented by disabling a compile option (Y) in compile.c and recompiling, but should be fixed.
bug report just as a reminder (can't we at least switch off Y by default though??)
## Comment 11461
Date: 2009-04-13 10:56:28 +0200
From: Jan Rittinger <<jan.rittinger>>
In both example queries I can see no mistake. Option Y only provides plans that the physical planner has problems with---the staircase join algorithms are (unnecessarily) called with unique iter values.
The solution (hopefully) will come soon: a MonetDB specific optimization that hides part of the job of optimization Y.
## Comment 11462
Date: 2009-04-13 11:35:42 +0200
From: @drstmane
FYI:
7 of the Xiraf test fail wit the CVS development trunk due to a BAT propcheck error:
ID: 2668437 "PF runtime: parent step produces not/wrongly sorted result"
(https://sourceforge.net/tracker/?func=detail&aid=2668437&group_id=56967&atid=482468)
(cf.,
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/index_short.html
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/Int.64.32.d.1-Fedora8/large-testset/q525.out.00.html
...
http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/GNU.64.64.d.1-Fedora8/large-testset/q538.out.00.html
)
With the Feb2009 release branch, the Xiraf queries work fine,
since I avoided the above mentioned BATprocheck error there (only);
(Cf.,
http://monetdb.cwi.nl/testing/intern/monetdb/Stable/_intern_/Xiraf/.mTests103/index_short.html
)
(ps: Xiraf testing result can only be accessed from within CWI, or with CWI intraweb access)
## Comment 11463
Date: 2009-09-07 23:39:25 +0200
From: Jan Rittinger <<jan.rittinger>>
Stefan,
do the tests work now?
## Comment 11464
Date: 2009-09-07 23:52:53 +0200
From: @drstmane
Jan,
thanks for the reminder.
yes, all Xiraf tests seem to work fine now
(except from a (minor?) timeout with test q569 on slow systems, but that is not related to this bug report).
Closing.
## Comment 11465
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2757104 at http://sourceforge.net/support/tracker.php?aid=2757104
| xiraf and other test queries fail (Y option) | https://api.github.com/repos/MonetDB/MonetDB/issues/2037/comments | 0 | 2020-11-30T10:17:58Z | 2024-06-28T07:37:10Z | https://github.com/MonetDB/MonetDB/issues/2037 | 753,346,664 | 2,037 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-12 08:55:03 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-04-13 08:49:17 +0200
## Comment 11457
Date: 2009-04-12 20:55:03 +0200
From: @skinkie
bash-3.2$ /export/scratch1/konink/monetdb-head/bin/stethoscope -p 50005
stethoscope [options] +[Ttcmipesrwd] {<mod>.<fcn>}
-d | --dbname=<database_name>
-u | --user=<user>
-P | --password=<password>
-p | --port=<portnr>
-h | --host=<hostname>
-g | --gnuplot
The trace options:
a =aggregates
e =event
f =function
o =operation called
T =time
t =ticks
c =cpu statistics
m =memory resources
i =io resources
b =bytes read/written
d =diskspace needed
s =statement
p =pg faults, cntxt switches
vs
bash-3.2$ /export/scratch1/konink/monetdb-head/bin/stethoscope --port=50005
connection with server for '(null)' established
ready to receive events
## Comment 11458
Date: 2009-04-13 08:49:17 +0200
From: @mlkersten
fixed the argument handling
## Comment 11459
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2756553 at http://sourceforge.net/support/tracker.php?aid=2756553
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.
| stethoscope -p parameter doesn't work | https://api.github.com/repos/MonetDB/MonetDB/issues/2036/comments | 0 | 2020-11-30T10:17:55Z | 2024-06-27T11:39:02Z | https://github.com/MonetDB/MonetDB/issues/2036 | 753,346,626 | 2,036 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-11 09:16:26 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-15 12:56:45 +0200
## Comment 11454
Date: 2009-04-11 09:16:26 +0200
From: @drstmane
Most probably due to the reduced error buffer size (1K instead of 10k), test
MonetDB4/tests/BugDay_2005-11-09_4.9.3/Tests/variable_nesting.SF-1027421.milC
now produces different output, i.e., cropped error messages;
in case this turns out to be to only such case,
we could consider approving this output;
otherwise, we could consider increasing the error buffer to, say, 2k.
?
## Comment 11455
Date: 2009-04-15 12:56:45 +0200
From: @sjoerdmullender
I increased the error buffer size to 1.5 KB and that seems to have done the trick.
## Comment 11456
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2752158 at http://sourceforge.net/support/tracker.php?aid=2752158
| M4: test output differs due to reduced error buffer size | https://api.github.com/repos/MonetDB/MonetDB/issues/2035/comments | 0 | 2020-11-30T10:17:51Z | 2024-06-27T11:39:01Z | https://github.com/MonetDB/MonetDB/issues/2035 | 753,346,567 | 2,035 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-09 03:18:39 +0200
From: Wouter Alink <<alink>>
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-04-28 12:54:11 +0200
## Comment 11448
Date: 2009-04-09 15:18:39 +0200
From: Wouter Alink <<alink>>
When stopping a MonetDB instance with merovingian (using "monetdb stop <dbname>"), it does not wait for the server to actually shutdown. This is very annoying, as you never know when the port becomes available again.
## Comment 11449
Date: 2009-04-09 21:51:17 +0200
From: @grobian
I concur this is an inconsistency regarding the behaviour of start, and implemented this.
## Comment 11450
Date: 2009-04-21 10:25:06 +0200
From: @sjoerdmullender
This bug is back since I reverted the changes.
I reverted the changes because they caused a worse situation on Linux in that "monetdb stop" would hang the server (instead of stopping it).
## Comment 11451
Date: 2009-04-21 14:22:44 +0200
From: @grobian
This has now been properly (?) fixed. monetdb stop now waits until the server is shut down, without locking merovingian.
## Comment 11452
Date: 2009-04-28 12:54:11 +0200
From: @grobian
Fixed released in Feb2009-SP2
## Comment 11453
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2747661 at http://sourceforge.net/support/tracker.php?aid=2747661
| Merovingian: wait for stopping MonetDB | https://api.github.com/repos/MonetDB/MonetDB/issues/2034/comments | 0 | 2020-11-30T10:17:47Z | 2024-06-27T11:39:00Z | https://github.com/MonetDB/MonetDB/issues/2034 | 753,346,520 | 2,034 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-07 11:10:05 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-08-16 04:20:33 +0200
## Comment 11442
Date: 2009-04-07 23:10:05 +0200
From: @skinkie
create table blabla(id integer);
explain alter table blabla add constraint dada unique (id);
explain alter table blabla add constraint dada unique (id);
!CONSTRAINT PRIMARY KEY: key dada already exists
alter table blabla drop constraint dada;
explain alter table blabla add constraint dada unique (id);
[Switching to Thread 0x7fffe1cd8950 (LWP 1752)]
0x00007fffe27ad4e6 in update_check_ukey (sql=0x128f9f8, updates=0x135b5b8, k=0x132bd98, idx_updates=0x0, updcol=0) at ../../../src/server/rel_bin.mx:2474
2474 sql_kc *c = k->columns->h->data;
Missing separate debuginfos, use: debuginfo-install bzip2-libs-1.0.5-3.fc10.x86_64 e2fsprogs-libs-1.41.4-4.fc10.x86_64 glibc-2.9-3.x86_64 keyutils-libs-1.2-3.fc9.x86_64 krb5-libs-1.6.3-16.fc10.x86_64 libselinux-2.0.78-1.fc10.x86_64 ncurses-libs-5.6-20.20080927.fc10.x86_64 openssl-0.9.8g-12.fc10.x86_64 pcre-7.8-1.fc10.x86_64 readline-5.2-13.fc9.x86_64 zlib-1.2.3-18.fc9.x86_64
(gdb) bt
0 0x00007fffe27ad4e6 in update_check_ukey (sql=0x128f9f8, updates=0x135b5b8, k=0x132bd98, idx_updates=0x0, updcol=0)
at ../../../src/server/rel_bin.mx:2474
1 0x00007fffe27ae765 in sql_update_check_key (sql=0x128f9f8, updates=0x135b5b8, k=0x132bd98, idx_updates=0x0, updcol=0, l=0x1315a58, cascade=0x134f518)
at ../../../src/server/rel_bin.mx:2767
2 0x00007fffe27af073 in update_idxs_and_check_keys (sql=0x128f9f8, t=0x12d5a98, updates=0x135b5b8, l=0x1315a58, cascades=0x7fffe1cd7730)
at ../../../src/server/rel_bin.mx:2944
3 0x00007fffe27af4c6 in sql_update (sql=0x128f9f8, t=0x12d5a98, updates=0x135b5b8) at ../../../src/server/rel_bin.mx:3034
4 0x00007fffe27af7e0 in rel2bin_update (sql=0x128f9f8, rel=0x134f388, refs=0x135b0f8) at ../../../src/server/rel_bin.mx:3096
5 0x00007fffe27b03eb in subrel_bin (sql=0x128f9f8, rel=0x134f388, refs=0x135b0f8) at ../../../src/server/rel_bin.mx:3368
6 0x00007fffe27b0499 in rel_bin (sql=0x128f9f8, rel=0x134f388) at ../../../src/server/rel_bin.mx:3388
7 0x00007fffe2758de2 in sql_update_add_idx (sql=0x128f9f8, t=0x12d5a98, idx=0x132bd98) at ../../../src/server/sql_schema.mx:1010
8 0x00007fffe275a4e7 in table_constraint_type (sql=0x128f9f8, name=0x1291bc8 "dada", s=0x1291c38, ss=0x1263ab8, t=0x12d5a98, alter=1)
at ../../../src/server/sql_schema.mx:1477
9 0x00007fffe275a645 in table_constraint (sql=0x128f9f8, s=0x1291cd8, ss=0x1263ab8, t=0x12d5a98, alter=1) at ../../../src/server/sql_schema.mx:1508
10 0x00007fffe275a89d in table_element (sql=0x128f9f8, s=0x1291cd8, ss=0x1263ab8, t=0x12d5a98, alter=1) at ../../../src/server/sql_schema.mx:1556
11 0x00007fffe275bcc5 in alter_table (sql=0x128f9f8, qname=0x1291b78, te=0x1291cd8) at ../../../src/server/sql_schema.mx:1872
12 0x00007fffe275c95d in schemas (sql=0x128f9f8, s=0x1291d78) at ../../../src/server/sql_schema.mx:2109
13 0x00007fffe2762190 in semantic (sql=0x128f9f8, s=0x1291d78) at ../../../src/server/sql_semantic.mx:1032
14 0x00007fffe27622c5 in output_semantic (sql=0x128f9f8, s=0x1291d78) at ../../../src/server/sql_semantic.mx:1094
15 0x00007fffe26fe2ce in sql_symbol2stmt (c=0x128f9f8, sym=0x1291d78) at ../../../../src/backends/monet5/sql.mx:1095
16 0x00007fffe2739ebd in SQLparser (c=0x604a68) at ../../../../src/backends/monet5/sql_scenario.mx:1019
17 0x00007ffff7d32d79 in runPhase (c=0x604a68, phase=1) at ../../../src/mal/mal_scenario.mx:591
18 0x00007ffff7d32e76 in runScenarioBody (c=0x604a68) at ../../../src/mal/mal_scenario.mx:627
19 0x00007ffff7d330a9 in runScenario (c=0x604a68) at ../../../src/mal/mal_scenario.mx:661
20 0x00007ffff7cef8bd in MSserveClient (dummy=0x604a68) at ../../../src/mal/mal_session.mx:460
21 0x00007ffff7773e36 in wrapper_routine (data=0x7fffe325dbe0) at ../../../src/gdk/gdk_posix.mx:955
22 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
23 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
## Comment 11443
Date: 2009-05-28 22:42:34 +0200
From: @njnes
solved simply by disabling (again) explain and friends in schema statements (as these are executed directly). test added to explain_gives_crash.SF-2741829.sql
## Comment 11444
Date: 2009-08-13 19:35:08 +0200
From: @drstmane
re-opened since the test produces different output since checkins on
2009/07/25 and/or 2009/07/26 on the CVS HEAD;
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/explain_gives_crash.SF-2741829.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.64.64.d.1-Fedora10/src_test_BugTracker-2009/explain_gives_crash.SF-2741829.err.00.html
## Comment 11445
Date: 2009-08-14 14:03:46 +0200
From: @drstmane
tagged subject
## Comment 11446
Date: 2009-08-16 16:20:33 +0200
From: @njnes
somehow the fix got reverted
## Comment 11447
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2741829 at http://sourceforge.net/support/tracker.php?aid=2741829
| SQL: explain alter table add constraint results into badness | https://api.github.com/repos/MonetDB/MonetDB/issues/2033/comments | 0 | 2020-11-30T10:17:44Z | 2024-06-27T11:38:59Z | https://github.com/MonetDB/MonetDB/issues/2033 | 753,346,491 | 2,033 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-06 05:58:02 +0200
From: Vasco Visser <<vascovisser>>
To: @mlkersten
Version: -- development
Last updated: 2009-06-07 05:33:45 +0200
## Comment 11437
Date: 2009-04-06 17:58:02 +0200
From: Vasco Visser <<vascovisser>>
The RAND fuction is only executed every row when _not_ using the ALIAS, I think should also be executed for every row when an alias is used
Test:
create table nr (nr int);
insert into nr values (1);
insert into nr values (2);
insert into nr values (3);
insert into nr values (4);
insert into nr values (5);
insert into nr values (6);
insert into nr values (7);
insert into nr values (8);
insert into nr values (9);
insert into nr values (10);
SELECT nr, RAND() FROM nr;
SELECT nr, RAND() AS rnd FROM nr;
Output:
sql>SELECT nr, RAND() FROM nr;
+----+-------------------+
| nr | rand_single_value |
+====+===================+
| 1 | 19391021 |
| 2 | 578488884 |
| 3 | 1653577571 |
| 4 | 1840458700 |
| 5 | 73059392 |
| 6 | 1967337715 |
| 7 | 559434993 |
| 8 | 1863488420 |
| 9 | 1819496522 |
| 10 | 2012247873 |
+----+-------------------+
10 tuples
sql>SELECT nr, RAND() AS rnd FROM nr;
+----+------------+
| nr | rnd |
+====+============+
| 1 | 2114458422 |
| 2 | 2114458422 |
| 3 | 2114458422 |
| 4 | 2114458422 |
| 5 | 2114458422 |
| 6 | 2114458422 |
| 7 | 2114458422 |
| 8 | 2114458422 |
| 9 | 2114458422 |
| 10 | 2114458422 |
+----+------------+
10 tuples
## Comment 11438
Date: 2009-06-07 17:33:44 +0200
From: @mlkersten
Seems fixed. Test file added to the suite.
## Comment 11439
Date: 2009-06-07 19:55:52 +0200
From: @drstmane
Where exactly can I find the test?
## Comment 11440
Date: 2009-06-08 10:58:15 +0200
From: @drstmane
For the records:
the test is in
sql/src/test/BugTracker-2009/Tests/random.SF-2737889.*
(CVS HEAD, only; not May2009 release branch)
## Comment 11441
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2737889 at http://sourceforge.net/support/tracker.php?aid=2737889
| rand() is not executed for every row when using alias | https://api.github.com/repos/MonetDB/MonetDB/issues/2032/comments | 0 | 2020-11-30T10:17:41Z | 2024-06-27T11:38:58Z | https://github.com/MonetDB/MonetDB/issues/2032 | 753,346,449 | 2,032 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-06 10:07:51 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-04-06 10:50:55 +0200
## Comment 11434
Date: 2009-04-06 10:07:51 +0200
From: @skinkie
CREATE TEMPORARY TABLE fubar (id integer);
insert into fubar values (1);
Rows affected 1
select * from fubar;
0 tuples
Please advise; it is doubtful that there is no testing on temporary tables.
## Comment 11435
Date: 2009-04-06 10:50:54 +0200
From: @skinkie
The example was in auto-commit, if placed in START TRANSACTION; it is able return values. Thanks Niels for pointing it out.
## Comment 11436
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2736702 at http://sourceforge.net/support/tracker.php?aid=2736702
| Temporary table does not contain anything | https://api.github.com/repos/MonetDB/MonetDB/issues/2031/comments | 0 | 2020-11-30T10:17:38Z | 2024-06-28T07:37:10Z | https://github.com/MonetDB/MonetDB/issues/2031 | 753,346,419 | 2,031 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-05 06:17:08 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-05-13 07:24:49 +0200
## Comment 11430
Date: 2009-04-05 18:17:08 +0200
From: @skinkie
verywrong.sql:
START TRANSACTION;
CREATE TEMPORARY TABLE persistent_temopary (id integer);
blabla;
COMMIT;
verywrong2.sql:
drop table persistent_temopary;
bash-3.2$ /export/scratch1/konink/monetdb-head/bin/mclient -H -lsql -p 50005 < verywrong.sql
MAPI = monetdb@localhost:50005
QUERY = blabla;
ERROR = !syntax error, unexpected IDENT in: "blabla"
MAPI = monetdb@localhost:50005
QUERY = COMMIT;
ERROR = !COMMIT: failed
!ERROR: COMMIT: transaction is aborted, will ROLLBACK instead
bash-3.2$ /export/scratch1/konink/monetdb-head/bin/mclient -H -lsql -p 50005 < verywrong.sql
MAPI = monetdb@localhost:50005
QUERY = CREATE TEMPORARY TABLE persistent_temopary (id integer);
ERROR = !CREATE TABLE: name 'persistent_temopary' already in use
MAPI = monetdb@localhost:50005
QUERY = blabla;
ERROR = !current transaction is aborted (please ROLLBACK)
MAPI = monetdb@localhost:50005
QUERY = COMMIT;
ERROR = !COMMIT: failed
!ERROR: COMMIT: transaction is aborted, will ROLLBACK instead
bash-3.2$ /export/scratch1/konink/monetdb-head/bin/mclient -H -lsql -p 50005 < verywrong2.sql
MAPI = monetdb@localhost:50005
ACTION= read_line
QUERY = drop table persistent_temopary;
ERROR = Connection terminated
>mserver5: ../../../src/storage/store.mx:3071: sys_drop_table: Assertion `rid != -1' failed.
## Comment 11431
Date: 2009-04-25 19:34:51 +0200
From: @drstmane
See also
ID: 2779437 "SQL: Temporary table leftovers"
https://sourceforge.net/tracker/?func=detail&aid=2779437&group_id=56967&atid=482468
## Comment 11432
Date: 2009-05-13 19:24:49 +0200
From: @njnes
Test added to src/test/BugTracker-2009/Tests/temporary_table_leftover.SF-2734713.sql
The reset_schema now correctly removes tables/views created in the the last failed transaction
## Comment 11433
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2734713 at http://sourceforge.net/support/tracker.php?aid=2734713
| Temporary table is semi-persistent when transaction fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2030/comments | 0 | 2020-11-30T10:17:34Z | 2024-06-27T11:38:56Z | https://github.com/MonetDB/MonetDB/issues/2030 | 753,346,377 | 2,030 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-03 11:12:45 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-11-22 10:10:25 +0100
## Comment 11419
Date: 2009-04-03 23:12:45 +0200
From: @skinkie
A very long IN part crashes the mserver5 code; gdb return the 'mcount' issue.
I rewrote the query in 'OR' and that resulted in a 'nice' error message.
QUERY = delete from nodes_legacy where id = 1278
ERROR = !memory exhausted in: "delete from nodes_legacy where id = 1278
! or id = 1279
! or id = 1280
! or id = 1281
...
Never the less, the individual deletes are very slow. I would like to know how I could optimise this problem.
## Comment 11420
Date: 2009-04-05 17:59:07 +0200
From: @skinkie
[Switching to thread 1 (Thread 0x7ffff6a377b0 (LWP 26534))]0 0x0000003c1a40df5b in read () from /lib64/libpthread.so.0
(gdb) where
0 0x0000003c1a40df5b in read () from /lib64/libpthread.so.0
1 0x0000003c22027581 in rl_getc () from /lib64/libreadline.so.5
2 0x0000003c22014ce1 in readline_internal_char () from /lib64/libreadline.so.5
3 0x0000003c220151c5 in readline () from /lib64/libreadline.so.5
4 0x00007ffff7d3c795 in getConsoleInput (prompt=0x613a78 ">", linemode=0, exit_on_error=1) at ../../../src/mal/mal_readline.mx:342
5 0x00007ffff7d3ce4f in readConsole (cntxt=0x604820) at ../../../src/mal/mal_readline.mx:499
6 0x00007ffff7cefaf6 in MALreader (c=0x604820) at ../../../src/mal/mal_session.mx:532
7 0x00007ffff7d32d79 in runPhase (c=0x604820, phase=0) at ../../../src/mal/mal_scenario.mx:591
8 0x00007ffff7d32e1a in runScenarioBody (c=0x604820) at ../../../src/mal/mal_scenario.mx:619
9 0x00007ffff7d330a9 in runScenario (c=0x604820) at ../../../src/mal/mal_scenario.mx:661
10 0x00007ffff7cef8bd in MSserveClient (dummy=0x604820) at ../../../src/mal/mal_session.mx:460
11 0x0000000000402f74 in main (argc=5, av=0x7fffffffe0f8) at ../../../src/tools/mserver5.mx:619
[17:56:38] … [Switching to thread 2 (Thread 0x7fffec551950 (LWP 26543))]0 0x0000003c1a40e851 in nanosleep () from /lib64/libpthread.so.0
(gdb) where
0 0x0000003c1a40e851 in nanosleep () from /lib64/libpthread.so.0
1 0x00007ffff7774b41 in MT_sleep_ms (ms=5000) at ../../../src/gdk/gdk_posix.mx:2090
2 0x00007ffff74ca017 in GDKvmtrim (limit=0x7ffff7aa39b0) at ../../../src/gdk/gdk_utils.mx:1471
3 0x00007ffff7773e36 in wrapper_routine (data=0x7fffffffdb40) at ../../../src/gdk/gdk_posix.mx:955
4 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
5 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
[17:56:47] … (gdb) where
0 0x0000003c19cdeaa2 in select () from /lib64/libc.so.6
1 0x00007fffe593e015 in SERVERlistenThread (Sock=0xd84588) at ../../../../src/modules/mal/mal_mapi.mx:525
2 0x00007ffff7773e36 in wrapper_routine (data=0x7fffffffc4f0) at ../../../src/gdk/gdk_posix.mx:955
3 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
4 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
[17:56:55] … (gdb) where
0 0x0000003c1a40e851 in nanosleep () from /lib64/libpthread.so.0
1 0x00007ffff7774b41 in MT_sleep_ms (ms=30000) at ../../../src/gdk/gdk_posix.mx:2090
2 0x00007fffe27b9f81 in store_manager () at ../../../src/storage/store.mx:1431
3 0x00007fffe277dd1e in mvc_logmanager () at ../../../src/server/sql_mvc.mx:342
4 0x00007ffff7773e36 in wrapper_routine (data=0x7fffe325bb10) at ../../../src/gdk/gdk_posix.mx:955
5 0x0000003c1a4073da in start_thread () from /lib64/libpthread.so.0
6 0x0000003c19ce62bd in clone () from /lib64/libc.so.6
[17:57:55] … [Switching to thread 5 (Thread 0x7fffe1cd8950 (LWP 26558))]0 0x0000003c19cea244 in mcount () from /lib64/libc.so.6
(gdb) where
0 0x0000003c19cea244 in mcount () from /lib64/libc.so.6
1 0x0000000000000000 in ?? ()
## Comment 11421
Date: 2009-04-05 18:13:32 +0200
From: @skinkie
My actual problem is solved using:
START TRANSACTION;
CREATE TEMPORARY TABLE delete_nodes (id integer);
COPY 228089 RECORDS INTO delete_nodes from '/tmp/deletemeuk.sql' USING DELIMITERS ',', '\n', '''';
delete from nodes_legacy where id in (select id from delete_nodes);
DROP TABLE delete_nodes;
COMMIT;
Which finishes in a minute.
## Comment 11422
Date: 2009-05-28 22:53:02 +0200
From: @njnes
do you still have the original query, ie the one with the big 'in' part.
## Comment 11423
Date: 2009-08-06 16:38:53 +0200
From: @mlkersten
Awaiting for the original query.
## Comment 11424
Date: 2009-08-11 02:45:21 +0200
From: @skinkie
create table test (number integer);
insert into test values (1);
(execute attached query)
backtrace:
0 0x00007f84c5e35d07 in free () from /lib/libc.so.6
1 0x00007f84c8020fbb in GDKfree_ (blk=0x666cb58) at ../../../src/gdk/gdk_utils.mx:1156
2 0x00007f84c8021044 in GDKfree (blk=0x666cb58) at ../../../src/gdk/gdk_utils.mx:1165
3 0x00007f84b6e667c9 in exp_destroy (exp=0x666caf8) at ../../../src/server/rel_exp.mx:132
4 0x00007f84b6ea1adb in node_destroy (l=0x666cab8, n=0x666cb98) at ../../../src/common/sql_list.mx:52
5 0x00007f84b6ea1b2f in list_destroy (l=0x666cab8) at ../../../src/common/sql_list.mx:66
6 0x00007f84b6e5192c in rel_destroy_ (rel=0x666ca68) at ../../../src/server/rel_select.mx:107
7 0x00007f84b6e51b50 in rel_destroy (rel=0x666ca68) at ../../../src/server/rel_select.mx:143
8 0x00007f84b6e519cd in rel_destroy_ (rel=0x666cd68) at ../../../src/server/rel_select.mx:114
9 0x00007f84b6e51b50 in rel_destroy (rel=0x666cd68) at ../../../src/server/rel_select.mx:143
10 0x00007f84b6e519cd in rel_destroy_ (rel=0x666d068) at ../../../src/server/rel_select.mx:114
11 0x00007f84b6e51b50 in rel_destroy (rel=0x666d068) at ../../../src/server/rel_select.mx:143
...and on and on.
## Comment 11425
Date: 2009-08-11 11:45:25 +0200
From: @drstmane
Yet another stack overflow due to too deep recursion.
## Comment 11426
Date: 2009-08-11 12:10:20 +0200
From: @skinkie
The original backtrace doesn't look like this at all. So maybe when this is finished it will unveil another bug :-\
## Comment 11427
Date: 2009-08-14 13:52:07 +0200
From: @drstmane
tagged subject
## Comment 11428
Date: 2009-11-22 22:10:25 +0100
From: @njnes
out of memory problem. we are working to improve these cases. Having a test is hard.
## Comment 11429
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2728891 at http://sourceforge.net/support/tracker.php?aid=2728891
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| SQL: where IN (....) crashes mserver5 | https://api.github.com/repos/MonetDB/MonetDB/issues/2029/comments | 0 | 2020-11-30T10:17:31Z | 2024-06-28T07:37:10Z | https://github.com/MonetDB/MonetDB/issues/2029 | 753,346,346 | 2,029 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-03 01:52:43 +0200
From: Wouter Alink <<alink>>
To: MonetDB4 devs <<bugs-monetdb4>>
Version: -- development
Last updated: 2010-04-25 04:20:17 +0200
## Comment 11414
Date: 2009-04-03 13:52:43 +0200
From: Wouter Alink <<alink>>
To scale PF/TIJAH (and also the rest of pathfinder/M4) beyond the magical 31 bit boundary, the count() function needs to return a wrd instead of an int. PF/TIJAH hits the 2G border earlier due to the fact that it counts each word in an XML element, where pathfinder only counts a text element as a single node. In M5 this apparently is designed right from the start. In M4 it seems to be a legacy issue.
A simple analysis showed that in the pathfinder code there are +- 584 occurrences of the 'count()' function (c and MIL invocations). In PF/TIJAH there are +- 155. Most of them seem to be easily to replace. Stefan estimated the change to be a 'weekend's work. A simple replacement function he came up with.
PROC count_wrd(BAT b) : wrd {
return wrd(count(int(b)));
}
It is debatable whether to actually implement this fix, as the M4 code is basically end-of-life, and M5 does not exhibit this bug. A plan needs to be made. To be continued.
## Comment 11415
Date: 2009-04-03 14:28:38 +0200
From: @drstmane
- GDK C function BATcount() does return a BUN, not an int.
- in MIL, we have
COMMAND: count(BAT[any,any]) : int
MODULE: algebra
COMPILED: by adm on Wed Apr 1 23:29:46 2009
Returns the number of elements currently in a BAT.
COMMAND: count(int) : lng
MODULE: bat
COMPILED: by adm on Wed Apr 1 23:29:46 2009
Returns the current size (in number of elements) of a BAT.
- my correct quote was "If you have a weekend, you're welcome to do it [i.e., change the count(BAT[any,any]) to return a wrd instead of and int --- and fix all MIL code that uses count(BAT[any,any]), accordingly --- and for consistency change all MIL function that return or expect a count or index of BUN(s) (thing of grouped counts for aggragation, slice, etc.) likewise]" --- don't know, though, whether a weekend is sufficient to do it all correctly & consistently ...
## Comment 11416
Date: 2009-04-24 16:17:26 +0200
From: Wouter Alink <<alink>>
Short update:
This bug was mainly filed for scalability issues in pf-tijah. Today I went through the pftijah code and changed the code so that it uses count_wrd instead of count. Still awaiting (local) test-results. More news (and perhaps a commit) after the weekend.
## Comment 11417
Date: 2010-04-25 04:20:14 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
---- Original comment by: sf-robot@users.sourceforge.net ----
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 365 days (the time period specified by
the administrator of this Tracker).
## Comment 11418
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2728133 at http://sourceforge.net/support/tracker.php?aid=2728133
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-monetdb4@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| M4: count() returns int | https://api.github.com/repos/MonetDB/MonetDB/issues/2028/comments | 0 | 2020-11-30T10:17:28Z | 2024-06-28T07:37:10Z | https://github.com/MonetDB/MonetDB/issues/2028 | 753,346,307 | 2,028 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-02 09:50:16 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-02 10:44:44 +0200
## Comment 11410
Date: 2009-04-02 09:50:16 +0200
From: @drstmane
After the below changes, Mserver fails to start properly:
$ Mserver
MonetDB Server v4.29.0
based on GDK v1.29.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-2009, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
!ERROR: CMDfind: value not found.
!ERROR: CMDfind: operation failed.
!ERROR: interpret_params: int(param 1): evaluation error.
MonetDB>
===================================================================
2009/04/01 - sjoerd: MonetDB/src/common/monet_options.mx,1.34
Option cleanup:
Removed monet_pid (not used anywhere that I can see), gdk_mem_bigsize,
gdk_mem_pagebits (used, but should not be advertized); cleaned up
monet_mod_path (no need to add MinGW-specific paths on non-MinGW
system); fixed sql_logdir and xquery_logdir to be different from each
other and the same as what's in the .conf file.
===================================================================
2009/04/01 - sjoerd: MonetDB4/src/monet/monet.mx,1.15
propagated changes of Tuesday Mar 31 2009 - Wednesday Apr 01 2009
from the Feb2009 branch to the development trunk
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2009/03/31 - sjoerd: src/monet/monet.mx,1.14.2.1
Fixed copyright year.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
===================================================================
2009/04/01 - sjoerd: MonetDB4/NT/Mserver.bat,1.5
Removed legacy code.
Move log file to new location.
===================================================================
2009/04/01 - boncz: MonetDB/src/gdk/gdk_posix.mx,1.168
MonetDB/src/gdk/gdk_utils.mx,1.239
gdk_posix:
- made mmap_trim really return a warning level between 0 and 4
gdk_utils:
- disable dynamic reduction of GDK_mem_maxsize in GDKmemfail
because the memory estimates never grow again and mem_inuse is not
a good estimator for it -- RAM in use also comes from mmapped files
this could make mem_maxsize very very small indeed
- code in GDKvmtrim now is certain to enforce a sizable mmap_minsize
(because we use log2(mem_maxsize_max)-8)
===================================================================
2009/04/01 - boncz: MonetDB/src/gdk/gdk_utils.mx,1.240
gd_utils:
- fix 32-bits overflow error in computation of GDK_mmap_minsize
===================================================================
## Comment 11411
Date: 2009-04-02 10:05:04 +0200
From: @drstmane
Most probably, the error is triggered by
./MonetDB4/src/modules/plain/sys.mx:479: CONST REMAP_PAGE_BITS := monet_environment.find("gdk_mem_pagebits").int();
after gdk_mem_pagebits has been removed from monet_options.mx, and hence from the enviroment (-BAT).
## Comment 11412
Date: 2009-04-02 10:44:44 +0200
From: @sjoerdmullender
I added the three values that I removed from monet_options.mx back into the monet_environment.
## Comment 11413
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2726337 at http://sourceforge.net/support/tracker.php?aid=2726337
| M4: Mserver startup errors after changes on 2009/04/01 | https://api.github.com/repos/MonetDB/MonetDB/issues/2027/comments | 0 | 2020-11-30T10:17:25Z | 2024-06-27T11:38:53Z | https://github.com/MonetDB/MonetDB/issues/2027 | 753,346,270 | 2,027 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-04-01 11:43:18 +0200
From: Loredana Afanasiev <<lafanasi>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2009-04-02 10:47:19 +0200
## Comment 11404
Date: 2009-04-01 23:43:18 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi team,
I get this two weird errors. Practically I can't write Boolean connectives in predicates, nor union of path expressions. Am I missing something totally obvious?
[lafanasi@zookst4 benchmarks]$ mclient -s "collection('HAN')[true and false]"
MAPI = monetdb@localhost:50100
QUERY = collection('HAN')[true
ERROR = !parse error: syntax error, unexpected $end, expecting ] on line 2, column 1
!parse error: XQuery parsing failed
and: cannot open
false]: cannot open
[lafanasi@zookst4 benchmarks]$ mcl -s "(collection('HAN')//spreker | collection('HAN')//spreker)"
MAPI = monetdb@localhost:50100
QUERY = (collection('HAN')//spreker
ERROR = !parse error: syntax error, unexpected $end, expecting ) on line 2, column 1
!parse error: XQuery parsing failed
|: cannot open
collection('HAN')//spreker): cannot open
thanks,
l.
## Comment 11405
Date: 2009-04-01 23:56:33 +0200
From: @drstmane
Works fine for me with the Feb2009 release branch --- well,
your literal
mclient -s "collection('HAN')[true and false]"
and
mcl -s "(collection('HAN')//spreker | collection('HAN')//spreker)"
"obviously" don't work, as mclient is not called with proper name/options,
but the corrected
mclient -lx -s "collection('HAN')[true and false]"
and
mclient -lx -s "(collection('HAN')//spreker | collection('HAN')//spreker)"
do work fine for me.
To me, your error messages suggest that the spaces are not quoted properly, i.e., only
"collection('HAN')[true"
resp.
"(collection('HAN')//spreker"
is seen as query and sent to the server.
If you use mclient with -s option, make sure that you properly quote the argument to -s on your command line such that the your shell indeed sees/treats it a one string/argument ...
## Comment 11406
Date: 2009-04-01 23:59:09 +0200
From: @drstmane
... in particular if (as most probably in your case) "mcl" and/or "mclient" are aliases or scripts as "convenience-wrappers" around the original mclient binary, make your that these scripts use proper quoting for arguments that might contain spaces --- for details, see the documentation of your scripting language and/or shell ...
## Comment 11407
Date: 2009-04-02 07:29:36 +0200
From: Jan Rittinger <<jan.rittinger>>
One obvious problem I see is that you try to 'and' nodes (./true and ./false) -- Perhaps you may try the boolean values ('true()' and 'false()') instead :)
## Comment 11408
Date: 2009-04-02 10:28:49 +0200
From: Loredana Afanasiev <<lafanasi>>
Both right!
(too tired too late yesterday..:))
thank you guys!
l.
## Comment 11409
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2725758 at http://sourceforge.net/support/tracker.php?aid=2725758
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.
| XQ: or and union | https://api.github.com/repos/MonetDB/MonetDB/issues/2026/comments | 0 | 2020-11-30T10:17:21Z | 2024-06-28T07:37:09Z | https://github.com/MonetDB/MonetDB/issues/2026 | 753,346,222 | 2,026 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-30 06:48:26 +0200
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-17 11:37:23 +0200
## Comment 11401
Date: 2009-03-30 18:48:26 +0200
From: Wouter Alink <<alink>>
After running a query like:
for $i in doc("1M_docs.xml")//doc return pf:add-doc($i,concat("1M_docs_",$i
),"1M_collection.xml")
(which failed, see "[ monetdb-Bugs-2722174 ] XQ: shredding 70GB XML fails")
A subsequent query shows that the database is in a state in between: the collection appearantly exists, but is broken. One would expect the previous query to behave atomically (either shred all, or shred none).
QUERY = count(collection("1M_collection.xml")//*)
ERROR = !ERROR: [append]: 1 times inserted nil due to errors at tuples 63@0.
!ERROR: [append]: first error was:
!ERROR: GDKload: cannot read: name=34/3430, ext=tail, 4 bytes missing.
!OS: No such file or directory
!ERROR: GDKload: failed name=34/3430, ext=tail
!ERROR: BUNappend: BAT required.
!ERROR: CMDappendConvert: operation failed.
!ERROR: interpret_unpin: [append] bat=1632,stamp=-44577 OVERWRITTEN
!ERROR: BBPdecref: tmp_3140 does not have pointer fixes.
!ERROR: interpret_params: leftfetchjoin(param 2): evaluation error.
real 1m22.913s
user 0m0.008s
sys 0m0.016s
## Comment 11402
Date: 2009-04-17 11:37:23 +0200
From: Wouter Alink <<alink>>
I assume this bug issue has disappeared after the fix for "[ monetdb-Bugs-2722174 ] XQ: shredding 70GB XML fails". (It has not appeared again)
This bug can be closed for now, but may be reopened if the issue re-appears.
Adding a test is not feasible as the data necessary is probably too large.
## Comment 11403
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2722190 at http://sourceforge.net/support/tracker.php?aid=2722190
| XQ: left-overs after failed shredding | https://api.github.com/repos/MonetDB/MonetDB/issues/2025/comments | 0 | 2020-11-30T10:17:18Z | 2024-06-28T07:37:09Z | https://github.com/MonetDB/MonetDB/issues/2025 | 753,346,190 | 2,025 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-30 06:38:44 +0200
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-10 01:36:43 +0200
## Comment 11394
Date: 2009-03-30 18:38:44 +0200
From: Wouter Alink <<alink>>
Shredding 1000000 (1 million) documents (+- 70GB) using MonetDB/XQuery fails, while it succeeds when only shredding the first 700000 of this collection. See error-message below. More investigation is needed. To be continued.
MAPI = monetdb@localhost:52009
QUERY = for $i in doc("1M_docs.xml")//doc return pf:add-doc($i,concat("1M_docs_",$i
),"1M_collection.xml")
ERROR = !ERROR: BBPdecref: 1001729024_rid_size does not have pointer fixes.
!ERROR: BBPdecref: 1001729024_rid_level does not have pointer fixes.
!ERROR: BBPdecref: 1001729024_rid_prop does not have pointer fixes.
!ERROR: BBPdecref: 1001729024_prop_text does not have pointer fixes.
!ERROR: BBPdecref: 1001729024_prop_val does not have pointer fixes.
real 240m55.752s
user 0m0.004s
sys 0m0.004s
## Comment 11395
Date: 2009-04-02 16:22:35 +0200
From: Wouter Alink <<alink>>
In the initial posting of this bug, the '1001729024_rid_size' bat was a bat which belonged to the /some/path/1M_docs.xml document (which contained the names of the documents). This document was shredded on the fly (cached, and not made persistent). The actual bug-query read:
for $i in doc("/some/path/1M_docs.xml")//doc return pf:add-doc($i,concat("1M_docs_",$i),"1M_collection.xml")
A possible problem could have been that the 'temporary' document was thrown away too early, but this doesn't seem to be the case:
If using an explicit add-doc for the XML-document which contained the document-names of the
million documents, which can be done using the following two queries
pf:add-doc("/some/path/1M_docs.xml","1M_docs.xml")
<>
for $i in doc("1M_docs.xml")//doc return pf:add-doc($i,concat("1M_docs_",$i),"1M_collection.xml")
Results in:
Mserver: gdk_bbp.mx:1705: decref: Assertion `0' failed.
Investigation showed that this time a 'ws' bat had too few refs.
So the thought that the 'temporary' document was thrown away too early may not be the problem after all.
## Comment 11396
Date: 2009-04-03 12:20:27 +0200
From: Wouter Alink <<alink>>
The following code seems to work (no errors or crashes are generated) in a few hours:
for line in 1 100001 200001 300001 400001 500001 600001 700001 800001 900001 1000001
do
echo " Shredding from $line to "$(($line + 100000))
time echo 'for $i in subsequence(doc("'$PWD/1M_doc_list.xml'")//doc,'$line',100000) return pf:add-doc($i, concat("all_",$i), "all")' | mclient -lxq
done
echo "Done!"
However, this doesn't say much about the actual problem. What it perhaps does say is that the total amount of data in 1 collection is not the problem.
## Comment 11397
Date: 2009-04-07 12:50:13 +0200
From: Wouter Alink <<alink>>
Cheering was too early... querying the resulting collection (which was shredded in batches) does still not work (assertion in decref).
The problem seems to be in __runtime_index() (which is invoked from open_coll(), which in turn is invoked in ws_collection_root()). This function both: uses massive amounts of memory (>150GB) and calls decref once too often (lowers the refs value to zero).
Debugging is more difficult, as setting watchpoints on an IA64 system seems a little difficult. To be continued.
## Comment 11398
Date: 2009-04-10 12:05:24 +0200
From: Wouter Alink <<alink>>
The bug should have been fixed yesterday by Peter's checkin. A test for the testweb can not be added easily, as the data is just too large. I will test the new code with the data, and will close the bug if everything works fine.
## Comment 11399
Date: 2009-04-10 13:36:43 +0200
From: Wouter Alink <<alink>>
There is only good news to tell:
- the initial bug is gone, and
- the database was not corrupted anyway, because the bug manifested itself only after the shredding of the document. This means that the databases created with the MonetDB before the fix (which gave an error at the end) can still be used, by simply using the recompiled Mserver on the same dbfarm)
## Comment 11400
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2722174 at http://sourceforge.net/support/tracker.php?aid=2722174
| XQ: shredding 70GB XML fails. | https://api.github.com/repos/MonetDB/MonetDB/issues/2024/comments | 0 | 2020-11-30T10:17:15Z | 2024-06-27T11:38:50Z | https://github.com/MonetDB/MonetDB/issues/2024 | 753,346,157 | 2,024 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-30 05:46:34 +0200
From: Wouter Alink <<alink>>
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2009-06-30 09:37:25 +0200
## Comment 11385
Date: 2009-03-30 17:46:34 +0200
From: Wouter Alink <<alink>>
dbat_finalize fails when runnning "tijah:create-ft-index()" on a 30GB XML document.
It seems like the count for BATsetcount() is calculated incorrectly. Note in the trace below that cnt=18446744073116273099 seems fairly unlikely, and is quite close to 2^63. So my guess is that there is a 64 bit to 32 bit conversion or the other way around that is incorrect.
Mserver: gdk_bat.mx:2136: BATsetcount: Assertion `b->U->capacity >= cnt' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 2305843009464971856 (LWP 13386)]
0xa000000000010621 in __kernel_syscall_via_break ()
(gdb) bt
0 0xa000000000010621 in __kernel_syscall_via_break ()
1 0x20000000026201c0 in raise () from /lib/libc.so.6.1
2 0x2000000002622810 in abort () from /lib/libc.so.6.1
3 0x2000000002610680 in __assert_fail () from /lib/libc.so.6.1
4 0x2000000001af6df0 in BATsetcount (b=0x6000000000d33688, cnt=18446744073116273099) at gdk_bat.mx:2136
5 0x200000000baec340 in dbat_finalize (dbat=0x6000000001887ce8, topidx=-593278517) at serialize_pftijah.mx:123
6 0x200000000baf9580 in add2collection_bathandler (tjCtx_BAT=0x60000000010010d8, ws=0x60000000014341c8, docs=0x6000000000fdea80)
at serialize_pftijah.mx:1431
7 0x200000000baf9b50 in CMDtj_throw2collection_bat (tjCtx_BAT=0x60000000010010d8, ws=0x60000000014341c8, docs=0x6000000000fdea80)
at serialize_pftijah.mx:1451
8 0x200000000baa8f50 in CMDtj_throw2collection_bat_unpack542006064 (argc=4, argv=0x200000000ef90d88) at pftijah.glue.c:138
9 0x200000000037f790 in interpret (stk=615, lt=0x600000000105a538, res=0x200000000ef9b798) at monet_interpreter.mx:1134
10 0x200000000039fdc0 in interpret_seqblock (stk=615, lt=0x600000000105a348, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
11 0x2000000000379860 in interpret (stk=574, lt=0x600000000105a348, res=0x200000000ef9b798) at monet_interpreter.mx:732
12 0x2000000000379c00 in interpret (stk=574, lt=0x600000000105a250, res=0x200000000ef9b798) at monet_interpreter.mx:752
13 0x200000000039fdc0 in interpret_seqblock (stk=574, lt=0x60000000010597b8, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
14 0x2000000000379860 in interpret (stk=578, lt=0x60000000010597b8, res=0x200000000ef9b798) at monet_interpreter.mx:732
15 0x2000000000273670 in CMDcatch (stk=578, lt=0x6000000001059740, res=0x200000000ef9b798) at builtin.mx:1047
16 0x200000000037b630 in interpret (stk=578, lt=0x6000000001059740, res=0x200000000ef9b798) at monet_interpreter.mx:820
17 0x200000000039f3c0 in interpret_assignment (stk=578, lt=0x60000000010596f0, res=0x200000000ef9b798) at monet_interpreter.mx:1827
18 0x2000000000389840 in interpret_var (stk=578, lt=0x60000000010596c8, res=0x200000000ef9b798) at monet_interpreter.mx:1289
19 0x200000000037b2e0 in interpret (stk=578, lt=0x60000000010596c8, res=0x200000000ef9b798) at monet_interpreter.mx:794
20 0x200000000039fdc0 in interpret_seqblock (stk=578, lt=0x6000000001059458, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
21 0x2000000000379860 in interpret (stk=579, lt=0x6000000001059458, res=0x200000000ef9b798) at monet_interpreter.mx:732
22 0x200000000039fdc0 in interpret_seqblock (stk=579, lt=0x6000000001059218, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
23 0x2000000000379860 in interpret (stk=544, lt=0x6000000001059218, res=0x200000000ef9b798) at monet_interpreter.mx:732
24 0x200000000037e5a0 in interpret (stk=544, lt=0x6000000000ce7148, res=0x200000000ef9b798) at monet_interpreter.mx:1117
25 0x200000000039fdc0 in interpret_seqblock (stk=544, lt=0x6000000000cfeea8, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
26 0x2000000000379860 in interpret (stk=589, lt=0x6000000000cfeea8, res=0x200000000ef9b798) at monet_interpreter.mx:732
27 0x2000000000379c00 in interpret (stk=589, lt=0x6000000000cfee58, res=0x200000000ef9b798) at monet_interpreter.mx:752
28 0x200000000039fdc0 in interpret_seqblock (stk=589, lt=0x6000000000cfec28, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
29 0x2000000000379860 in interpret (stk=588, lt=0x6000000000cff918, res=0x200000000ef9b798) at monet_interpreter.mx:732
30 0x200000000039fdc0 in interpret_seqblock (stk=588, lt=0x6000000000d1d6f8, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
31 0x2000000000379860 in interpret (stk=591, lt=0x6000000000d1d6f8, res=0x200000000ef9b798) at monet_interpreter.mx:732
32 0x200000000037e5a0 in interpret (stk=591, lt=0x6000000000d1d490, res=0x200000000ef9b798) at monet_interpreter.mx:1117
33 0x200000000039fdc0 in interpret_seqblock (stk=591, lt=0x6000000000d1d468, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
34 0x2000000000379860 in interpret (stk=594, lt=0x6000000000d1d468, res=0x200000000ef9b798) at monet_interpreter.mx:732
35 0x200000000039fdc0 in interpret_seqblock (stk=594, lt=0x6000000000d1d228, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
36 0x2000000000379860 in interpret (stk=592, lt=0x6000000000d1d228, res=0x200000000ef9b798) at monet_interpreter.mx:732
37 0x200000000037e5a0 in interpret (stk=592, lt=0x6000000000b82a88, res=0x200000000ef9b798) at monet_interpreter.mx:1117
38 0x200000000039fdc0 in interpret_seqblock (stk=592, lt=0x6000000000b828f8, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
39 0x2000000000379860 in interpret (stk=595, lt=0x6000000000b828f8, res=0x200000000ef9b798) at monet_interpreter.mx:732
40 0x2000000000379c00 in interpret (stk=595, lt=0x6000000000b827d8, res=0x200000000ef9b798) at monet_interpreter.mx:752
41 0x200000000039fdc0 in interpret_seqblock (stk=595, lt=0x6000000000b81f88, res=0x200000000ef9b798, scope=1) at monet_interpreter.mx:1877
42 0x2000000000379860 in interpret (stk=599, lt=0x6000000000b81f88, res=0x200000000ef9b798) at monet_interpreter.mx:732
43 0x200000000039fdc0 in interpret_seqblock (stk=599, lt=0x6000000000b81f08, res=0x200000000ef9b798, scope=0) at monet_interpreter.mx:1877
44 0x2000000000379860 in interpret (stk=599, lt=0x6000000000b81f08, res=0x200000000ef9b798) at monet_interpreter.mx:732
45 0x20000000003eec30 in tuple_interpret_vpval_fival (head=0x6000000000cb37e0, tail=0x6000000000f1af68, handle=0x6000000000b6c3a8)
at monet_interpreter.mx:2310
46 0x200000000022bc90 in doCMDbatloop (b=0x6000000000d4b5c8, handle=0x200000000ef9b9a0, low=0, high=0) at bat.mx:1748
47 0x200000000022c570 in CMDbatloop_std (b=0x6000000000d4b5c8, handle=0x200000000ef9b9a0) at bat.mx:1795
48 0x20000000002118d0 in CMDbatloop_std_unpack1481088144 (argc=3, argv=0x200000000ef9b980) at bat.glue.c:2534
49 0x2000000000409c70 in interpret_iterator (stk=599, lt=0x6000000000d4c3d8, parallel=1) at monet_interpreter.mx:2258
50 0x200000000037ad40 in interpret (stk=599, lt=0x6000000000d4c3d8, res=0x200000000efa16f8) at monet_interpreter.mx:778
51 0x200000000039fdc0 in interpret_seqblock (stk=599, lt=0x6000000000d014e8, res=0x200000000efa16f8, scope=1) at monet_interpreter.mx:1877
52 0x2000000000379860 in interpret (stk=597, lt=0x6000000000d014e8, res=0x200000000efa16f8) at monet_interpreter.mx:732
53 0x200000000039fdc0 in interpret_seqblock (stk=597, lt=0x6000000000d49098, res=0x200000000efa16f8, scope=1) at monet_interpreter.mx:1877
54 0x2000000000379860 in interpret (stk=554, lt=0x6000000000d49098, res=0x200000000efa16f8) at monet_interpreter.mx:732
55 0x200000000037e5a0 in interpret (stk=554, lt=0x6000000000ffa4f8, res=0x200000000efa16f8) at monet_interpreter.mx:1117
56 0x200000000039fdc0 in interpret_seqblock (stk=554, lt=0x6000000000d29028, res=0x200000000efa16f8, scope=1) at monet_interpreter.mx:1877
57 0x2000000000379860 in interpret (stk=1, lt=0x6000000000d6d4c8, res=0x200000000efa16f8) at monet_interpreter.mx:732
58 0x2000000000273670 in CMDcatch (stk=1, lt=0x6000000000b74e48, res=0x200000000efa16f8) at builtin.mx:1047
59 0x200000000037b630 in interpret (stk=1, lt=0x6000000000b74e48, res=0x200000000efa16f8) at monet_interpreter.mx:820
60 0x200000000039f3c0 in interpret_assignment (stk=1, lt=0x6000000000b74df8, res=0x200000000efa16f8) at monet_interpreter.mx:1827
61 0x2000000000379720 in interpret (stk=1, lt=0x6000000000b74df8, res=0x200000000efa16f8) at monet_interpreter.mx:725
62 0x200000000039fdc0 in interpret_seqblock (stk=1, lt=0x6000000000a20590, res=0x200000000efa16f8, scope=0) at monet_interpreter.mx:1877
63 0x2000000000379860 in interpret (stk=1, lt=0x600000000002ca28, res=0x200000000efa16f8) at monet_interpreter.mx:732
64 0x200000000b19a7d0 in xquery_tree_exec (ctx=0x200000000c436ea8, t=0x600000000002ca28, repeat=0) at pathfinder.mx:4517
65 0x200000000b19b940 in xquery_mil_exec (ctx=0x200000000c436ea8,
buf=0x6000000000d4ceb0 "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 pathfinder.mx:4575
66 0x200000000b19d390 in xquery_compile_exec (ctx=0x200000000c436ea8, options=2,
xquery=0x200000000c473879 "tijah:create-ft-index((\"patent_500000.xml\"))\n", is_url=0, prologue=0x200000000efa2508,
query=0x200000000efa2510, epilogue=0x200000000efa2518, module=0x0) at pathfinder.mx:4723
67 0x200000000b1b14e0 in xquery_prepare (ctx=0x200000000c436ea8, usec=22391967,
query=0x200000000c473879 "tijah:create-ft-index((\"patent_500000.xml\"))\n") at pathfinder.mx:6042
68 0x200000000b1b2950 in xquery_client_engine (mc=0x200000000b8f31d8) at pathfinder.mx:6197
69 0x200000000b8d93e0 in mapi_client_engine (FC=0x200000000b8f31d8) at mapi.mx:502
70 0x20000000021815d0 in start_thread () from /lib/libpthread.so.0
71 0x2000000002754b10 in __clone2 () from /lib/libc.so.6.1
## Comment 11386
Date: 2009-03-30 18:00:14 +0200
From: @drstmane
could also be a unsigned vs. signed under/overflow problem:
18446744073116273099ULL <-> -593278517LL
Stefan
## Comment 11387
Date: 2009-03-30 18:03:36 +0200
From: @drstmane
and ...
18446744073116273099 is of course closer to 2^64 = 18446744073709551616 than to 2^63 = 9223372036854775808 --- (even) on 64-bit systems, BATs can only contain less than 2^63 = 9223372036854775808 BUNs ...
## Comment 11388
Date: 2009-03-30 18:05:46 +0200
From: @drstmane
... and:
5 0x200000000baec340 in dbat_finalize (dbat=0x6000000001887ce8,
topidx=-593278517) at serialize_pftijah.mx:123
^^^^^^^^^^^^^^^^^
## Comment 11389
Date: 2009-03-31 09:40:24 +0200
From: Henning Rode <<hrode>>
after a second look in serialize_pftijah.mx, it might go wrong in line 553:
par_tijahPre = (oid)atol(str_tijahPre);
the conversion from string to integer and then to oid is probably not a good idea here.
## Comment 11390
Date: 2009-03-31 09:53:14 +0200
From: Jan Flokstra <<jflokstra>>
I changed the type of the topidx parameter in dbat_finalize() and associated local variables to oid. It could be the base adres of the bat was computed faulty by this.
JanF
## Comment 11391
Date: 2009-04-03 12:16:25 +0200
From: Wouter Alink <<alink>>
New day, new error. Previously the dbat_finanlize() failed. That seems to be fixed, but now I get this at the Mserver prompt (more investigation needed).
Mserver: algebra.mx:1847: CMDcount: Assertion `BATcount(b) <= 2147483647' failed.
Aborted
This appears to be because count() in mil returns an int. It should have been returning a wrd, but there is a lot of code affected by such a change. I'll look into this.
No test possible as data is just too large.
## Comment 11392
Date: 2009-06-30 09:37:25 +0200
From: Henning Rode <<hrode>>
the bug was fixed recently by changing all MIL calls to count() to count_wrd() which returns wrd instead of integer.
## Comment 11393
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2722117 at http://sourceforge.net/support/tracker.php?aid=2722117
| PF/TIJAH: dbat_finalize fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2023/comments | 0 | 2020-11-30T10:17:11Z | 2024-06-27T11:38:49Z | https://github.com/MonetDB/MonetDB/issues/2023 | 753,346,113 | 2,023 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-27 02:56:02 +0100
From: Wouter Alink <<alink>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-17 11:28:16 +0200
## Comment 11377
Date: 2009-03-27 14:56:02 +0100
From: Wouter Alink <<alink>>
Regarding compilation:
./monetdb-install.sh --nightly=stable --enable-xquery --prefix=/home/walink/opt/MonetDB-stable-debug/ --enable-debug
When I try to use the '--enable-debug' flag, compilation fails (see attached log). The end of the log reads:
/tmp/cc6YZd3B.s:4926942: Error: integer operand out of range
/tmp/cc6YZd3B.s:4927107: Error: integer operand out of range
/tmp/cc6YZd3B.s:4927379: Error: integer operand out of range
gmake[5]: *** [libbat_la-gdk_scanselect_defs.lo] Error 1
gmake[4]: *** [all] Error 2
gmake[3]: *** [all-recursive] Error 1
gmake[2]: *** [all] Error 2
gmake[1]: *** [all-recursive] Error 1
gmake: *** [all] Error 2
making MonetDB failed
If I compile without "--enable-debug", all works fine.
Note that the machine used is an IA64 machine.
## Comment 11378
Date: 2009-03-27 15:01:00 +0100
From: @grobian
sorry, click error.
## Comment 11379
Date: 2009-03-29 11:17:01 +0200
From: Wouter Alink <<alink>>
hmmm, I found the following URL which might be related: https://bugzilla.redhat.com/show_bug.cgi?id=33288. Is it related? Do I understand correctly that this bug (which is marked "won't fix") is about the object file becoming to large?, and that this 'shouldn't be done'.
I tried compiling without the 2 ALGODEBUG lines in src/gdk/gdk_scanselect_defs.mx and that worked fine. The errors also disappear when I only remove the BATgetId() calls in those lines.
## Comment 11380
Date: 2009-03-30 00:19:41 +0200
From: @drstmane
I can reproduce the compilation error with the source base from CVS (Feb2009 branch) using default CVS configure settings (i.e., --enable-strict --enable-assert --enable-debug --disable-optimize) which is about the same as using monetdb-install.sh with --enable-debug (default of compilation from tarballs, and hence when using monetdb-install.sh, is --disable-strict --disable-assert --disable-debug --disable-optimize).
In case you want/need to debug only other code but MonetDB Common (GDK) consider compiling MonetDB without --enable-debug (with --disable-debug) and only those parts that you want/need to debug with --ebale-debug --- don't know though, whether monetdb-install.sh allows this easily --- or consider reducing the code (and hence .o) file size via
$ .../configure --help
[...]
--enable-noexpand do not expand the comma-separated list of MIL types
given as argument, or "all" if no expansion should
be done default=
[...]
e.g.,
$ .../configure --enable-noexpand=ptr
or
$ .../configure --enable-noexpand=str
## Comment 11381
Date: 2009-03-30 00:41:48 +0200
From: @drstmane
--enable-noexpand=ptr
does not help
--enable-noexpand=all
appears to work fine
## Comment 11382
Date: 2009-04-17 11:17:08 +0200
From: @sjoerdmullender
It seems to me this is a compiler bug. The compiler should not produce offsets that the assembler can't cope with.
I propose to close this as Won't Fix.
## Comment 11383
Date: 2009-04-17 11:28:16 +0200
From: Wouter Alink <<alink>>
Sounds OK to me.
## Comment 11384
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2716942 at http://sourceforge.net/support/tracker.php?aid=2716942
| GDK: Error: integer operand out of range (on IA64/Itanium) | https://api.github.com/repos/MonetDB/MonetDB/issues/2022/comments | 0 | 2020-11-30T10:17:07Z | 2024-06-28T07:37:09Z | https://github.com/MonetDB/MonetDB/issues/2022 | 753,346,073 | 2,022 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-27 12:01:31 +0100
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: 11.1.1 (Mar2011) [obsolete]
Last updated: 2011-04-28 16:39:00 +0200
## Comment 11372
Date: 2009-03-27 12:01:31 +0100
From: Wouter Alink <<alink>>
The following error occurs for the query below:
$ ~/opt/MonetDB-Feb2009/bin/pf ../bugs/no_string_value_implementation.xq
fatal error: Algebra implementation for function `pf:string-value' is missing.
What I tried:
- specify the return type of the function: "as node()*" (which does not work)
- specify the return type of the function: "as element()*" (which works fine)
- inline the function in the query "let $items := $patents//country" (works fine too)
----------------------------------
declare function do($nodes as node()*) {
$nodes//country
};
let $countries := ("NL","DE","UK")
let $patents := (<entry><country>NL</country></entry>,
<entry><country>DE</country></entry>)
let $items := do($patents)
for $i at $k in $items
let $country := $countries[. = $i]
return element { "entry" } { $i, $country }
## Comment 11373
Date: 2009-04-07 13:38:17 +0200
From: @peterboncz
it is interesting that there is a difference between node() and element()
Jan, any idea?
## Comment 11374
Date: 2009-04-07 14:07:03 +0200
From: Jan Rittinger <<jan.rittinger>>
Currently we only resolve string-value if (at compile time) we can derive a type for which we have a translation on the MIL level. As there is no code that can provide the string-value of mixed node sequences an error is generated.
A solution which (almost) always helps is a stricter return type for UDFs.
## Comment 11375
Date: 2009-06-25 16:34:47 +0200
From: Wouter Alink <<alink>>
I found another/better example for this bug (I think it is the same bug, correct me if i'm wrong). This fails:
declare function equalA($a, $b) as xs:boolean {
$a=$b
};
equalA("a","b")
It produces:
$ mclient -lxq -p50100 < ~/tmp/xqBug.xq
MAPI = monetdb@localhost:50100
QUERY = declare function equalA($a, $b) as xs:boolean {
ERROR = !fatal error: Algebra implementation for function `pf:string-value' is missing.
! halted in /home/alink/workspace/MonetDB/pathfinder/compiler/algebra/builtins.c (PFbui_pf_string_value), line 6341
This xquery fails, while the following works fine:
declare function equalA($a as xs:string, $b as xs:string) as xs:boolean {
$a=$b
};
equalA("a","b")
so again, "stricter types" for UDFs is the solution? (note that this time it affects the input parameters of the function)
## Comment 11376
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2716743 at http://sourceforge.net/support/tracker.php?aid=2716743
## Comment 15695
Date: 2011-03-28 17:37:06 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15774
Date: 2011-04-28 16:39:00 +0200
From: @sjoerdmullender
Development on MonetDB4 and MonetDB/XQuery has ceased. It is unlikely that this bug will be fixed.
The last release of MonetDB/XQuery and MonetDB4 is Mar2011.
| PF: pf:string-value missing | https://api.github.com/repos/MonetDB/MonetDB/issues/2021/comments | 0 | 2020-11-30T10:17:03Z | 2024-06-28T07:37:08Z | https://github.com/MonetDB/MonetDB/issues/2021 | 753,346,017 | 2,021 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-27 11:40:29 +0100
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-11-12 07:06:00 +0100
## Comment 11362
Date: 2009-03-27 11:40:29 +0100
From: Wouter Alink <<alink>>
The following query doesn't seem to get through step 18 of the pathfinder compiler (it 'hangs')
What I tried:
- Leaving out the 'replace()' function, the query compiles fine
- Replacing one or more child steps into descendant steps in "$rootnode//company/addressbook/name" makes it work fine, for example "$rootnode//company//name"
(I used the pf that comes with Feb2009 release)
-----------------------------
declare function local:normCompanyName($name as xs:string) as xs:string {
normalize-space(replace(
upper-case(translate($name,",./()-"," "))
,"LIMITED","LTD"))
};
declare function local:companyList($rootnode as node()*) {
let $all := $rootnode//company/addressbook/name
let $uniqueNames := distinct-values(for $i in $all
return local:normCompanyName($i))
for $i in $uniqueNames
let $firstNode := $all[local:normCompanyName(.)=$i][1]
return $firstNode/../..
};
let $col := doc("%SOURCE%")
return local:companyList($col)
## Comment 11363
Date: 2009-03-27 12:05:49 +0100
From: Wouter Alink <<alink>>
oops, for this bug I used by accident a pf-compiler from last months 'current'. I don't know whether the bug is still valid. The Feb2009-pf-compiler does compile the query fine.
The pf-compiler I used for this query:
$ pf -h
Pathfinder XQuery Compiler ($Revision: 1.113 $, $Date: 2009/02/09 08:29:27 $)
(c) Database Systems Group, Eberhard Karls Universitaet Tuebingen
## Comment 11364
Date: 2009-03-27 12:12:21 +0100
From: Wouter Alink <<alink>>
oops, for this bug I used by accident a pf-compiler from last months 'current'. I don't know whether the bug is still valid. The Feb2009-pf-compiler does compile the query fine.
The pf-compiler I used for this query:
$ pf -h
Pathfinder XQuery Compiler ($Revision: 1.113 $, $Date: 2009/02/09 08:29:27 $)
(c) Database Systems Group, Eberhard Karls Universitaet Tuebingen
## Comment 11365
Date: 2009-04-07 13:47:24 +0200
From: @peterboncz
(gdb) bt
0 better_or_equal (a=0x7fffcf717150, b=0x7fffcfc79010) at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3247
1 0x00000000004dd6c9 in prune_plans (planlist=0x7fffd0b11e20)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3186
2 0x00000000004deec7 in plan_subexpression (n=0x7ffff7167c80)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3737
3 0x00000000004dd906 in plan_subexpression (n=0x7ffff71682c0)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
4 0x00000000004dd906 in plan_subexpression (n=0x7ffff710d7c0)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
5 0x00000000004dd906 in plan_subexpression (n=0x7ffff710db70)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
6 0x00000000004dd906 in plan_subexpression (n=0x7ffff7168960)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
7 0x00000000004dd906 in plan_subexpression (n=0x7ffff7168fa0)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
8 0x00000000004dd906 in plan_subexpression (n=0x7ffff71694e0)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
9 0x00000000004dd906 in plan_subexpression (n=0x7ffff7131c90)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
10 0x00000000004dd906 in plan_subexpression (n=0x7ffff7131e30)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
11 0x00000000004dd906 in plan_subexpression (n=0x7ffff7169b30)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
12 0x00000000004dd906 in plan_subexpression (n=0x7ffff710fc50)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
13 0x00000000004dd906 in plan_subexpression (n=0x7ffff710ff10)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3305
14 0x00000000004def85 in PFplan (root=0x7ffff710ff10) at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3773
15 0x000000000042ab46 in PFcompile (url=0x7fffffffe3c5 "t", pfout=0x39b476c780, status=0x7fffffffdf00)
at /home/users/boncz/src/pathfinder/compiler/compile.c:683
16 0x0000000000429ad5 in main (argc=2, argv=0x7fffffffe078) at /home/users/boncz/src/pathfinder/compiler/main.c:1078
(gdb) l
3242 for (unsigned int j = 0; j < PFord_set_count (a->orderings); j++) {
3243 /*
3244 * If the this order in a implies the current order in b,
3245 * we are satisfied.
3246 */
3247 if (PFord_implies (
3248 PFord_set_at (a->orderings, j),
3249 PFord_set_at (b->orderings, i))) {
3250 satisfied = true;
3251 break;
(gdb) p PFord_set_count (a->orderings)
$4 = 107520
(gdb)
(gdb) finish
TAKES HALF A SECOND
Run till exit from 0 better_or_equal (a=0x7fffcf717150, b=0x7fffcfc79010)
at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3247
0x00000000004dd6c9 in prune_plans (planlist=0x7fffd0b11e20) at /home/users/boncz/src/pathfinder/compiler/algebra/planner.c:3186
3186 while (j < PFarray_last (in) &&
Value returned is $5 = false
(gdb) l
3164 for (unsigned int i = 0; i < PFarray_last (in); i++) {
(gdb)
3165 plan_t *cur = *(plan_t **) PFarray_at (in, i);
(gdb)
3168 bool found_better = false;
(gdb)
3171 for (unsigned int j = 0; j < PFarray_last (ret); j++)
(gdb)
3172 if (better_or_equal (*(plan_t **) PFarray_at (ret, j), cur)) {
(gdb) p i
$8 = 4
(gdb) p *in
$9 = {base = 0x7fffcf30bc80, bound = 52, appi = 8, esize = 8, clear = false}
(gdb) p *ret
$10 = {base = 0x7fffcf30bac0, bound = 51, appi = 4, esize = 8, clear = false}
(gdb)
I think something needs to be done to cut off the search space...
## Comment 11366
Date: 2009-04-07 13:50:05 +0200
From: @peterboncz
forgot to say, memory consumption goes through the roof as well
Tasks: 257 total, 1 running, 254 sleeping, 2 stopped, 0 zombie
Cpu(s): 0.7%us, 1.3%sy, 0.0%ni, 96.4%id, 1.6%wa, 0.0%hi, 0.0%si, 0.0%st
Mem: 8199192k total, 8152836k used, 46356k free, 1244k buffers
Swap: 16579000k total, 5931108k used, 10647892k free, 24664k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18454 boncz 20 0 19248 1408 976 R 0.3 0.0 0:00.07 top
18397 boncz 20 0 10.0g 7.3g 284 T 0.0 93.6 0:53.21 pf
## Comment 11367
Date: 2009-04-07 14:03:09 +0200
From: Jan Rittinger <<jan.rittinger>>
I tried to improve the search space enumeration some time ago. The enumeration however was never designed to perform well and I don't have ideas to improve its performance without sacrificing the approach.
Furthermore if the M5 port is successful this part of the code will become superfluous.
## Comment 11368
Date: 2009-09-08 08:48:26 +0200
From: Jan Rittinger <<jan.rittinger>>
Hi Wouter this seems to work fine again...
Could you please verify.
## Comment 11369
Date: 2009-09-08 09:36:33 +0200
From: Wouter Alink <<alink>>
I added a test "child-steps-and-replace.SF-2716723", it ran fine with my Aug2009 release MonetDB.
## Comment 11370
Date: 2009-11-12 19:06:00 +0100
From: Wouter Alink <<alink>>
testweb entry is green
## Comment 11371
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2716723 at http://sourceforge.net/support/tracker.php?aid=2716723
| PF: child-steps + replace() fails to compile | https://api.github.com/repos/MonetDB/MonetDB/issues/2020/comments | 0 | 2020-11-30T10:17:00Z | 2024-06-28T07:37:08Z | https://github.com/MonetDB/MonetDB/issues/2020 | 753,345,972 | 2,020 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-27 10:11:21 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-04-24 11:01:26 +0200
## Comment 11356
Date: 2009-03-27 10:11:21 +0100
From: @grobian
done
make[1]: Entering directory
`/home/monet/testing/monet.GNU.64.64.d.1.21272/java/Gentoo2.0.0/conf'
make[1]: *** No rule to make target `config.guess', needed by `distdir'.
http://www.ins.cwi.nl/~monet/permastore/2009-03-27/Stable/dist-java-GNU.64.64.d.
1-Gentoo2.0.0.errors.htmll205
Since this happens on both pegasus (Gentoo Prefix powered OpenSolaris) and pegathree (Gentoo Linux), I suspect this is caused by a newer release of auto* software or related. Needs investigation. Both machines run the newest of the newest, same versions from the same sources.
## Comment 11357
Date: 2009-04-22 08:06:48 +0200
From: @drstmane
The same problems now also occurs on build-x86-macosx (Darwin), where we (now) also use the Gentoo Prefix.
On all affected systems, automake & autoconf differ only slightly from other systems (automake: v1.10.[12] vs. v1.10; autoconf: v1.63 vs. v1.61; the newer version are actually also used on Fedora 10, where `make dist` works fine also for Java),
but libtool differs more significantly: v2.2.6 vs v1.5.2[246].
Hence, this problem, i.e., conf/config.guess is no longer generated during `./bootstrap` for Java, might be related to the newer version of libtool.
## Comment 11358
Date: 2009-04-23 22:14:27 +0200
From: @grobian
https://answers.launchpad.net/ubuntu/+source/libtool/+question/46987
however adding --install to the libtoolize call doesn't seem to work for me at least.
## Comment 11359
Date: 2009-04-23 22:27:28 +0200
From: @grobian
not sure if it's libtool any more.
## Comment 11360
Date: 2009-04-24 11:01:26 +0200
From: @grobian
We explicitly insisted on installing config.guess, config.sub and ltmain.sh, which are not necessary in the Java repository, which newer autotools detect and hence do not generate/install.
This bug is not blocking the release, since we build the release with older autotools which do not exhibit this bug, hence the released sources which include these autotools will build fine on platforms having newer autotools available.
## Comment 11361
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2716585 at http://sourceforge.net/support/tracker.php?aid=2716585
| Java fails to run make dist with latest autotools | https://api.github.com/repos/MonetDB/MonetDB/issues/2019/comments | 0 | 2020-11-30T10:16:57Z | 2024-06-27T11:38:45Z | https://github.com/MonetDB/MonetDB/issues/2019 | 753,345,936 | 2,019 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-25 08:06:38 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2009-03-30 09:26:06 +0200
## Comment 11352
Date: 2009-03-25 08:06:38 +0100
From: @drstmane
While working fine with Python >= 2.5, Mtest.py fails with Pyhton (<=)2.3.4 as "os.devnull" (and os.path.devnull) appear to not be present in "such old" versions of Python; cf. e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.Int.64.64.d.1-RedHat4WS..2009.03.25_00-09-01/test10.out.html
Should we either require a more recent version of Python (say >=2.5?) --- and hope we can upgrade the respective machine (titan) ---, or rather (re-)add a fall-back to not require os.devnull in Mtest.py with older version sof Pyhton?
## Comment 11353
Date: 2009-03-25 09:28:38 +0100
From: @sjoerdmullender
I checked in a fix. If it works, we can close this.
## Comment 11354
Date: 2009-03-30 09:26:06 +0200
From: @drstmane
The fix appears to work fine:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.Int.64.64.d.1-RedHat4WS/test10.out.html
Thanks!
## Comment 11355
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2711258 at http://sourceforge.net/support/tracker.php?aid=2711258
| Mtest.py fails with Python <=2.3.? | https://api.github.com/repos/MonetDB/MonetDB/issues/2018/comments | 0 | 2020-11-30T10:16:53Z | 2024-06-27T11:38:44Z | https://github.com/MonetDB/MonetDB/issues/2018 | 753,345,896 | 2,018 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-24 10:07:48 +0100
From: Wouter Alink <<alink>>
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2009-03-30 06:08:14 +0200
## Comment 11347
Date: 2009-03-24 22:07:48 +0100
From: Wouter Alink <<alink>>
The following error occurred after +- 1 hour of indexing, for a document which is roughly 30GB in size.
(I don't think we ran out of OIDs this time, as they are described in 64bits)
$ echo 'tijah:create-ft-index("doc30GB.xml")' | mclient -lxq -p52009
MAPI = monetdb@localhost:52009
QUERY = tijah:create-ft-index("doc30GB.xml")
ERROR = !ERROR: dbat_extend: BATextend["incomplete"](size>INT_MAX) fails
!ERROR: CMDtj_throw2collection_bat: operation failed.
!ERROR: BBPdecref: 1000000011_rid_level does not have pointer fixes.
The Mserver prompt reads:
$ /home/walink/opt/MonetDB-Feb2009//bin/Mserver --set mapi_port=52009 --dbinit="module(pathfinder);"
MonetDB Server v4.28.0
based on GDK v1.28.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for ia64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.0 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:52010/admin
MonetDB>
## Comment 11348
Date: 2009-03-26 19:14:52 +0100
From: Wouter Alink <<alink>>
I recompiled MonetDB from the stable branch. The previous error is gone, but there is still something wrong (and it happens around the same time in the process (+- 60min))... I will do some more tests to get more information.
$ time echo 'tijah:create-ft-index(("doc30GB.xml"))' | mclient -lxq -p52011
MAPI = monetdb@localhost:52011
ACTION= read_line
QUERY = tijah:create-ft-index(("doc30GB.xml"))
ERROR = Connection terminated
real 59m32.971s
user 0m0.016s
sys 0m1.224s
$
Mserver says:
$ ~/opt/MonetDB-stable/bin/Mserver --dbinit="module(pathfinder);" --set mapi_port=52011
MonetDB Server v4.28.3
based on GDK v1.28.3
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for ia64-suse-linux/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.3 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:52012/admin
MonetDB>Segmentation fault
$
## Comment 11349
Date: 2009-03-30 18:08:10 +0200
From: Wouter Alink <<alink>>
fixed in cvs (Feb2009 branch)
follow up filed in: [ monetdb-Bugs-2722117 ] PF/TIJAH: dbat_finalize fails
## Comment 11350
Date: 2009-03-30 18:09:13 +0200
From: Wouter Alink <<alink>>
ps: no test possible as data to reproduce is too large (30GB)
## Comment 11351
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2710426 at http://sourceforge.net/support/tracker.php?aid=2710426
| PF/TIJAH: dbat_extend fails | https://api.github.com/repos/MonetDB/MonetDB/issues/2017/comments | 0 | 2020-11-30T10:16:50Z | 2024-06-27T11:38:43Z | https://github.com/MonetDB/MonetDB/issues/2017 | 753,345,862 | 2,017 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-23 05:56:23 +0100
From: @swingbit
To: @mlkersten
Version: -- development
Last updated: 2009-05-09 11:20:33 +0200
## Comment 11342
Date: 2009-03-23 17:56:23 +0100
From: @swingbit
The statement CREATE VIEW .. AS BATS; seems to be no longer available, but it still is in the documentation.
## Comment 11343
Date: 2009-04-01 16:52:04 +0200
From: @sjoerdmullender
This is documented in at least monetweb/Docs/SQL/SQLsyntax.texi. The feature seems to have been removed August 2006.
## Comment 11344
Date: 2009-04-26 10:34:15 +0200
From: @drstmane
The outdated documentation in has been removed by
===================================================================
2009/04/01 - mk: monetweb/Docs/SQL/SQLsyntax.texi,1.2
Patching the documentation, removal of non-recoginzed statement
===================================================================
Unless there are other known places where this deprecated feature is still documented, I think this report can be closed, right?
## Comment 11345
Date: 2009-05-09 23:20:06 +0200
From: @mlkersten
This feature is closed indeed. It will be replaced soon by an BAT attach function.
## Comment 11346
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2706627 at http://sourceforge.net/support/tracker.php?aid=2706627
| SQL: CREATE VIEW .. AS BATS; | https://api.github.com/repos/MonetDB/MonetDB/issues/2016/comments | 0 | 2020-11-30T10:16:47Z | 2024-06-27T11:38:42Z | https://github.com/MonetDB/MonetDB/issues/2016 | 753,345,823 | 2,016 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-23 10:44:10 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-03-26 03:46:07 +0100
## Comment 11339
Date: 2009-03-23 10:44:10 +0100
From: @grobian
Merovingian should remove its pid-file upon a clean shutdown.
## Comment 11340
Date: 2009-03-23 15:21:04 +0100
From: @grobian
fixed in stable
## Comment 11341
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2705666 at http://sourceforge.net/support/tracker.php?aid=2705666
| Merovingian does not remove pid-file on clean shutdown | https://api.github.com/repos/MonetDB/MonetDB/issues/2015/comments | 0 | 2020-11-30T10:16:44Z | 2024-06-27T11:38:41Z | https://github.com/MonetDB/MonetDB/issues/2015 | 753,345,794 | 2,015 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-22 08:35:41 +0100
From: @skinkie
To: @njnes
Version: 11.21.5 (Jul2015)
CC: @swingbit
Last updated: 2016-01-15 11:38:07 +0100
## Comment 11335
Date: 2009-03-22 20:35:41 +0100
From: @skinkie
There are two issues here; one is easy to reproduce the other one I cannot yet reproduce in a smaller setting.
Create a file /tmp/nullcheck containing:
'null'
create table testnull (test varchar(10));
copy 1 records into testnull from '/tmp/nullcheck' USING DELIMITERS '\n', '''';
select * from testnull will give now an empty value.
While: insert into testnull values('null'); will result into the string 'null' inside the table.
The actual observation was that anything starting with 'nu...' would become a null variable; but outside the OSM insert script I cannot reproduce this behavior. The expected behavior would be that 'null' would be just the string. While the quoteless variant would get into NULL.
## Comment 11336
Date: 2009-03-22 22:38:35 +0100
From: @skinkie
Other (worse) example now works too:
CREATE TABLE "sys"."node_tags" (
"node" int,
"k" varchar(255),
"v" varchar(1024)
);
/tmp/nulltest:
1, 'test', 'Nullen RA'
COPY 1 RECORDS INTO node_tags from '/tmp/nulltest' USING DELIMITERS ',', '\n', '''';
sql>select * from node_tags;
+------+------+---+
| node | k | v |
+======+======+===+
| 1 | test | n |
: : : u :
: : : l :
: : : l :
+------+------+---+
1 tuple
## Comment 11337
Date: 2009-04-01 17:35:35 +0200
From: @sjoerdmullender
This was fixed.
I added a test sql/src/test/BugTracker-2009/Tests/nullstr.SF-2704016.sql.
## Comment 11338
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2704016 at http://sourceforge.net/support/tracker.php?aid=2704016
## Comment 21470
Date: 2015-11-06 11:38:10 +0100
From: @swingbit
This issue seems to pop up again in Jul2015 (tested on 11.21.6):
$ cat temp.data
CREATE TABLE x (a CLOB);
COPY 3 RECORDS INTO x FROM STDIN USING DELIMITERS ',', '\n', '\'';
'null'
'aap'
'beer'
SELECT * FROM x WHERE a IS NULL;
DROP TABLE x;
$ mclient -lsql -p50110 test001 < temp.data
operation successful
3 affected rows
+------+
| a |
+======+
| null |
+------+
1 tuple
operation successful
## Comment 21618
Date: 2015-11-28 17:31:21 +0100
From: MonetDB Mercurial Repository <<hg>>
Changeset [366cebe9e451](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=366cebe9e451) made by Niels Nes <niels@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=366cebe9e451](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=366cebe9e451)
Changeset description:
allow null in strings, fixes bug #2014 (again).
## Comment 21619
Date: 2015-11-28 17:31:43 +0100
From: @njnes
allow for null's in copy into strings
| 'null' from copy into gets wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/2014/comments | 0 | 2020-11-30T10:16:41Z | 2024-06-27T11:38:40Z | https://github.com/MonetDB/MonetDB/issues/2014 | 753,345,761 | 2,014 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-20 09:26:42 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2009-03-23 09:44:14 +0100
## Comment 11332
Date: 2009-03-20 21:26:42 +0100
From: @mlkersten
After rebuilding the HEAD from scratch I get the following:
MonetDB server v5.11.0, based on kernel v1.29.0
Serving database 'demo', 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- 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/monet5//Linux/etc/monetdb5.conf)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.29.0 loaded
>select * from tables;
mserver5: /ufs/mk/monet5//package/MonetDB/src/gdk/gdk_bbp.mx:1773: BBPkeepref: Assertion `BBP[(((int)(i))>0?((int)(i)):-((int)(i)))].refs' failed.
Aborted
## Comment 11333
Date: 2009-03-23 21:44:14 +0100
From: @mlkersten
It appeared there was still some experimental code lying around.
## Comment 11334
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2698421 at http://sourceforge.net/support/tracker.php?aid=2698421
| SQL: Server crash | https://api.github.com/repos/MonetDB/MonetDB/issues/2013/comments | 0 | 2020-11-30T10:16:38Z | 2024-06-28T13:27:03Z | https://github.com/MonetDB/MonetDB/issues/2013 | 753,345,727 | 2,013 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-20 08:37:32 +0100
From: Wouter Alink <<alink>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 01:53:55 +0200
## Comment 11328
Date: 2009-03-20 20:37:32 +0100
From: Wouter Alink <<alink>>
With a document with 100000 patents the following happens when shredding it:
$ ls -l patent_100000_problem_data.xml
-rw-r--r-- 1 roberto ins 6139885886 2009-03-20 17:44 patent_100000_problem_data.xml
$ echo 'pf:add-doc("/export/scratch0/roberto/lhm/patent_100000_problem_data.xml","bug.xml")' | mclient -lxq -p50030
MAPI = monetdb@localhost:50030
ACTION= read_line
QUERY = pf:add-doc("/export/scratch0/roberto/lhm/patent_100000_problem_data.xml","bug.xml")
ERROR = Connection terminated
On the server side an assertion is raised:
$ Mserver --dbfarm=/export/scratch0/roberto/lhm/dbfarm_xquery_2 --dbinit="module(pathfinder);" --set mapi_port=50030
MonetDB Server v4.29.0
based on GDK v1.29.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 32bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.29.0 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50031/admin
MonetDB>Mserver: /export/scratch0/roberto/MonetDB/src/MonetDB/src/gdk/gdk_atoms.mx:2097: strPut: Assertion `h->free + sizeof(var_t) <= ((var_t) 2147483647)' failed.
Aborted
It is the exact same document that gave the entity reference loop on the LDC. It is reproducable (got exactly the same result twice). The data cannot be made publicly available, but will be in the private lhm-testweb soon.
Is it perhaps a oid32 boundary we hit? Or is it something else?
## Comment 11329
Date: 2009-03-20 22:32:32 +0100
From: @sjoerdmullender
You're using 32 bit oids, and the type which is used to point into the string heap is based on oid, i.e. 32 bits. Your file is 6 GB in size, presumably most of it text, so that won't fit into 32 bits.
Try this with 64 bit oid.
This probably shouldn't fail with an assertion, though.
## Comment 11330
Date: 2009-04-07 13:53:55 +0200
From: @peterboncz
fixed: it gives an error now
## Comment 11331
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2698327 at http://sourceforge.net/support/tracker.php?aid=2698327
| XQ/GDK: strPut: Assertion failed | https://api.github.com/repos/MonetDB/MonetDB/issues/2012/comments | 0 | 2020-11-30T10:16:35Z | 2024-06-27T11:38:38Z | https://github.com/MonetDB/MonetDB/issues/2012 | 753,345,683 | 2,012 |
[
"MonetDB",
"MonetDB"
] | Date: 2009-03-19 09:10:00 +0100
From: Hans <<hans_0_>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-08-05 02:17:12 +0200
## Comment 11314
Date: 2009-03-19 09:10:00 +0100
From: Hans <<hans_0_>>
The following xquery fails, using Monet4 Nov 2008 SP2.
$ cat error.xq
let $result := (let $items := doc("consumer04.xml")//properties/..
let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
for $i in $items[properties/content]
where some $x in $values satisfies $x=$i/properties/content
return $i)
let $attrs := distinct-values(
for $j in $result/properties/*
return name($j)
)
let $props := doc("elements.xml")//property[@name]
let $subprops := doc("elements.xml")//subproperty[@name]
return element result {
element matches { count($result) },
element attributes {
let $usedprops := for $attr in $attrs return $props[@name=$attr]
for $prop in $usedprops/.
return element { string($prop/@name) } {
attribute format { $prop/format },
attribute unit { $prop/unit },
attribute description { $prop/description },
for $subprop in $prop/subproperty
let $sub := $subprops[@name=$subprop]
return element { string(exactly-one($sub/@name)) } {
attribute format { $sub/format },
attribute unit { $sub/unit },
attribute description { $sub/description }
}
}
}
}
<>
$ mclient -p55555 -lx -t error.xq > error.xml
MAPI = monetdb@localhost:55555
QUERY = let $result := (let $items := doc("consumer04.xml")//properties/..
ERROR = !ERROR: GDKmallocmax: failed for 238795816 bytes
!ERROR: GDKload: failed name=61/6151, ext=head
!ERROR: CMDleftjoin: operation failed.
!ERROR: BBPdecref: 1000000017_rid_level does not have pointer fixes.
!ERROR: BBPdecref: 1000000017_rid_prop does not have pointer fixes.
!ERROR: BBPdecref: 1000000017_prop_text does not have pointer fixes.
!ERROR: BBPdecref: 1000000017_prop_val does not have pointer fixes.
!ERROR: BBPdecref: 1000000017_attr_qn does not have pointer fixes.
!ERROR: BBPdecref: 1000000017_attr_prop does not have pointer fixes.
$ cat error.xml
GDKmalloc(180627422248) fail => BBPtrim(enter) usage[mem=148149976,vm=902317056]
GDKmalloc(180627422248) fail => BBPtrim(ready) usage[mem=36756832,vm=583467008]
Timer 34246.875 msec
$
The used documents were sent earlier in March 2009 to Jan (Tuebingen, PF WIKI) and to Sjoerd (CWI, testset).
## Comment 11315
Date: 2009-03-19 10:31:04 +0100
From: @drstmane
With Nov2008 release branch (post Nov2008-SP2 release):
$ Mserver --dbinit='module(pathfinder);'
MonetDB Server v4.26.5
based on GDK v1.26.5
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.26.5 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
$ mclient -lx
xquery>let $items := doc("consumer04.xml")//properties/..
more>return count($items)
more><>
1156921
xquery>let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
more>return count($values)
more><>
1
xquery>let $items := doc("consumer04.xml")//properties/..
more>let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
more>return count($items[properties/content])
more><>
146457
xquery>let $items := doc("consumer04.xml")//properties/..
more>let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
more>let $result := (
more>for $i in $items[properties/content]
more>where some $x in $values satisfies $x=$i/properties/content
more>return $i
more>)
more>return count($result)
more><>
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = let $items := doc("consumer04.xml")//properties/..
ERROR = Connection terminated
MonetDB>Mserver: /ufs/manegold/_/scratch0/Monet/Testing/Stable_Nov2008/source/MonetDB/src/gdk/gdk_bbp.mx:1593: decref: Assertion `0' failed.
Aborted
## Comment 11316
Date: 2009-03-19 10:42:27 +0100
From: @drstmane
With Feb2009 release branch (post Feb2009 release)
$ Mserver --dbinit='module(pathfinder);'
MonetDB Server v4.28.0
based on GDK v1.28.1
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs; dynamically linked.
Visit http://monetdb.cwi.nl/ for further information.
PF/Tijah module v0.9.0 loaded. http://dbappl.cs.utwente.nl/pftijah
MonetDB/XQuery module v0.28.1 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
$ mclient -lx
xquery>let $items := doc("consumer04.xml")//properties/..
more>return count($items)
more><>
1156921
xquery>let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
more>return count($values)
more><>
1
xquery>let $items := doc("consumer04.xml")//properties/..
more>let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
more>return count($items[properties/content])
more><>
146457
xquery>let $items := doc("consumer04.xml")//properties/..
more>let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
more>let $result := (
more>for $i in $items[properties/content]
more>where some $x in $values satisfies $x=$i/properties/content
more>return $i
more>)
more>return count($result)
more><>
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
26353 manegold 20 0 337g 7.1g 7.1g R 32.1 91.3 2:09.11 Mserver
^^^^ ^^^^ ^^^^
... stopped (I killed client & server) after 10 min without result ...
## Comment 11317
Date: 2009-03-19 10:44:53 +0100
From: @drstmane
ps: in both cases (Nov2008 & Feb2009) I locally applied the following patch to avoid
[ 2668437 ] PF runtime: parent step produces not/wrongly sorted result
https://sourceforge.net/tracker/index.php?func=detail&aid=2668437&group_id=56967&atid=482468
$ cvs diff pathfinder/runtime/ll_upwards.mx
Index: pathfinder/runtime/ll_upwards.mx
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/runtime/ll_upwards.mx,v
retrieving revision 1.32
diff -u -r1.32 ll_upwards.mx
--- pathfinder/runtime/ll_upwards.mx 8 Jan 2009 16:54:18 -0000 1.32
+++ pathfinder/runtime/ll_upwards.mx 19 Mar 2009 09:43:04 -0000
@@ -571,7 +571,7 @@
}
bn->tsorted = 0;
if (niters == 1) {
- bn->tsorted = GDK_SORTED;
+ /*bn->tsorted = GDK_SORTED;*/
BATkey(BATmirror(bn), 1);
}
*ret = bn;
## Comment 11318
Date: 2009-03-19 10:59:09 +0100
From: @drstmane
BTW:
What the intended and/or factual difference between your
let $result := (
let $items := doc("consumer04.xml")//properties/..
let $values := distinct-values((doc("consumer04.xml")//properties/..)/properties/content)
for $i in $items[properties/content]
where some $x in $values satisfies $x=$i/properties/content
return $i
)
and a simple
xquery>let $result := doc("consumer04.xml")//*[properties/content]
more>return count($result)
more><>
146457
or
xquery>let $result := doc("consumer04.xml")//properties/content/../..
more>return count($result)
more><>
146457
?
The latter two work fine with Nov2008 & Feb2009 and make your original query work fine with both, too, (at least with my below patch applied), returning
<result><matches>146457</matches><attributes><name description="Removed content" unit="" format="xs:string"/><path description="Removed content" unit="" format="xiraf:path"/><content description="Removed content" unit="" format="xiraf:complex"><utf16le description="Removed content" unit="" format="xs:string"/><utf8 description="Removed content" unit="" format="xs:string"/><int32le description="Removed content" unit="" format="xs:integer"/><int64le description="Removed content" unit="" format="xs:integer"/></content><stream description="Removed content" unit="" format=""/><size description="Removed content" unit="bytes" format="xs:integer"/></attributes></result>
## Comment 11319
Date: 2009-03-19 11:09:33 +0100
From: @drstmane
Using your "customer04-small.xml", both your original query and both of my proposed alternatives produce the same ("empty"?) result, with both Feb2009 & Nov2008 and both ALG & MPS:
<result><matches>0</matches><attributes/></result>
## Comment 11320
Date: 2009-03-19 11:11:50 +0100
From: @drstmane
Just for completeness, as can be read from my Mserver welcome messages, I'm working on 64-bit Linux.
## Comment 11321
Date: 2009-03-19 15:33:09 +0100
From: Hans <<hans_0_>>
Reply to question from stmane Date: 2009-03-19 10:09
consumer04-small.xml is a very limited intersection of the bigger consumer04.xml. A lot of 'directories' from the original system were left out in order to create a small document to fit in the nightly test (less than 10 MB). As a result no 'content' type properties are present there, hence the zero size result set.
Reply to question from stmane Date: 2009-03-19 09:59
Most of our xqueries are generated by putting a lot of small pieces together. These xqueries are a result of a filter description and a required result set. As a result most xqueries we send to Mserver are not optimized. We realize there could be a performance improvement, if we always send the most optimal xquery. The drawback would be a lot of development costs.
## Comment 11322
Date: 2009-03-27 19:01:27 +0100
From: @peterboncz
Jan, it seems that an equi-join is not detected here.. it seems a pretty normal pattern though. Could you check what gies wrong?
## Comment 11323
Date: 2009-04-07 14:53:34 +0200
From: @peterboncz
for $i in $items[properties/content]
where some $x in $values satisfies $x=$i/properties/content
return $i)
is a join of 86K nodes with itself, and all have the same value: "" (the empty string).
Therefore, there are 9G result tuples for the join. Therefore a runtime error occurs.
So, the direct problem is that this query (on this data, with all values equal) produces a very large intermediate result. It should be rewritten or avoided by the application.
However, this "where some satisfies" currently uses a normal join strategy, whereas a semijoin strategy would allow to push duplicate elimination on the outer side under the join. That would turn this join into a 86K x 1 join and solve the problem.
The algebra plans has this opportunity pretty openly exposed, so Jan figured it would be possible to put an optimization in.
turning this over to Jan, then
## Comment 11324
Date: 2009-04-07 15:27:23 +0200
From: Jan Rittinger <<jan.rittinger>>
Added an optimized translation for thetajoins that takes semijoins into account. (Query now runs in the HEAD.)
## Comment 11325
Date: 2009-06-23 11:46:13 +0200
From: @drstmane
Hans,
does this problem persist with the Feb2009-SP2 release and/or the May2009 release?
If not, I guess we could close this bug report --- after adding a respective test to our Xiraf test suite ...
Stefan
## Comment 11326
Date: 2009-08-05 14:17:12 +0200
From: @sjoerdmullender
I added the test from the report to the Xiraf "large" test set.
Closing since nobody seems to disagree with Stefan's assessment.
## Comment 11327
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2693776 at http://sourceforge.net/support/tracker.php?aid=2693776
| xquery fails: memory allocation | https://api.github.com/repos/MonetDB/MonetDB/issues/2011/comments | 0 | 2020-11-30T10:16:31Z | 2024-06-27T11:38:37Z | https://github.com/MonetDB/MonetDB/issues/2011 | 753,345,635 | 2,011 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.