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-01-04 11:16:17 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2009-01-26 08:20:57 +0100
## Comment 10748
Date: 2009-01-04 11:16:17 +0100
From: @mlkersten
Reported by farkashon@hotmail.com
When I use COPY INTO with a count query, monetDB crashes.
For example:
copy select count (*) into 'C:\\copyinto.txt' using delimiters ',';
Gives me the following result and kills the server:
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = copy select count (*) into 'C:\\copyinto.txt' using delimiters ',';
ERROR = Connection terminated
Confirmed. Test added in BugTracker-2008
## Comment 10749
Date: 2009-01-05 21:26:25 +0100
From: @romulogoncalves
The name of the test is:
copy-count.SF-2485215.sql
## Comment 10750
Date: 2009-01-26 20:20:57 +0100
From: @njnes
fixed (added handling of count (single value) results in copy into
## Comment 10751
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2485215 at http://sourceforge.net/support/tracker.php?aid=2485215
| SQL: copy aggregate fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1910/comments | 0 | 2020-11-30T10:07:24Z | 2024-06-27T11:34:01Z | https://github.com/MonetDB/MonetDB/issues/1910 | 753,339,087 | 1,910 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-29 10:27:34 +0100
From: John van Schie <<johnvanschie>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-02-16 03:54:22 +0100
## Comment 10742
Date: 2008-12-29 10:27:34 +0100
From: John van Schie <<johnvanschie>>
We use the MonetDB Nov 2008 SP1 server supplied by the Fedora 9 RPM's.
When we execute the following query, which we believe is valid, it results in the following error:
Query:
element result {
if (distinct-values(exactly-one(doc("bookmarks.xml"))//*)) then 1 else 2
}
Mclient output:
xquery>\</media/disk/querylog
MAPI = monetdb@localhost:51240
QUERY = element result {
ERROR = !fatal error: attribute 'item' with type '0x20' not found in environment
It executes without a problem, when we rewrite the query to the following:
Query:
element result {
if (not(empty(distinct-values(exactly-one(doc("bookmarks.xml"))//*)))) then 1 else 2
}
Mclient output:
xquery>\</media/disk/querylog.workaround
<result>1</result>
## Comment 10743
Date: 2008-12-29 12:07:04 +0100
From: @drstmane
With assertions disabled (as in the RPMs), I get the same error:
$ pf /tmp/ebv.SF-2474519-KO.xq >/dev/null
fatal error: attribute 'item' with type '0x20' not found in environment
With assertions enabled (default when compiled from CVS sources), I get:
$ pf /tmp/ebv.SF-2474519-KO.xq
pf: /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/pathfinder/compiler/algebra/logical.c:1831: PFla_not: Assertion `PFprop_type_of (n, att) == 0x00000020' failed.
Aborted
With the old / deprecated MPS back-end (cf., `pf -M` / `mclient -g` / '\g' command on mclient prompt), the query compiles fine:
$ pf -M /tmp/ebv.SF-2474519-KO.xq | wc
718 2994 31177
## Comment 10744
Date: 2009-02-16 15:37:35 +0100
From: Jan Rittinger <<jan.rittinger>>
Fixed in CVS.
## Comment 10745
Date: 2009-02-16 15:40:15 +0100
From: Jan Rittinger <<jan.rittinger>>
BTW: The two queries query something different. The first one returns a runtime error if there are more than one values and looks at the value to decide the outcome. The second query returns true if there is 1 or more resulting values.
## Comment 10746
Date: 2009-02-16 15:54:22 +0100
From: Jan Rittinger <<jan.rittinger>>
Test added.
## Comment 10747
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2474519 at http://sourceforge.net/support/tracker.php?aid=2474519
| Effective boolean value of sequence results in an error | https://api.github.com/repos/MonetDB/MonetDB/issues/1909/comments | 0 | 2020-11-30T10:07:21Z | 2024-06-27T11:34:00Z | https://github.com/MonetDB/MonetDB/issues/1909 | 753,339,053 | 1,909 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-27 06:13:01 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2008-12-28 08:55:50 +0100
## Comment 10738
Date: 2008-12-27 18:13:01 +0100
From: @mlkersten
The COPY statement does not respect the VARCHAR limits
Test added
## Comment 10739
Date: 2008-12-27 18:24:50 +0100
From: @romulogoncalves
The test was added at:
sql/src/test/BugTracker-2008/Tests/
And its name is:
varchar.SF-2471371.sql
Like this it is easier to find it ;)
## Comment 10740
Date: 2008-12-28 20:55:50 +0100
From: @njnes
added bound checks
## Comment 10741
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2471371 at http://sourceforge.net/support/tracker.php?aid=2471371
| SQL: varchar bounds should be obeyed | https://api.github.com/repos/MonetDB/MonetDB/issues/1908/comments | 0 | 2020-11-30T10:07:18Z | 2024-06-27T11:33:59Z | https://github.com/MonetDB/MonetDB/issues/1908 | 753,339,019 | 1,908 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-26 12:25:50 +0100
From: @mlkersten
To: @njnes
Version: -- development
Last updated: 2008-12-30 06:41:49 +0100
## Comment 10734
Date: 2008-12-26 12:25:50 +0100
From: @mlkersten
The load_with_offset file contains erroneous input, which is not properly detected.
CREATE TABLE my_test (
col1 INT,
col2 INT,
col3 INT,
col4 VARCHAR(1),
col5 VARCHAR(1)
) ;
COPY 5 OFFSET 5 RECORDS INTO my_test FROM stdin USING DELIMITERS '|','\n' NULL as '';
123|1.01||aaa|bbb
553|.02||aaa|bbb
223|2.03||aaa|bbb
## Comment 10735
Date: 2008-12-27 18:22:31 +0100
From: @mlkersten
test file added:
BugTracker-2008/Tests/copy-format.SF-2468513.sql
## Comment 10736
Date: 2008-12-30 18:41:49 +0100
From: @njnes
we have stricter checking now
## Comment 10737
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2468513 at http://sourceforge.net/support/tracker.php?aid=2468513
| SQL: copy into does not detect syntax errors | https://api.github.com/repos/MonetDB/MonetDB/issues/1907/comments | 0 | 2020-11-30T10:07:14Z | 2024-06-27T11:33:58Z | https://github.com/MonetDB/MonetDB/issues/1907 | 753,338,984 | 1,907 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-25 05:48:39 +0100
From: z lh <<zlh>>
To: @njnes
Version: -- development
Last updated: 2008-12-27 10:29:43 +0100
## Comment 10730
Date: 2008-12-25 17:48:39 +0100
From: z lh <<zlh>>
create table t1 ( a int, b int ) ;
create table t2 ( a int, b int ) ;
insert into t1 values ( 1, 1 ), ( 2, 2 ) ;
insert into t2 values ( 1, 1 ) ;
--the result of
select * from t1 where exists( select * from t2 where t2.a = t1.a ) or t1.b > 0 ;
--is the same as the result of
select * from t1 where exists( select * from t2 where t2.a = t1.a ) and t1.b > 0 ;
--but the 'OR' should return two records.
## Comment 10731
Date: 2008-12-27 16:45:08 +0100
From: @njnes
test added to src/test/BugTracker-2008/Tests/subselect_with_or.SF-2466725.sql
## Comment 10732
Date: 2008-12-27 22:29:43 +0100
From: @njnes
fixed by proper or handling
## Comment 10733
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2466725 at http://sourceforge.net/support/tracker.php?aid=2466725
| SubSelect with Outer Reference, result is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1906/comments | 0 | 2020-11-30T10:07:11Z | 2024-06-27T11:33:57Z | https://github.com/MonetDB/MonetDB/issues/1906 | 753,338,937 | 1,906 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-23 06:54:11 +0100
From: marspluto <<juntezhang>>
To: Henning Rode <<hrode>>
Version: -- development
Last updated: 2009-06-30 09:41:15 +0200
## Comment 10724
Date: 2008-12-23 18:54:11 +0100
From: marspluto <<juntezhang>>
I have this query:
declare function tijah:getINEXPath ( $node as node() ) as xs:string { let
$pathelements := for $a in $node/ancestor-or-self::* return if ( name($a) =
"ead" ) then "/ead[1]" else concat(name($a), "[" ,
count($a/preceding-sibling::*[name()=name($a)]) + 1, "]") return
string-join( $pathelements, "/" ) }; let $options := let $start := 1 let
$end := 24 let $query_text := tijah:tokenize("groningen") let $query_nexi
:= concat("//ead[about(., ", $query_text, ")]") let $qid :=
tijah:queryall-id($query_nexi, $options) let $nodes := tijah:nodes($qid)
let $result := for $node in $nodes return {
data($node/ancestor-or-self::ead/@file) } { tijah:getINEXPath($node) }
{ $node/normalize-space() } let $total := count($result) return { for
$res at $rankGlobal in $result where( $rankGlobal >= $start and $rankGlobal
<= $end ) return { $res } }
Then I get this error:
ERROR = !ERROR: interpret: no matching MIL operator to
'tj_query_handler(bit, BAT[void,BAT], BAT[oid,BAT], BAT[void,BAT],
BAT[oid,oid], BAT[oid,BAT], BAT[oid,lng], BAT[oid,dbl], BAT[oid,str],
void)'.
!MAYBE YOU MEAN:
! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT],
BAT[void,BAT], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl],
BAT[void,str], BAT[void,BAT]) : BAT[void,BAT]
When I restart the Mserver, I can again query 1 time, and then I am getting that error again. This is not a very useful feature of PF/Tijah, because obviously you would want to query more than 1 time in a single Mserver session. So I hope it can be omitted, thanks.
## Comment 10725
Date: 2008-12-24 15:48:14 +0100
From: @drstmane
A the correct query and an instance of the data has been attached to
[ 2461857 ] Error: !fatal error: Algebra implementation for function `p
https://sourceforge.net/tracker/index.php?func=detail&aid=2461857&group_id=56967&atid=482468
## Comment 10726
Date: 2009-01-30 09:41:28 +0100
From: Henning Rode <<hrode>>
the bug is occurring only when using the MPS version of monetdb/query. since we do not support this version any more, and Junte found a solution to write and execute his query with the algebra version, i will close this bug report without fixing it.
## Comment 10727
Date: 2009-02-16 12:07:24 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test for the "work around" with the ALG back-end
## Comment 10728
Date: 2009-06-30 09:41:15 +0200
From: Henning Rode <<hrode>>
since this bug is related to the old MPS version of pathfinder it won't get fixed. the same type of queries have been succesfully tested on the algebra version of pathfinder.
## Comment 10729
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2462165 at http://sourceforge.net/support/tracker.php?aid=2462165
| PF/Tijah: cannot query the 2nd time in millprint_summer | https://api.github.com/repos/MonetDB/MonetDB/issues/1905/comments | 0 | 2020-11-30T10:07:09Z | 2024-06-28T13:27:54Z | https://github.com/MonetDB/MonetDB/issues/1905 | 753,338,916 | 1,905 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-23 04:57:19 +0100
From: marspluto <<juntezhang>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-02-16 03:55:37 +0100
## Comment 10713
Date: 2008-12-23 16:57:19 +0100
From: marspluto <<juntezhang>>
I upgraded to the latest stable version, because I wanted to use the standard XQuery algebra, but when I execute a query, I get this error:
Error: !fatal error: Algebra implementation for function `pf:string-value' is missing.
To prove that I am indeed using the latest stable version:
MonetDB Server v4.26.2
based on GDK v1.26.2
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-pc-linux-gnu/32bit 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.26.2 loaded (default back-end is 'algebra')
XRPC administrative console at http://127.0.0.1:50001/admin
I installed it from CVS. This problem does not occur when I use the milprint_summer backend.
## Comment 10714
Date: 2008-12-23 17:04:17 +0100
From: @drstmane
Which XQuer(y|ies) do trigger this error?
## Comment 10715
Date: 2008-12-23 17:15:14 +0100
From: @drstmane
Just for info, the code says:
========
/**
* Build up operator tree for built-in function 'pf:string-value'.
*/
struct PFla_pair_t
PFbui_pf_string_value (const PFla_op_t *loop, bool ordering,
struct PFla_pair_t *args)
{
/* We cannot cope with a mix of certain node kinds.
E.g. comments and element nodes are not distinguishable
in the algebra but still require a different treating in
the backend.
One solution could be to get all nodes with
desc-or-self::text() U attribute::* U self::pi() U self::comment
and then have a universal doc_access operator kind that
can cope with all these kinds.
The nicest solution however seems to be C primitive in
the runtime that implements string-value. (This would make
the algebra a lot easier to read and optimize.) */
PFoops (OOPS_FATAL,
"Algebra implementation for function "
"`pf:string-value' is missing.");
(void) loop; (void) ordering;
return args[0];
}
========
The question is, which XQuer(y|ies) (on what kind of data/document(s)) do(es) trigger this error?
(And why?)
## Comment 10716
Date: 2008-12-23 18:35:34 +0100
From: marspluto <<juntezhang>>
This is the query:
declare function tijah:getINEXPath ( $node as node() ) as xs:string { let $pathelements := for $a in $node/ancestor-or-self::* return if ( name($a) = "ead" ) then "/ead[1]" else concat(name($a), "[" , count($a/preceding-sibling::*[name()=name($a)]) + 1, "]") return string-join( $pathelements, "/" ) }; let $options := let $start := 1 let $end := 24 let $query_text := tijah:tokenize("groningen") let $query_nexi := concat("//ead[about(., ", $query_text, ")]") let $qid := tijah:queryall-id($query_nexi, $options) let $nodes := tijah:nodes($qid) let $result := for $node in $nodes return { data($node/ancestor-or-self::ead/@file) } { tijah:getINEXPath($node) } { $node/normalize-space() } let $total := count($result) return { for $res at $rankGlobal in $result where( $rankGlobal >= $start and $rankGlobal <= $end ) return { $res } }
When I use milprint_summer, I am also getting another error after executing the query the 2nd time:
ERROR = !ERROR: interpret: no matching MIL operator to 'tj_query_handler(bit, BAT[void,BAT], BAT[oid,BAT], BAT[void,BAT], BAT[oid,oid], BAT[oid,BAT], BAT[oid,lng], BAT[oid,dbl], BAT[oid,str], void)'.
!MAYBE YOU MEAN:
! tj_query_handler(bit, BAT[void,BAT], BAT[void,BAT], BAT[void,BAT], BAT[oid,any], BAT[oid,BAT], BAT[void,lng], BAT[void,dbl], BAT[void,str], BAT[void,BAT]) : BAT[void,BAT]
When I restart the Mserver, I can again query 1 time, and then I am getting that error again.
So nothing works for me anymore, neither milprint_summer nor algebra.
## Comment 10717
Date: 2008-12-23 18:48:13 +0100
From: @drstmane
Junte,
could you please file a separate bug report for the milprint_summer case (one bug per bug report / one bug report per bug ;-)), indicating that is appears to be a PF/tijah problem (the same seems to hold for the pf:string-value error reported here), and assign it to Jan Flokstra (jflokstra)?
Thanks!
Stefan
## Comment 10718
Date: 2008-12-23 18:55:58 +0100
From: marspluto <<juntezhang>>
Stefan, thanks!
If Jan needs more information, please let me know. I really would like to switch to algebra....
junte
## Comment 10719
Date: 2008-12-23 19:04:08 +0100
From: @drstmane
Is you query correct?
I get
parse error: syntax error, unexpected { on line 9, column 46 (next token is `{')
parse error: XQuery parsing failed
In case the SF bug tracker text rendering messes things up, please feel free to attach you query as file to the bug report...
## Comment 10720
Date: 2008-12-23 23:51:39 +0100
From: marspluto <<juntezhang>>
Oops, the correct query and an instance of my data has been attached.
junte
File Added: bug.zip
## Comment 10721
Date: 2008-12-24 11:07:02 +0100
From: Jan Rittinger <<jan.rittinger>>
I won't fix this problem in the next months to come as you can avoid your problem.
The problem here is function pftijah:nodes that returns the most generic type (node) which you then use with normalize-space (line 31 of your query – that triggers the string-value lookup).
You can avoid the problem by wrapping the return clause of the for loop over $nodes in a typeswitch that checks for the respective node-kinds (here e.g., 'typeswitch ($node) case $elem-node as element(ead) return '[$node/$elem-node]...' default return error ("unexpected node")').
## Comment 10722
Date: 2008-12-24 15:49:38 +0100
From: @drstmane
For the MPS/tijah problem, please see
[ 2462165 ] PF/Tijah: cannot query the 2nd time in millprint_summer
https://sourceforge.net/tracker/index.php?func=detail&aid=2462165&group_id=56967&atid=482468
## Comment 10723
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2461857 at http://sourceforge.net/support/tracker.php?aid=2461857
| Error: !fatal error: Algebra implementation for function `#p | https://api.github.com/repos/MonetDB/MonetDB/issues/1904/comments | 0 | 2020-11-30T10:07:04Z | 2024-06-28T13:27:53Z | https://github.com/MonetDB/MonetDB/issues/1904 | 753,338,860 | 1,904 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-23 10:03:16 +0100
From: @drstmane
To: Jan Flokstra <<jflokstra>>
Version: -- development
Last updated: 2008-12-24 03:43:20 +0100
## Comment 10709
Date: 2008-12-23 10:03:16 +0100
From: @drstmane
`make dist` (and hence `make rpm`) fail(s) for pathfinder, since probxml now seems to require the geom module, but is not (yet) told where to find it.
(See details below.)
In fact, module geom does not yet install the header files that are required to develop "on top of" module geom.
(Please do not hesitate to ask in case you need advice and/or help with fixing this one.)
From
http://www.ins.cwi.nl/~monet/permastore/2008-12-23/Current/dist-pathfinder-GNU.64.64.d.1-Fedora8.errors.htmll515 :
"
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel -c pf_config.h -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml -I../../runtime -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/../../runtime -I../../compiler/include -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/../../compiler/include -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4 -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/monet -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/plain -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/contrib -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/mapi -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/calibrator -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB/common -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB/gdk -I/usr/include/libxml2 -mil geoxml.m > geoxml.mil
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel: "/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/geoxml.mx", line 27, Module not found at "4" of geom.
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel: "/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/geoxml.mx", line 27, syntax error at "1" of ;.
Found 2 syntax errors.
make[2]: *** [geoxml.mil] Error 1
make[2]: *** Deleting file `geoxml.mil'
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel -c pf_config.h -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml -I../../runtime -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/../../runtime -I../../compiler/include -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/../../compiler/include -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4 -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/monet -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/plain -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/contrib -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/mapi -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/calibrator -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB/common -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB/gdk -I/usr/include/libxml2 -proto geoxml.m > geoxml.proto.h
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel: "/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/geoxml.mx", line 27, Module not found at "4" of geom.
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel: "/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/geoxml.mx", line 27, syntax error at "1" of ;.
Found 2 syntax errors.
make[2]: *** [geoxml.proto.h] Error 1
make[2]: *** Deleting file `geoxml.proto.h'
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel -c pf_config.h -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml -I../../runtime -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/../../runtime -I../../compiler/include -I/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/../../compiler/include -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4 -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/monet -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/plain -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/contrib -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/mapi -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB4/.GNU.64.64.d.1-Fedora8/include/MonetDB4/calibrator -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB/common -I/scratch/monet.GNU.64.64.d.1.30790/MonetDB/.GNU.64.64.d.1-Fedora8/include/MonetDB/gdk -I/usr/include/libxml2 -glue geoxml.m > geoxml.glue.c
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel: "/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/geoxml.mx", line 27, Module not found at "4" of geom.
/scratch/monet.GNU.64.64.d.1.30790/buildtools/.GNU.64.64.d.1-Fedora8/bin/mel: "/scratch/monet.GNU.64.64.d.1.30790/pathfinder/modules/probxml/geoxml.mx", line 27, syntax error at "1" of ;.
Found 2 syntax errors.
make[2]: *** [geoxml.glue.c] Error 1
make[2]: *** Deleting file `geoxml.glue.c'
"
## Comment 10710
Date: 2008-12-23 10:39:02 +0100
From: Jan Flokstra <<jflokstra>>
By some 'magic' CVS mishap the probxml repository was filled with the geoxml stuff. I corrected this and the probxml module should now again only contain the probxml.mx module. This should fix the problem.
## Comment 10711
Date: 2008-12-24 15:43:20 +0100
From: @drstmane
Seems to work fine, again.
Thanks for the quick fix.
## Comment 10712
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2460953 at http://sourceforge.net/support/tracker.php?aid=2460953
| `make dist` (and hence `make rpm`) fails for pathfinder | https://api.github.com/repos/MonetDB/MonetDB/issues/1903/comments | 0 | 2020-11-30T10:07:01Z | 2024-06-27T11:33:54Z | https://github.com/MonetDB/MonetDB/issues/1903 | 753,338,826 | 1,903 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-23 09:52:12 +0100
From: @drstmane
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-12-23 10:27:49 +0100
## Comment 10705
Date: 2008-12-23 09:52:12 +0100
From: @drstmane
Subject: Compiling pathfinder (Current) failed on Int.64.32.d.1-Fedora8 Int.64.64.d.1-Fedora8 Int.64.64.d.1-RedHat4WS
prop_rec_delta.c:81: argument is incompatible with corresponding format string conversion
79 case la_internal_op:
80 case la_dummy:
81 fprintf(stderr,"%i\n", n->kind);
82 PFoops (OOPS_FATAL,
83 "This property checking phase should be run "
icc -no-gcc -fPIC -DHAVE_CONFIG_H -I. -I../../.. -I/scratch/monet.Int.64.32.d.1.30790/pathfinder/compiler/algebra/prop -I/scratch/monet.Int.64.32.d.1.30790/pathfinder/compiler/algebra/prop -I../../include
+-I/scratch/monet.Int.64.32.d.1.30790/pathfinder/compiler/algebra/prop/../../include -I/scratch/monet.Int.64.32.d.1.30790/MonetDB/.Int.64.32.d.1-Fedora8/include/MonetDB
+-I/scratch/monet.Int.64.32.d.1.30790/MonetDB/.Int.64.32.d.1-Fedora8/include/MonetDB/common -I/scratch/monet.Int.64.32.d.1.30790/MonetDB/.Int.64.32.d.1-Fedora8/include/MonetDB/gdk -DLIBPROP -we140 -wd1418 -Wall -w2 -std=c99 -O3 -we266 -Werror
+-wd1418,1419,981,810,193,111,1357,1572,1599 -wd279 -c /scratch/monet.Int.64.32.d.1.30790/pathfinder/compiler/algebra/prop/prop_rec_delta.c -DPIC -o .libs/libprop_la-prop_rec_delta.o
/scratch/monet.Int.64.32.d.1.30790/pathfinder/compiler/algebra/prop/prop_rec_delta.c(81): error 181: argument is incompatible with corresponding format string conversion
fprintf(stderr,"%i\n", n->kind);
^
compilation aborted for /scratch/monet.Int.64.32.d.1.30790/pathfinder/compiler/algebra/prop/prop_rec_delta.c (code 2)
make[8]: *** [libprop_la-prop_rec_delta.lo] Error 1
http://www.ins.cwi.nl/~monet/permastore/2008-12-23/Current/make-pathfinder-Int.64.32.d.1-Fedora8.errors.htmll355
CVS committers: manegold@cwi.nl sjoerd@cwi.nl
module maintainers: lsidir@cwi.nl zhang@cwi.nl henning@cwi.nl
An identical error message was detected on the following systems:
Int.64.32.d.1-Fedora8 Int.64.64.d.1-Fedora8 Int.64.64.d.1-RedHat4WS
This might just be due to a left-over debugging fprintf statement?
## Comment 10706
Date: 2008-12-23 09:54:04 +0100
From: @drstmane
cf.
http://www.ins.cwi.nl/~monet/permastore/2008-12-23/Current/make-pathfinder-Int.64.32.d.1-Fedora8.errors.htmll351
## Comment 10707
Date: 2008-12-23 10:27:49 +0100
From: Jan Rittinger <<jan.rittinger>>
I overlooked that one -- thanks Stefan for the reminder
## Comment 10708
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2460935 at http://sourceforge.net/support/tracker.php?aid=2460935
| Pathfinder fails to compile with icc | https://api.github.com/repos/MonetDB/MonetDB/issues/1902/comments | 0 | 2020-11-30T10:06:57Z | 2024-06-27T11:33:53Z | https://github.com/MonetDB/MonetDB/issues/1902 | 753,338,788 | 1,902 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-23 08:03:35 +0100
From: David Wung <<fivecolor>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-12-23 10:34:32 +0100
## Comment 10701
Date: 2008-12-23 08:03:35 +0100
From: David Wung <<fivecolor>>
In new version Nov2008, I found timer in trace result was lost.
If this is not bug, how can I get the trace time in new version.
Thank you.
## Comment 10702
Date: 2008-12-23 10:34:32 +0100
From: @mlkersten
The timing of SQL execution is described in
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/TRACE-Statement.htmlTRACE-Statement
and
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/Query-History.html
## Comment 10703
Date: 2008-12-23 11:02:29 +0100
From: @romulogoncalves
I think here he is talking about the execution time for each instruction when you trace a query, e.g.
Trace select 1;
Yes there was a bug, but it is fixed and the fix is available in the latest bug release
Nov2008-SP1 ;)
## Comment 10704
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2460710 at http://sourceforge.net/support/tracker.php?aid=2460710
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.
| Time loss in trace result | https://api.github.com/repos/MonetDB/MonetDB/issues/1901/comments | 0 | 2020-11-30T10:06:54Z | 2024-06-28T13:27:53Z | https://github.com/MonetDB/MonetDB/issues/1901 | 753,338,753 | 1,901 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-22 03:18:07 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-12-27 11:51:33 +0100
## Comment 10697
Date: 2008-12-22 03:18:07 +0100
From: @skinkie
The following query operates on a table with less than 300k of records.
create table test (lhs varchar(16), rhs varchar(16));
select rhs,
(lhs like 'A%' OR lhs like 'B%' OR lhs like 'C%' OR lhs like 'D%' OR lhs like 'E%' OR lhs like 'F%' OR lhs like 'G%' OR lhs like 'H%' OR lhs like 'I%' OR lhs like 'J%' OR lhs like 'K%' OR lhs like 'L%' OR lhs like 'M%' OR lhs like 'N%' OR lhs like 'O%' OR lhs like 'P%' OR lhs like 'Q%' OR lhs like 'R%' OR lhs like 'S%' OR lhs like 'T%' OR lhs like 'U%' OR lhs like 'V%' OR lhs like 'W%' OR lhs like 'X%' OR lhs like 'Y%' OR lhs like 'Z%'),
(lower(lhs) like 'a%'),
(lower(lhs) like 'in%'),
(lower(lhs) like 'un%'),
(lower(lhs) like 'non%'),
((lower(lhs) like '%ise_') OR (lower(lhs) like '%ize_')),
(lower(lhs) like '%ly_'),
(lower(lhs) like '%s_'),
(lower(lhs) like '%ed_'),
(lower(lhs) like '%ing_'),
(lower(lhs) like '%-%_'),
(lower(lhs) like '%-_'),
(lower(lhs) like '%.%_'),
(lower(lhs) like '%._')
from test where lhs like '%!_' escape '!';
The brokeness is the SELECT part with _ it should be !_.
But interestingly; when it is done right I cannot get output:
/opt/monetdb/bin/mclient -lsql
sql>select rhs,
more>(lhs like 'A%' OR lhs like 'B%' OR lhs like 'C%' OR lhs like 'D%' OR lhs like 'E%' OR lhs like 'F%' OR lhs like 'G%' OR lhs like 'H%' OR lhs like 'I%' OR lhs like 'J%' OR lhs like 'K%' OR lhs like 'L%' OR lhs like 'M%' OR lhs like 'N%' OR lhs like 'O%' OR lhs like 'P%' OR lhs like 'Q%' OR lhs like 'R%' OR lhs like 'S%' OR lhs like 'T%' OR lhs like 'U%' OR lhs like 'V%' OR lhs like 'W%' OR lhs like 'X%' OR lhs like 'Y%' OR lhs like 'Z%'),
more>(lower(lhs) like 'a%'),
more>(lower(lhs) like 'in%'),
more>(lower(lhs) like 'un%'),
more>(lower(lhs) like 'non%'),
more>((lower(lhs) like '%ise!_') OR (lower(lhs) like '%ize!_')),
more>(lower(lhs) like '%ly!_'),
more>(lower(lhs) like '%s!_'),
more>(lower(lhs) like '%ed!_'),
more>(lower(lhs) like '%ing!_'),
more>(lower(lhs) like '%-%!_'),
more>(lower(lhs) like '%-!_'),
more>(lower(lhs) like '%.%!_'),
more>(lower(lhs) like '%.!_')
more>from test where lhs like '%!_' escape '!';
950028 tuples
I must point out that I think the amount of memory/cpu is time is used for this query is extremely high. Like my previous suggestion in the feature request, I hope that the deduplication of operations in one query, or per row can be achieved to reduce the actual operations.
## Comment 10698
Date: 2008-12-22 03:33:55 +0100
From: @skinkie
Just as reference; I noticed that the right query for SQLite:
select rhs,
(lhs like 'A%' OR lhs like 'B%' OR lhs like 'C%' OR lhs like 'D%' OR lhs like 'E%' OR lhs like 'F%' OR lhs like 'G%' OR lhs like 'H%' OR lhs like 'I%' OR lhs like 'J%' OR lhs like 'K%' OR lhs like 'L%' OR lhs like 'M%' OR lhs like 'N%' OR lhs like 'O%' OR lhs like 'P%' OR lhs like 'Q%' OR lhs like 'R%' OR lhs like 'S%' OR lhs like 'T%' OR lhs like 'U%' OR lhs like 'V%' OR lhs like 'W%' OR lhs like 'X%' OR lhs like 'Y%' OR lhs like 'Z%'),
(lower(lhs) like 'a%'),
(lower(lhs) like 'in%'),
(lower(lhs) like 'un%'),
(lower(lhs) like 'non%'),
((lower(lhs) like '%ise!_' escape '!') OR (lower(lhs) like '%ize!_' escape '!')),
(lower(lhs) like '%ly!_' escape '!'),
(lower(lhs) like '%s!_' escape '!'),
(lower(lhs) like '%ed!_' escape '!'),
(lower(lhs) like '%ing!_' escape '!'),
(lower(lhs) like '%-%!_' escape '!'),
(lower(lhs) like '%-!_' escape '!'),
(lower(lhs) like '%.%!_' escape '!'),
(lower(lhs) like '%.!_'escape '!' )
from test where lhs like '%!_' escape '!';
Is not even working for MonetDB; !SELECT: no such operator 'like'
## Comment 10699
Date: 2008-12-27 23:51:33 +0100
From: @njnes
added test OOM_query.SF-2457195.sql
fixed memory leak and missing BATseqbase
## Comment 10700
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2457195 at http://sourceforge.net/support/tracker.php?aid=2457195
| Broken query results in OOM, working one has no output | https://api.github.com/repos/MonetDB/MonetDB/issues/1900/comments | 0 | 2020-11-30T10:06:51Z | 2024-06-27T11:33:51Z | https://github.com/MonetDB/MonetDB/issues/1900 | 753,338,703 | 1,900 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-21 07:18:35 +0100
From: Wouter Alink <<alink>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2009-02-16 10:49:25 +0100
## Comment 10693
Date: 2008-12-21 19:18:35 +0100
From: Wouter Alink <<alink>>
I get the following error:
$ echo 'for $i in <aap><beer/></aap>//beer return root($i)' | mclient -lxq -p50590
!ERROR: serialize.mx:xquery_print_result_main: [kind=32, cont=0]
MAPI = monetdb@localhost:50590
QUERY = for $i in <aap><beer/></aap>//beer return root($i)
ERROR = !ERROR: XML Generation: UNKNOW_TYPE(' 'ch(32))
!ERROR:
!ERROR: xquery_print_result_loop: operation failed.
Using Mserver:
MonetDB Server v4.27.0
based on GDK v1.27.0
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for x86_64-redhat-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.27.0 loaded (default back-end is 'milprint_summer')
XRPC administrative console at http://127.0.0.1:50591/admin
MonetDB>
I'm not sure what the actual answer should be. The following change could be a possible solution (it prints <aap><beer/></aap>). Such an answer seems reasonable to me.
Index: serialize.mx
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/runtime/serialize.mx,v
retrieving revision 1.118
diff -u -r1.118 serialize.mx
--- serialize.mx 26 Nov 2008 15:00:15 -0000 1.118
+++ serialize.mx 21 Dec 2008 18:09:41 -0000
@@ -1896,6 +1896,7 @@
xmlNsDispose( &ctx->nsTop );
}
break;
+ case NODE:
case ELEM:
{
/* node_kind and cont have been already looked up */
## Comment 10694
Date: 2009-02-15 21:33:36 +0100
From: @drstmane
Jan,
do you have an opinion about this one?
Thanks!
Stefan
## Comment 10695
Date: 2009-02-16 11:26:23 +0100
From: @drstmane
test added in pathfinder/tests/BugTracker/Tests/root-node_of_constructed_element.SF-2456324.*
appears to work fine.
## Comment 10696
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2456324 at http://sourceforge.net/support/tracker.php?aid=2456324
| XQ: root()-node of constructed element cant be printed | https://api.github.com/repos/MonetDB/MonetDB/issues/1899/comments | 0 | 2020-11-30T10:06:47Z | 2024-06-28T13:27:52Z | https://github.com/MonetDB/MonetDB/issues/1899 | 753,338,663 | 1,899 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-15 01:43:43 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-12-27 03:47:31 +0100
## Comment 10688
Date: 2008-12-15 01:43:43 +0100
From: @skinkie
sql>select distinct way from way_tags group by way, k having count(*) > 1;
+----------+
| way |
+==========+
| 23950375 |
| 23950375 |
| 23950375 |
| 23950375 |
| 23950375 |
| 24644162 |
| 24644162 |
| 24644162 |
+----------+
8 tuples
Is the above correct. Since I would expect it to only have two results. I guess what happens is that the distinct operates on the group by product instead of the selected output.
select distinct (select 10 union all select 10);
+--------------+
| single_value |
+==============+
| 10 |
| 10 |
+--------------+
opposed to:
sql>select distinct a from (select 10 as a union all select 10 as a) as b;
+----+
| a |
+====+
| 10 |
+----+
## Comment 10689
Date: 2008-12-15 10:51:14 +0100
From: @romulogoncalves
Without updating my sources, this means I do not have the fixes from Niels, I can't reproduce the same output for this query:
(I did it for the current and stable branch...)
select distinct way from way_tags group by way, k having count(*) > 1;
% sys.way_tags table_name
% way name
% int type
% 8 length
[ 23950375 ]
[ 24644162 ]
## Comment 10690
Date: 2008-12-15 11:05:56 +0100
From: @romulogoncalves
Test added:
sql/src/test/BugTracker-2008/Tests/is_distinct_broken.SF-2430201.sql
And I think this is a bug for SQL-CVS branch and not MonetDB5-CVS branch... ;)
## Comment 10691
Date: 2008-12-27 15:47:31 +0100
From: @njnes
fixed the distinct operator
## Comment 10692
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2430201 at http://sourceforge.net/support/tracker.php?aid=2430201
| Is distinct broken? | https://api.github.com/repos/MonetDB/MonetDB/issues/1898/comments | 0 | 2020-11-30T10:06:43Z | 2024-06-27T11:33:49Z | https://github.com/MonetDB/MonetDB/issues/1898 | 753,338,622 | 1,898 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-12 01:57:51 +0100
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-12-15 10:58:32 +0100
## Comment 10684
Date: 2008-12-12 13:57:51 +0100
From: @romulogoncalves
I used the current branch of SQL this means I am using the algebra version of it (it is the default one)...
It seems a column from another system is not detected inside a function body...
This example covers the problem:
CREATE FUNCTION fDocColumns(tabname varchar(400))
RETURNS TABLE (enum varchar(64))
BEGIN
RETURN TABLE( select t.name from sys.tables t where name='romulo');
END;
drop function fDocColumns;
MAPI = skyserver@localhost:50000
>> QUERY = CREATE FUNCTION fDocColumns(tabname varchar(400))
>> ERROR = !SELECT: no such column 't.name'
## Comment 10685
Date: 2008-12-12 14:01:17 +0100
From: @romulogoncalves
Test added at:
sql/src/test/BugTracker-2008/Tests/col_from_another_inside_function_body.SF-2420768.sql
Note:
This bug only occurs in the current and not stable branch ;)
## Comment 10686
Date: 2008-12-15 10:58:32 +0100
From: @romulogoncalves
The bug can be closed... It was fixed with following check in and the test is green in all platforms:
[Monetdb-sql-checkins] sql/src/server rel_select.mx,,1.101,1.102
Modified Files:
rel_select.mx
Log Message:
fixed bug in table alias handling (for view used in create function).
## Comment 10687
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2420768 at http://sourceforge.net/support/tracker.php?aid=2420768
| col from another schema inside function body | https://api.github.com/repos/MonetDB/MonetDB/issues/1897/comments | 0 | 2020-11-30T10:06:40Z | 2024-06-27T11:33:48Z | https://github.com/MonetDB/MonetDB/issues/1897 | 753,338,591 | 1,897 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-12 12:31:49 +0100
From: Loredana Afanasiev <<lafanasi>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-18 06:27:35 +0200
## Comment 10677
Date: 2008-12-12 00:31:49 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi,
see bellow.
[lafanasi@zookst4 xq]$ mclient -lx -s 'for $d in pf:documents("HAN") return pf:docname($d)'
MAPI = monetdb@localhost:50000
QUERY = for $d in pf:documents("HAN") return pf:docname($d)
ERROR = !ERROR: BATfetchjoin(tmp_4306616,tmp_5160577) does not hit always (|bn|=0 != 19820=|l|) => can't use fetchjoin.
!ERROR: CMDleftfetchjoin: operation failed.
thx,
l.
## Comment 10678
Date: 2008-12-12 01:14:45 +0100
From: Loredana Afanasiev <<lafanasi>>
Related?
[lafanasi@zookst4 xq]$ mclient -lx -s 'for $d in pf:collection("HAN_Updatable")/node() return pf:docname($d)'MAPI = monetdb@localhost:50000
QUERY = for $d in pf:collection("HAN_Updatable")/node() return pf:docname($d)
ERROR = !ERROR: Division by zero
!ERROR: intint_checkbinary_DIV: operation failed.
!ERROR: interpret_params: mposjoin(param 1): evaluation error.
HAN and HAN_Updatable are the same collections but stored readonly and updatable, respectively.
## Comment 10679
Date: 2008-12-18 12:16:29 +0100
From: @lsidir
Hi,
docname is expecting exactly one node while pf:documents is returning a sequence of nodes. However, more investigation is needed to verify the correct behavior of docname.
## Comment 10680
Date: 2009-04-18 01:44:50 +0200
From: @peterboncz
this one turned out to be related to a known and open problem whith this pf:collection()
phtantom node: downward steps on it were not properly handled.
In particular:
- document reached would not be officially opened (triggering this bug)
- nodes would be returned from documents that were deleted
this is fixed now by testing in downward steps if the collection node is in the context sequence. if so, the ws_docfilter function is called
## Comment 10681
Date: 2009-04-18 11:06:58 +0200
From: @drstmane
re-opened to remind us that we should consider adding a test,
or at least give a reason why not test can be added.
## Comment 10682
Date: 2009-04-18 18:27:35 +0200
From: @peterboncz
test was added in HEAD, so it is there for the future
## Comment 10683
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2418722 at http://sourceforge.net/support/tracker.php?aid=2418722
| pf:docname() problem | https://api.github.com/repos/MonetDB/MonetDB/issues/1896/comments | 0 | 2020-11-30T10:06:37Z | 2024-06-27T11:33:47Z | https://github.com/MonetDB/MonetDB/issues/1896 | 753,338,558 | 1,896 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-11 05:04:00 +0100
From: Hans <<hans_0_>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-12-26 02:16:12 +0100
## Comment 10672
Date: 2008-12-11 17:04:00 +0100
From: Hans <<hans_0_>>
Hi MonetDB development team,
The MonetDB database gets corrupt when Mserver is killed shortly after a series of xqueries containing add-doc() and insert statements. Starting Mserver shows problems while loading the pathfinder module.
I downloaded Monet Fedora RPMs from:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./20081209/RPMs/Fedora9.i386.oid32/
I installed these with yum on my Fedora fc9 installation, running within VMWare on my Windows XP 32 bit machine. On request, a copy of the VMware virtual machine is available for analysis.
I performed the 4 steps as described in the text following this intro.
For step 2 I use a couple of Java programs that interact with Mserver via a JDBC connection. The xquery log of these Java programs is included.
After this I also cannot gain access to Mserver with mclient:
mclient -p 51240 -l xq
!xchange_challenge: frontend xquery not found
Regards,
Hans van Rijswijk
===================================================================================================================
===================================================================================================================
============== Step 1: boot Mserver
===================================================================================================================
===================================================================================================================
Command:
($MONETDB_HOME/bin/Mserver --config=$MONETDB_CONFIG_FILE --dbinit="module(pathfinder);mil_start();" --set xquery_backend=algebra)&
===================================================================================================================
===================================================================================================================
Config script:
Configuration file for MonetDB main-memory database
xiraf_pid_file=/var/xiraf/recover_monetdb_frontend.PID
xiraf_current_mserver_pid_file=/var/xiraf/current_mserver_frontend.PID
xiraf_recover_log=/var/xiraf/log/recover_frontend.log
xiraf_monetdb_lives=9
xiraf_transfer_folder=/var/xiraf/dbtransfer
This startup file is read by the GDK kernel, to set
system wide parameters. It can reside in either the local directory
where Mserver is called, or the home directory of the MonetDB user.
Where MonetDB is installed
prefix=/usr
exec_prefix=/usr
datadir=/usr/share
GDK Section
============
All databases are stored as a directory under the directory
given below. Use this value to change the overall location
of your data.
gdk_dbfarm=/var/xiraf/MonetDB4/dbfarm-frontend
MonetDB can only handle one database at a time. You can specify
the name of the database to use below. Note that you can use
multiple databases, but that you have to edit the database name
and restart MonetDB.
gdk_dbname=demo
The options below deal with various aspects of memory usage behaviour.
If you don't know what these values mean, you should leave them alone.
gdk_mem_bigsize & gdk_vm_minsize will be set/limited to
1/2 of the physically available amount of main-memory
during start-up in src/tools/Mserver.mx
memory chunks of size >= gdk_mem_bigsize (in bytes) will be mmaped anonymously
gdk_mem_bigsize=262144
memory chunks of size >= gdk_vm_minsize (in bytes) will be mmaped;
gdk_vm_minsize=137438953472
for 32 bit systems try to claim 3G of (virtual) memory;
gdk_vmtrim=yes
set to "no" to disable the vmtrim thread.
valgrind issues:
for 32 bit systems it tries claim 3G of (virtual) memory
set to "no" to run Mserver with valgrind.
also, you need to tell valgrind to use 8-byte alignment, hence:
"valgrind --alignment=8 Mserver --set gdk_alloc_map=no ..."
gdk_alloc_map=no
the kernel can be used in embedded situations (don't set this yourself)
gdk_embedded=no
You can enable debug for specific parts. By default debug is
switched off.
gdk_debug=0
possible values: (can be a combination of)
1 = thread-specific debug output
2 = property enforcing on new BATs
4 = memory allocation
8 = property checking on all values: tells about wrongly set properties
16 = major IO activity
32 = BAT handling
64 = MIL parser debugging
128 = Thread management
256 = Event management
512 = Transaction management
1024 = Locks and Triggers
2048 = Dynamic loading
4096 = BBP Performance (?)
8192 = Delta debugging (?)
16384 = Module loading
32768 = Yacc specific error messages
65536 = tcpip (??)
131072 = monet_multiplex: setaggr debugging (??)
262144 = \
524288 = ddbench (???)
1048576 = /
2097152 = show join/select algorithm chosen
4194304 = show result size estimations (for join,select)
8388608 = extended property checking: tells also about not set properties
16777216 = disable property checking with join & outerjoin (e.g., for performance measurements)
33554432 = disable "cleaning" of freed memory in GDKfree() (e.g., for performance measurements)
General client Section
=======================
host=localhost the host the server runs on
MonetDB Section
================
Administrator user name
monet_admin=adm
Prompt when using MIL interface
monet_prompt=MonetDB>
Show version and copyright information when starting the server or
a MIL client?
monet_welcome=yes
Where do the MonetDB modules reside?
The first directory contains MIL modules, and either the second or third (depending on the system) the C modules.
monet_mod_path=/usr/lib/MonetDB4:/usr/lib/MonetDB4/lib:/usr/lib/MonetDB4/bin
Start Mserver in daemon mode, or start with MIL interactive interface?
monet_daemon=yes
Monet Application Interface Section
====================================
default port to address an Mserver for a MIL session
mapi_port=51240
allow mclient sessions from outside the server machine
mapi_open=true
show all the MIL output? (default: no)
mapi_noheaders=no
The MAPI debug level (should be disabled for normal use)
mapi_debug=0
The number of concurrent clients can be set using mapi_clients
(smaller than 1 is not very useful)
mapi_clien1970-01-01 01:00:02 +0100
SQL Interface Section
======================
The SQL debug level (should be disabled for normal use)
sql_debug=0
Place to store transaction logs
The logs are typically stored on a different storage medium
to protect the database against accidental hardware loss.
it should be different directory as used for xquery!
sql_logdir=/var/MonetDB4/sql_logs
XQuery Interface Section
=========================
default back-end: "milprint_summer" or "algebra"
xquery_backend=algebra
output mode "dm" = pretty printed,
"xml" = enforce XML with enclosing <XQueryResult> tags
xquery_output=dm
limit the document cache on disk to 100MB
xquery_cacheMB=100
rules like {URL=seconds;}* e.g. cache w3c for a day, CNN for 5 minutes
xquery_cacherules="http://www.w3.org/=79200;http://www.cnn.com=300"
xquery_cacherules=""
limit the function cache in memory to 128MB
xquery_procMB=128
Place to store transaction logs
The logs are typically stored on a different storage medium
to protect the database against accidental hardware loss.
it should be different directory as used for sql!
xquery_logdir=/opt/xiraf/MonetDB/var/MonetDB4/xquery_logs_frontend
if not set port to address the HTTP server for pathfinder = mapi_port+1
xrpc_port=""
xrpc daemon is open for outside connections by default
xrpc_open=false
Additional options to be passed to the XRPC server, currently only
"timing".
xrpc_options=""
IP addresses or hostname separated by ';' who can execute scripts in
<datadir>/MonetDB/xrpc/admin/
xrpc_admin="http://127.0.0.1;127.0.0.1;http://localhost;localhost"
IP addresses or hostname separated by ';' who can retrieve XML
documents stored in the database using a URL of the form:
http://<host>[:port]/xrpc/<name>.xml
xrpc_user="http://127.0.0.1;127.0.0.1;http://localhost;localhost"
url prefixes of trusted modules separated by ';'
xrpc_trusted="http://monetdb.cwi.nl;http://127.0.0.1;http://localhost;/usr/share/MonetDB/xrpc/export"
standoff annotation XPath extension
standoff_ns=http://monetdb.cwi.nl/standoff
standoff_ns=
standoff_start=start
standoff_end=end
Profile Interface Section
====================================
for 32 bit systems try to claim 3G of (virtual) memory;
set to "no" to run Mserver with valgrind.
valgrind --tool=callgrind Mserver --set gdk_alloc_map=no ..."
gdk_alloc_map=yes
===================================================================================================================
===================================================================================================================
============== Step 2: Insert data via JDBC connection
===================================================================================================================
===================================================================================================================
Query log:
Thu Dec 11 13:42:55 CET 2008 executeQuery:
element result {let $projdoc := pf:documents()[.='projects.xml']
return if (exists($projdoc)) then element projectsdocexists {} else element projectsdocnonexistent {}}
Thu Dec 11 13:42:55 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf4040814192720964387.xml","projects.xml","projects.xml_1228999375401",10)
Thu Dec 11 13:42:55 CET 2008 executeQuery:
element result {let $projdoc := pf:documents()[.='bookmarks.xml']
return if (exists($projdoc)) then element docexists {} else element docnonexistent {}}
Thu Dec 11 13:42:55 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf3326179746776330670.xml","bookmarks.xml","bookmarks.xml_1228999375870",10)
Thu Dec 11 13:42:55 CET 2008 executeQuery:
element result {let $projdoc := pf:documents()[.='reports.xml']
return if (exists($projdoc)) then element docexists {} else element docnonexistent {}}
Thu Dec 11 13:42:56 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf6349201089799532961.xml","reports.xml","reports.xml_1228999376208",10)
Thu Dec 11 13:43:09 CET 2008 executeQuery:
doc("projects.xml")/projects/project[@name='demo']
Thu Dec 11 13:43:09 CET 2008 executeQuery:
1+1
Thu Dec 11 13:43:09 CET 2008 hasXMLDoc:
count(pf:documents()[.="demo.xml"])
Thu Dec 11 13:43:09 CET 2008 hasXMLDoc:
count(pf:documents()[.="notes_demo.xml"])
Thu Dec 11 13:43:09 CET 2008 hasXMLDoc:
count(pf:documents()[.="demo.xml"])
Thu Dec 11 13:43:10 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf493570239516592169.xml","demo.xml","demo.xml_1228999390017")
Thu Dec 11 13:43:10 CET 2008 hasXMLDoc:
count(pf:documents()[.="notes_demo.xml"])
Thu Dec 11 13:43:10 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf7574288057964248812.xml","notes_demo.xml","notes_demo.xml_1228999390164",10)
Thu Dec 11 13:43:10 CET 2008 executeQuery:
element result {let $projdoc := pf:documents()[.='projects.xml']
return if (exists($projdoc)) then ( element projectsdocexists {} ,
let $created := doc("projects.xml")/projects/project[@name='demo']
return if (exists($created)) then element projectcreated {} else element projectnotcreated {} )
else element projectsdocnonexistent {},let $proj := pf:documents()[.='demo.xml']
return if (exists($proj)) then element projectxmlexists {} else element projectxmlnonexistent {}}
Thu Dec 11 13:43:10 CET 2008 executeUpdate:
let $proj := element project { attribute name {"demo"}, element index {"demo.xml"}, element casename {"demo"},
element notes {"notes_demo.xml"}, element anonymous {"nesag8"}, element description {""}}
return do insert $proj as last into doc("projects.xml")/projects
Thu Dec 11 13:43:10 CET 2008 hasXMLDoc:
count(pf:documents()[.="restored-document.xml"])
Thu Dec 11 13:43:10 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf1949015156574180619.xml","restored-document.xml","restored-document.xml_1228999390760")
Thu Dec 11 13:43:10 CET 2008 executeQuery:
for $f in doc("restored-document.xml")/bookmark/folder return (string($f/@name), pf:nid(exactly-one($f/bookmark-definition)))
Thu Dec 11 13:43:10 CET 2008 deleteXMLDoc:
pf:del-doc("restored-document.xml")
Thu Dec 11 13:43:10 CET 2008 hasXMLDoc:
count(pf:documents()[.="restored-document.xml"])
Thu Dec 11 13:43:11 CET 2008 insertXMLDoc:
pf:add-doc("/var/xiraf/dbtransfer/xiraf2115018461422569140.xml","restored-document.xml","restored-document.xml_1228999391045")
Thu Dec 11 13:43:11 CET 2008 executeQuery:
for $f in doc("restored-document.xml")/report/folder return (string($f/@name), pf:nid(exactly-one($f/report-definition)))
Thu Dec 11 13:43:11 CET 2008 deleteXMLDoc:
pf:del-doc("restored-document.xml")
===================================================================================================================
===================================================================================================================
============== Step 3: shutdown Mserver
===================================================================================================================
===================================================================================================================
Command:
kill -TERM $MONETDB_PID
===================================================================================================================
===================================================================================================================
============== Step 4: boot Mserver
===================================================================================================================
===================================================================================================================
Command:
($MONETDB_HOME/bin/Mserver --config=$MONETDB_CONFIG_FILE --dbinit="mil_start();module(pathfinder);" --set xquery_backend=algebra)&
===================================================================================================================
===================================================================================================================
Errors:
MonetDB Server v4.26.1
based on GDK v1.26.1
Copyright (c) 1993-July 2008, CWI. All rights reserved.
Copyright (c) August 2008-, MonetDB B.V.. All rights reserved.
Compiled for i686-redhat-linux-gnu/32bit 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
!ERROR: logger: could not use bat (220) for 1000000005_map_pid
!ERROR: logger: could not use bat (780) for 1000000005_rid_size
!ERROR: logger: could not use bat (781) for 1000000005_rid_level
!ERROR: logger: could not use bat (735) for 1000000005_rid_prop
!ERROR: logger: could not use bat (782) for 1000000005_rid_kind
!ERROR: logger: could not use bat (242) for 1000000005_rid_nid
!ERROR: logger: could not use bat (748) for 1000000005_nid_rid
!ERROR: logger: could not use bat (750) for 1000000005_qn_histogram
!ERROR: logger: could not use bat (447) for 1000000005_qn_prefix_uri_loc
!ERROR: logger: could not use bat (228) for 1000000005_qn_uri_loc
!ERROR: logger: could not use bat (515) for 1000000005_qn_prefix
!ERROR: logger: could not use bat (343) for 1000000005_qn_uri
!ERROR: logger: could not use bat (326) for 1000000005_qn_loc
!ERROR: logger: could not use bat (757) for 1000000005_attr_own
!ERROR: logger: could not use bat (786) for 1000000005_attr_qn
!ERROR: logger: could not use bat (785) for 1000000005_attr_prop
!ERROR: logger: could not use bat (244) for 1000000006_map_pid
!ERROR: logger: could not use bat (761) for 1000000006_rid_size
!ERROR: logger: could not use bat (755) for 1000000006_rid_level
!ERROR: logger: could not use bat (702) for 1000000006_rid_prop
!ERROR: logger: could not use bat (706) for 1000000006_rid_kind
!ERROR: logger: could not use bat (230) for 1000000006_nid_rid
!ERROR: logger: could not use bat (525) for 1000000006_qn_uri_loc
!ERROR: logger: could not use bat (564) for 1000000006_qn_prefix
!ERROR: logger: could not use bat (523) for 1000000006_qn_uri
!ERROR: logger: could not use bat (516) for 1000000006_qn_loc
!ERROR: logger: could not use bat (736) for 1000000006_prop_text
!ERROR: logger: could not use bat (372) for 1000000006_prop_com
!ERROR: logger: could not use bat (783) for 1000000006_prop_ins
!ERROR: logger: could not use bat (316) for 1000000006_prop_tgt
!ERROR: logger: could not use bat (347) for 1000000006_prop_val
!ERROR: logger: could not use bat (749) for 1000000006_attr_own
!ERROR: logger: could not use bat (747) for 1000000006_attr_qn
===================================================================================================================
===================================================================================================================
## Comment 10673
Date: 2008-12-11 23:49:55 +0100
From: @peterboncz
Sjoerd: it looks like bats are non-existent after the server is restarted.
I think it may have something to do with the logger changes you carried through (the "leftover" bugs). I am not sure now when a subcommit is forced. The subcommit should checkpoint the new bats and write BBP.dir. After that, the bats should exist.
Is a subcommit forced after each document mgt query? I guess it must be, because afaik we do not implement logging a shred action.
In any case, the log gives a good handle for a replay, and the VM image will be handy too.
## Comment 10674
Date: 2008-12-12 10:14:32 +0100
From: @sjoerdmullender
The only way I can reproduce this scenario is by only partially cleaning up the database.
The database consists of two important parts: the dbfarm directory and the xquery_logs directory. If I delete (the contents of) the dbfarm directory, but not (the contents of) the xquery_logs directory, I get these same error messages when I restart the server afterwards.
Note the definitions of these variables in your config file:
gdk_dbfarm=/var/xiraf/MonetDB4/dbfarm-frontend
xquery_logdir=/opt/xiraf/MonetDB/var/MonetDB4/xquery_logs_frontend
It is these two directories that should be cleared together when removing the database.
## Comment 10675
Date: 2008-12-12 10:33:24 +0100
From: @sjoerdmullender
I found another way of reproducing the errors: by doing a sync() before the server is killed.
From your mailing list posting I remembered that you used sync() at some point.
Don't use sync() or commit(). They just don't work in combination with the write-ahead log.
## Comment 10676
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2417515 at http://sourceforge.net/support/tracker.php?aid=2417515
| MonetDB database corrupt on restart shortly after an update | https://api.github.com/repos/MonetDB/MonetDB/issues/1895/comments | 0 | 2020-11-30T10:06:34Z | 2024-06-28T13:27:51Z | https://github.com/MonetDB/MonetDB/issues/1895 | 753,338,515 | 1,895 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-09 12:09:18 +0100
From: @peterboncz
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-04-07 02:57:46 +0200
## Comment 10669
Date: 2008-12-09 00:09:18 +0100
From: @peterboncz
pathfinder.mx:
1671 ws.slice(NID_RID,ATTR_PROP).[append](mem);
I saw a just created rcopy()-ed PROP_VAL bat from an updatable multi-doc collection cause an assert() in CMD_append, as it got unloaded from the BBP (ie BBP[].b[0] == NULL). I observed it having both a logical *and* a physical BBP refcount of 1. Question is how it could be unloaded. A strange clue was its BBP status (4, that is BBPTMP)
BBPTMP are bats that are not persistent (that is correct, it is a rcopy) but that got saved. That is strange, because why would that bat get saved? Note that an rcopy() bat is a "logical view" (lview) on the master bat.
Another clue was that the logger background thread was in the middle of a BBPsync() when this assert went off. Regrettably I lost the gdb session so I could not debug further.
possble ideas:
- maybe the new logger somehow gets to checkpoint the copied private images instead of the master bats?
- meybe the rcopy bats are not properly recognized by the BBPtrim thread such that it saves and unloads them.
being unloaded in BBP,
## Comment 10670
Date: 2009-04-07 14:57:46 +0200
From: @peterboncz
i think the bugfix of december 2008 for NFI (BBPdecref) caught this one
this is a race condition and impossible to reproduce in the testweb
## Comment 10671
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2407834 at http://sourceforge.net/support/tracker.php?aid=2407834
| logger-rcopy BBP bug | https://api.github.com/repos/MonetDB/MonetDB/issues/1894/comments | 0 | 2020-11-30T10:06:31Z | 2024-06-28T13:27:51Z | https://github.com/MonetDB/MonetDB/issues/1894 | 753,338,479 | 1,894 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-08 04:59:48 +0100
From: @drstmane
To: @yzchang
Version: -- development
Last updated: 2009-07-31 02:43:23 +0200
## Comment 10661
Date: 2008-12-08 16:59:48 +0100
From: @drstmane
All tests in pathfinder/runtime/xrpc/admin/Tests/ fail on all platforms, with both ALG & MPS.
On Fedora 8 & Gentoo 1.12.11.1, they run into a timeout, on all other platforms, they produce a syntax error like
"
QUERY = import module namespace adm = "http://monetdb.cwi.nl/XQuery/admin/"
ERROR = !parse error: syntax error, unexpected invalid_character, expecting $end on line 1, column 5 (next token is `N')
!parse error: XQuery parsing failed
!module import: "import module" references a query, not a module
"
See, e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/add_del_doc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora9/runtime_xrpc_admin/add_del_doc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.64.64.d.1-Fedora8/runtime_xrpc_admin/add_del_doc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora9/runtime_xrpc_admin/add_del_doc.err.00.html
## Comment 10662
Date: 2009-02-14 18:06:10 +0100
From: @drstmane
The test now appear to timeout on many (though not all) platforms --- with MPS back-end; XRPC is not yet supported with the Algebra back-end:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/add_del_doc_noxrpc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/add_del_doc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/backup_restore_noxrpc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/db_stats_noxrpc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/db_stats.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/db_env_noxrpc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/db_env.err.00.html
## Comment 10663
Date: 2009-02-15 19:04:05 +0100
From: @drstmane
Jennie,
are the "noxrpc" variants of the xrpc admin tests supposed to work withou XRPc, and hence also with the default Algebra back-end?
Thanks,
Stefan
## Comment 10664
Date: 2009-02-17 13:43:30 +0100
From: @yzchang
The first two, i.e., add_del_doc_noxrpc and backup_restore_noxrpc, should work with the algebra back-end, so I have enabled them.
The last two, i.e., db_env_noxrpc and db_stat_noxrpc, don't work with the algebra back-end, because they need pf:mil(), which is not implemented in the algebra back-end, so, they remain disabled.
## Comment 10665
Date: 2009-02-20 12:34:52 +0100
From: @yzchang
On several systems, all tests work now, after the HTTP server document-root has been made comfigurable (via xrpc_docroot).
On Fedora 8, the tests time out, and on Windows they give syntax error. But both problems might due to the same reason, i.e., could not retrieve the module file.
This only happens if monet is compiled with --enable-optimize, but then, both with RunMtest and Mtest.
## Comment 10666
Date: 2009-03-19 07:55:36 +0100
From: @drstmane
Correctly setting the xrpc_docroot in RunMtest.bat[.in] for Windows (just like it done in RunMtest[.in] for Unix),
helps to make the XRPC/admin tests work on Windows;
cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/index_short.html
(and
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/index_short.html
as of coming weekend).
The "misterious" timeout on Fedora 8 still remains unexplained and non-investigated.
## Comment 10667
Date: 2009-07-31 14:43:22 +0200
From: @drstmane
No longer testing on Fedora 8, all tests now work fine.
Closing.
## Comment 10668
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2406824 at http://sourceforge.net/support/tracker.php?aid=2406824
| PF: all xrpc/admin tests fail | https://api.github.com/repos/MonetDB/MonetDB/issues/1893/comments | 0 | 2020-11-30T10:06:27Z | 2024-06-27T11:33:44Z | https://github.com/MonetDB/MonetDB/issues/1893 | 753,338,439 | 1,893 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-08 10:40:46 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2009-01-27 08:41:21 +0100
## Comment 10657
Date: 2008-12-08 10:40:46 +0100
From: @grobian
PID USERNAME NLWP PRI NICE SIZE RES STATE TIME CPU COMMAND
6689 fabian 4 59 0 22M 924K run 48:54 0.25% merovingian
merovingian just always seems to be in running state, consuming too much CPU cycles in "idle" state.
Need to investigate if we can switch to blocking operations (more threads) instead of controlled polling using sleep.
## Comment 10658
Date: 2008-12-28 23:56:39 +0100
From: @grobian
27685 fabian 4 59 0 22M 2576K sleep 0:00 0.00% merovingian
Merovingian now takes way less resources, being in idle state consistently below mserver5 now and showing with truss/strace a healthy amount of syspoll()/time() calls.
Using select() now to avoid using more threads and make waiting for something to happen more efficient.
Next bugfix/feature release will include this improvement.
## Comment 10659
Date: 2009-01-27 20:41:21 +0100
From: @grobian
has been released in Nov2008-SP2
## Comment 10660
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2405952 at http://sourceforge.net/support/tracker.php?aid=2405952
| Merovingian takes too much CPU resources | https://api.github.com/repos/MonetDB/MonetDB/issues/1892/comments | 0 | 2020-11-30T10:06:24Z | 2024-06-27T11:33:43Z | https://github.com/MonetDB/MonetDB/issues/1892 | 753,338,398 | 1,892 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-04 02:15:49 +0100
From: @sjoerdmullender
To: @njnes
Version: -- development
Last updated: 2008-12-27 10:32:17 +0100
## Comment 10654
Date: 2008-12-04 14:15:49 +0100
From: @sjoerdmullender
This little (incorrect) program causes a server crash:
create table b (data blob);
insert into b values ('0102030405060708090A0B0C0D0E0F');
(there is a blob missing before the string, but this should give an error, not a crash).
## Comment 10655
Date: 2008-12-27 22:31:39 +0100
From: @njnes
fixed in CVS Head (only)
(test was added BugTracher-2008/blob_insert_crash.SF-2388542.sql)
## Comment 10656
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2388542 at http://sourceforge.net/support/tracker.php?aid=2388542
| SQL bad blob insert causes crash | https://api.github.com/repos/MonetDB/MonetDB/issues/1891/comments | 0 | 2020-11-30T10:06:21Z | 2024-06-27T11:33:42Z | https://github.com/MonetDB/MonetDB/issues/1891 | 753,338,364 | 1,891 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-04 01:32:38 +0100
From: Floris Ouwendijk <<floris233>>
To: Peter Boncz <<boncz>>
Version: -- development
Last updated: 2009-03-15 11:21:27 +0100
## Comment 10649
Date: 2008-12-04 13:32:38 +0100
From: Floris Ouwendijk <<floris233>>
While running a scenario that produces invalid XML, Mserver correctly reports errors, but afterwards the data is corrupt.
The scenario involves quite some queries, some concurrently executed. The following are the steps leading up to the problem. Replaying the log of the scenario doesn't reproduce the situation, while rerunning the scenario does.
The database version used is built from /projects/monetdb/Stable/.DailyBuilds./20081126/
The following is the query that contains invalid XML in the file being shredded:
(: Thu Dec 04 11:36:01 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@4ab34646' :)
pf:add-doc("/var/dbtransfer/invalidxml/xiraf12186.xml","-6254939761029904246-148-1228386961869.xml","cons02_log.xml")
<>
Error: ERROR: Char 0xFFFF out of allowed range
ERROR: PCDATA invalid Char value 65535
ERROR: Char 0xFFFF out of allowed range
ERROR: PCDATA invalid Char value 65535
ERROR: Char 0xFFFF out of allowed range
ERROR: PCDATA invalid Char value 65535
ERROR: Char 0xFFFF out of allowed range
ERROR: PCDATA invalid Char value 65535
ERROR: Char 0xFFFF out of allowed range
ERROR: PCDATA invalid Char value 65535
ERROR: Char 0xFFFF out of allowed range
ERROR: PCDATA invalid Char value 65535
ERROR: Char 0xFFFF out of allowed range
(and lots more of these errors).
This is followed by some queries that do not involve the above document:
(: Thu Dec 04 11:37:19 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@7b712193' :)
1+1
<>
(: Thu Dec 04 11:37:19 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@7b712193' :)
count(doc("cons02.xml")//*)
<>
(: Thu Dec 04 11:37:19 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@fcdfd19' :)
doc("cons02.xml")
<>
(: Thu Dec 04 11:37:27 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@612e4cd' :)
1+1
<>
(: Thu Dec 04 11:37:27 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@612e4cd' :)
pf:del-doc("cons02.xml")
<>
(: Thu Dec 04 11:37:28 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@4ab34646' :)
pf:add-doc("/var/dbtransfer/invalidxml/xiraf12187.xml","cons02.xml","cons02.xml_1228387047960",10)
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@5f3c296b' :)
1+1
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@5f3c296b' :)
pf:del-doc("prepared11965.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@7b712193' :)
pf:del-doc("prepared11976.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@fcdfd19' :)
pf:del-doc("prepared11995.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@612e4cd' :)
pf:del-doc("prepared12024.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@4ab34646' :)
pf:del-doc("prepared12031.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@5f3c296b' :)
pf:del-doc("prepared12032.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@7b712193' :)
pf:del-doc("prepared12156.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@fcdfd19' :)
pf:del-doc("prepared12171.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@612e4cd' :)
pf:del-doc("prepared12182.data")
<>
(: Thu Dec 04 11:37:45 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@4ab34646' :)
let $doc := doc("cons02.xml")//*[not(self::container)]
let $count := count(for $i in $doc
where not($i/@xid)
return $i)
let $max := (let $nodes := for $j in $doc/@xid
return $j cast as xs:integer
return
if (count($nodes) > 0) then
max($nodes)
else
0)
return ($count, $max, count($doc))
<>
(: Thu Dec 04 11:37:55 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@5f3c296b' :)
1+1
<>
(: Thu Dec 04 11:37:55 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@5f3c296b' :)
doc("cons02.xml")
<>
(: Thu Dec 04 11:38:02 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@7b712193' :)
pf:del-doc("cons02.xml")
<>
(: Thu Dec 04 11:38:03 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@fcdfd19' :)
pf:add-doc("/var/dbtransfer/invalidxml/xiraf12190.xml","cons02.xml","cons02.xml_1228387082386",10)
<>
(: Thu Dec 04 11:38:21 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@612e4cd' :)
1+1
<>
Then the final steps involve the document:
(: Thu Dec 04 11:38:21 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@612e4cd' :)
count(pf:collections()[.="cons02_log.xml"])
<>
(: Thu Dec 04 11:38:21 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@4ab34646' :)
element { "log" } { pf:collection("cons02_log.xml")//run }
<>
(: Thu Dec 04 11:38:21 CET 2008 @ connection 'nl.minjus.nfi.xiraf.XQueryDBConnection@5f3c296b' :)
pf:add-doc("/var/dbtransfer/invalidxml/xiraf12192.xml","BED68817-131F-9A60-51AB-1300FAF5AE8E.xml","BED68817-131F-9A60-51AB-1300FAF5AE8E.xml_1228387101406")
<>
Error: ERROR: error parsing attribute name
ERROR: attributes construct error
ERROR: Couldn't find end of Start Tag fault line 81143
ERROR: Premature end of data in tag task line 81119
ERROR: Premature end of data in tag failure line 81118
ERROR: Premature end of data in tag run line 81066
ERROR: Premature end of data in tag log line 1
ERROR: [shred_url]: 1 times inserted nil due to errors at tuples 0@0.
ERROR: [shred_url]: first error was:
ERROR: shredder_parse: XML input not well-formed.
ERROR: CMDshred_url: operation failed.
This final error is correct: the file being shredded is not valid. The file is the output of the query right before it:
element { "log" } { pf:collection("cons02_log.xml")//run }
In this output, the last lines are:
<task exitvalue="0" xid="1639">
<errout/>
<stdout>11:34:48,498 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] Going to run OLE2Tool on case 'cons02' (82126168995,82126170531)
11:34:48,499 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] Writing XML to '/tmp/floris_xiraf_invalidxml/work/invoke-1252256301/output/1639.xml' and handler to (/tmp/floris_xiraf_invalidxml/work/invoke-1252256301/output
/1639.hndlr)
11:34:48,509 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] Starting tool-run...
11:34:48,509 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] run: Getting StreamNode for 'cons02', [82126168995,82126170531]
11:34:53,985 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] StreamNode size: 1536
11:34:53,985 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] run: Opening OLE2 file...
CANNOT FIND CHILD Catalog
CANNOT FIND CHILD PoMAPI = monetdb@server.xiraf:49980
QUERY = element { "log" } { pf:collection("cons02_log.xml")//run }
ERROR = !ERROR:
!ERROR: XML Generation: NULL BAT has a 24 head, but tail is NULL.
!ERROR:
!ERROR: xquery_print_result_main: operation failed.
werPoint Document
CANNOT FIND CHILD WordDocument
11:34:54,181 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] run: got unknown ole2 subformat
11:34:54,181 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] run: Generating XML...
11:34:54,189 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] run: size is 0
11:34:54,189 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] run: type is ole2
11:34:54,213 INFO [nl.minjus.nfi.xiraf.tools.ole2.OLE2Tool] Done!
</stdout>
<fault!ERROR: XML Generation: tmp_1454 BAT does not have a 24 head.
This is a merger of output and error streams of mclient. The error seems to be:
monetdb@server.xiraf:49980
QUERY = element { "log" } { pf:collection("cons02_log.xml")//run }
ERROR = !ERROR:
!ERROR: XML Generation: NULL BAT has a 24 head, but tail is NULL.
!ERROR:
!ERROR: xquery_print_result_main: operation failed.
ERROR: XML Generation: tmp_1454 BAT does not have a 24 head.
## Comment 10650
Date: 2009-02-16 13:40:09 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
(and find out how/by whow it was fixed, if at all; there is no comment about that ...)
## Comment 10651
Date: 2009-02-17 01:28:58 +0100
From: @drstmane
Unfortunately, this bug report does not provide the data (documents) that is required to create a proper test.
## Comment 10652
Date: 2009-03-15 11:21:27 +0100
From: @drstmane
Due to lack of information and/or data to reproduce the problem,
closing without test,
and hence, without both
check whether the bug is indeed fixed
and monitoring to ensure the persistence of the fix.
## Comment 10653
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2388424 at http://sourceforge.net/support/tracker.php?aid=2388424
| ERROR: XML Generation: NULL BAT has a 24 head, but tail is N | https://api.github.com/repos/MonetDB/MonetDB/issues/1890/comments | 0 | 2020-11-30T10:06:18Z | 2024-06-27T11:33:41Z | https://github.com/MonetDB/MonetDB/issues/1890 | 753,338,319 | 1,890 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-04 11:37:59 +0100
From: Floris Ouwendijk <<floris233>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-12-15 11:46:29 +0100
## Comment 10644
Date: 2008-12-04 11:37:59 +0100
From: Floris Ouwendijk <<floris233>>
While investigating a problem where a collection-query returns invalid data, I ran into problems with mclient seemingly not generating a proper exit value.
If I run:
$ mclient -lxq -p49980 -s"element { \"log\" } {
pf:collection(\"cons02_log.xml\")//run }"
-removed a lot of xml-
</stdout>
<fault!ERROR: XML Generation: tmp_3265 BAT does not have a 24 head.
MAPI = monetdb@bo...:49980
QUERY = element { "log" } { pf:collection("cons02_log.xml")//run }
ERROR = !ERROR:
!ERROR: XML Generation: NULL BAT has a 24 head, but tail is NULL.
!ERROR:
!ERROR: xquery_print_result_main: operation failed.
$ echo $?
0
The above returns a lot of correct XML, then dumps an error to stderr, but returns error code 0.
In contrast, the following works as expected:
$ mclient -lxq -p49980 -s"eelement { \"log\" } {
pf:collection(\"cons02_log.xml\")//run }" >/dev/null
MAPI = monetdb@server:49980
QUERY = eelement { "log" } { pf:collection("cons02_log.xml")//run }
ERROR = !parse error: syntax error, unexpected {, expecting $end on line
1, column 10 (next token is `{')
!parse error: XQuery parsing failed
! halted in parser.tab.c (PFparse), line 5716
$ echo $?
1
Which is the expected result for a flawed query.
## Comment 10645
Date: 2008-12-12 00:07:28 +0100
From: @peterboncz
Sjoerd: the above was a true bug that led to a runtime error. However, mapi did see an error hence the error code of mclient should have been set.
On a related note, I have noticed that when in xquery mode and handling a script with multiple queries (with the <> seprator), after a (correct) XQuery error (nonexisting document, I believe( mclients stops executing the remaining queries (and actualy hangs). Do not know whether this happens always.
This behavior hinders the ability of NFI to replay logs, because sometimes not all documents used in a log are available, hence errors are bound to occur.
## Comment 10646
Date: 2008-12-15 11:13:51 +0100
From: @sjoerdmullender
I could implement something, but I'd first like to know what it is we want.
If there is a single query which fails, the answer is obvious: mclient should exit with an error.
But what if there are multiple queries (assuming mclient continues--if not, file a different bug report), but the last query succeeds. What should mclient return? Should it return an indication that somewhere along the line a query failed, or should it just return the status of the last query? And what if mclient is really interactive?
## Comment 10647
Date: 2008-12-15 11:46:19 +0100
From: @sjoerdmullender
I thought about it more and this is what I implemented:
In interactive mode (i.e. when prompts are displayed), only exit with an error indication if the last query failed.
In non interactive mode, exit with an error code (after executing all queries) if any of the executed queries failed.
This should fix the problem, so I'll close the bug report.
Peter, if you can find out if and when your other problem occurs, please file a new bug report.
## Comment 10648
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2388047 at http://sourceforge.net/support/tracker.php?aid=2388047
| Mclient exit code | https://api.github.com/repos/MonetDB/MonetDB/issues/1889/comments | 0 | 2020-11-30T10:06:15Z | 2024-06-27T11:33:40Z | https://github.com/MonetDB/MonetDB/issues/1889 | 753,338,271 | 1,889 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-12-01 10:35:10 +0100
From: @grobian
To: @mlkersten
Version: -- development
Last updated: 2008-12-08 06:15:11 +0100
## Comment 10637
Date: 2008-12-01 10:35:10 +0100
From: @grobian
I discovered by accident there is a tool called "mrecover", however it is totally unclear what this tool "recovers", if it recovers at all. Its help message doesn't give me any clue as to what it does, and there is no man-page. BigBrother/Google can't tell me what mrecover in MonetDB context is either.
(pegasus:src/tools/Tests) fabian% $INSTALL_DIR/bin/mrecover --help
Usage: mrecover [options]
--dbname=<database_name>
--ascii=<yes/no> default no
--tool=<mapi/jdbc> default mapi
--dir=<directory>
--help
(pegasus:src/tools/Tests) fabian% man mrecover
No manual entry for mrecover
(pegasus:src/tools/Tests) fabian%
## Comment 10638
Date: 2008-12-01 22:28:00 +0100
From: @mlkersten
The mcheckpoint/mrecover are old scripts for the Linux environment.
The code has not been actively maintained.
It is out of date.
## Comment 10639
Date: 2008-12-08 10:46:27 +0100
From: @grobian
perhaps then it should be removed?
## Comment 10640
Date: 2008-12-08 11:48:31 +0100
From: @sjoerdmullender
If it is to be removed, then only from the development branch.
## Comment 10641
Date: 2008-12-08 22:42:15 +0100
From: @sjoerdmullender
Why did you close this with a "Won't fix"? Please elaborate.
## Comment 10642
Date: 2008-12-08 22:47:01 +0100
From: @grobian
well, he didn't fix it (by documenting), but just removed it. One can indeed consider that as a "wontfix".
## Comment 10643
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2369980 at http://sourceforge.net/support/tracker.php?aid=2369980
| M5: mrecover: what is it? | https://api.github.com/repos/MonetDB/MonetDB/issues/1888/comments | 0 | 2020-11-30T10:06:12Z | 2024-06-28T13:27:50Z | https://github.com/MonetDB/MonetDB/issues/1888 | 753,338,236 | 1,888 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-26 02:36:16 +0100
From: @mlkersten
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-12-05 05:27:04 +0100
## Comment 10633
Date: 2008-11-26 14:36:16 +0100
From: @mlkersten
A few weeks ago i noticed that M5/SQL startup could be very slow.
Probably after a system crash, or quick stop.
I happened to get the same situation and was able to attach gdb.
It turned out that mserver was working in bbpinit/ diskscan
freeing bats. The unlink of a 69 and 111 GB files are
extremely slow. Taking ages.....(many minutes!)
0 0x0000003652cc8537 in unlink () from /lib64/libc.so.6
1 0x00002aaaab59bd6a in BBPdiskscan (parent=0x7fff681723a0 "bat/22")
at /ufs/mk/monet5//package/MonetDB/src/gdk/gdk_bbp.mx:3476
2 0x00002aaaab59b730 in BBPdiskscan (parent=0x2aaaab9ccf56 "bat")
at /ufs/mk/monet5//package/MonetDB/src/gdk/gdk_bbp.mx:3434
3 0x00002aaaab58b016 in BBPinit ()
## Comment 10634
Date: 2008-12-05 15:01:04 +0100
From: @sjoerdmullender
I don't think there is much we can do about this. The files need to be removed, and it just takes time to do so.
The only thing would be to fork() and do the unlink in the child process, but this makes the code much more complex (you need to administer the forked off children and wait for them), so I don't think this is the way we should proceed.
I propose to close this as a "won't fix".
## Comment 10635
Date: 2008-12-05 17:27:04 +0100
From: @mlkersten
Indeed. Correct parallel removal might cause other dependencies.
## Comment 10636
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2350868 at http://sourceforge.net/support/tracker.php?aid=2350868
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.
| [GDK]: slow bbp cleanup | https://api.github.com/repos/MonetDB/MonetDB/issues/1887/comments | 0 | 2020-11-30T10:06:08Z | 2024-06-28T13:27:49Z | https://github.com/MonetDB/MonetDB/issues/1887 | 753,338,195 | 1,887 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-25 05:27:47 +0100
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2008-12-05 03:25:21 +0100
## Comment 10628
Date: 2008-11-25 17:27:47 +0100
From: @skinkie
sql>\>/home/skinkie/betteroutput
sql>select distinct way_nds.way, way_nds.to_node from way_nds left join nodes_legacy on way_nds.to_node = nodes_legacy.id where nodes_legacy.id is NULL;
0 tuples
15386 tuples
File output:
+----------+-----------+
| way | to_node |
+==========+===========+
....
| 28539879 | 313483410 |
| 28539879 | 313483411 |
| 28539879 | 313483412 |
| 28539879 | 313483413 |
| 2
(that is line 15238, which ends with 2)
## Comment 10629
Date: 2008-11-25 17:41:19 +0100
From: @lsidir
I have run to that before. Since you are outputting to a file, the buffer is not flushed, so either you wait for a while or you exit mclient to force flushing. This is not the correct way to deal with the problem of course, I am just pointing out the problem and a work around.
## Comment 10630
Date: 2008-11-25 19:48:43 +0100
From: @skinkie
Thanks! Confirmed. I hope fflush could be implemented after each query.
## Comment 10631
Date: 2008-12-05 15:25:21 +0100
From: @sjoerdmullender
I consider this not a bug but a feature request since no output is lost (it's only buffered, when you exit mclient or close the output file, the data *is* flushed first).
A possible work around is to direct output back to stdout before looking at the output file (however, there is no way to then continue outputting to the file).
Despite this not (IMHO) being a bug, I have fixed it (in the stable branch) by adding a fflush just before a new line is read from stdin.
## Comment 10632
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2344251 at http://sourceforge.net/support/tracker.php?aid=2344251
| Output isn't complete | https://api.github.com/repos/MonetDB/MonetDB/issues/1886/comments | 0 | 2020-11-30T10:06:05Z | 2024-06-27T11:33:37Z | https://github.com/MonetDB/MonetDB/issues/1886 | 753,338,163 | 1,886 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-24 01:08:57 +0100
From: Floris Ouwendijk <<floris233>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2009-02-17 12:13:03 +0100
## Comment 10619
Date: 2008-11-24 13:08:57 +0100
From: Floris Ouwendijk <<floris233>>
While running multiple processes performing queries that add/remove documents, the system locked.
The following is a (gdb) dump of the threads, and for each of the threads the location.
The version of the database is the August 2008 tarball release.
(gdb) info threads
67 Thread 1157667136 (LWP 14091) 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
66 Thread 1166059840 (LWP 1404) 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
62 Thread 1149274432 (LWP 1400) 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
23 Thread 1124096320 (LWP 5202) 0x000000366440c0ed in sem_wait () from /lib64/libpthread.so.0
5 Thread 1107310912 (LWP 5041) 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
4 Thread 1098918208 (LWP 5040) 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
3 Thread 1090525504 (LWP 5039) 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
2 Thread 1082132800 (LWP 5038) 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
* 1 Thread 46912538871296 (LWP 5035) 0x00000036638c0e1b in __read_nocancel () from /lib64/libc.so.6
(gdb) thre 1
[Switching to thread 1 (Thread 46912538871296 (LWP 5035))]0 0x00000036638c0e1b in __read_nocancel () from /lib64/libc.so.6
(gdb) l
11979 MT_unset_lock(PF_UPDATE_LOCK, "pflock_begin: updateLock for update");
11980 } else {
11981 /* update in exclusive mode */
11982 MT_down_sema(PF_UPDATE_BARRIER, "pflock_begin: updateBarrier for retry");
11983 MT_set_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for writer");
11984 pf_writer = *wsid;
11985 MT_unset_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for writer");
11986 }
11987 return GDK_SUCCEED;
11988 }
(gdb) bt
0 0x00000036638c0e1b in __read_nocancel () from /lib64/libc.so.6
1 0x000000366386a617 in _IO_new_file_underflow () from /lib64/libc.so.6
2 0x000000366386930e in _IO_file_xsgetn_internal () from /lib64/libc.so.6
3 0x000000366385f692 in fread () from /lib64/libc.so.6
4 0x00002aaaacf63c63 in file_read (s=0x605d70, buf=0x67bbbe, elmsize=1, cnt=1) at stream.c:447
5 0x00002aaaacf63311 in stream_read (s=0x605d70, buf=0x67bbbe, elmsize=1, cnt=1) at stream.c:165
6 0x00002aaaabc329ff in readClient (c=0x2aaaabe99bc0) at monet_client.c:428
7 0x00002aaaabc3323a in serveClient (stk=0, lt=0x6536b8, res=0x7fffe6999c30) at monet_client.c:622
8 0x00002aaaabbfd54b in interpret (stk=0, lt=0x6536b8, res=0x7fffe6999c30) at monet_interpreter.c:808
9 0x00002aaaabc2dc48 in handleRequest (t=0x2aaaacf4c9a0, q=0x6ed8188, res=0x7fffe6999c30) at monet_queue.c:342
10 0x00002aaaabc2e145 in doRequest (t=0x2aaaacf4c9a0, preference=0x0) at monet_queue.c:368
11 0x00002aaaabc846dd in monetInterpreter (status=0x7fffe6999d34) at monet_process.c:45
12 0x0000000000401fa4 in main (argc=3, av=0x7fffe6999e58) at Mserver.c:234
(gdb) thre 2
[Switching to thread 2 (Thread 1082132800 (LWP 5038))]0 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
(gdb) l
11989
11990 /* query execution finishes; note that we have PF_SHORT_LOCK during this */
11991 int CMDpflock_end(lng *wsid)
11992 {
11993 int mode = ((*wsid) & (3LL << 30)) >> 30;
11994 lng nil = lng_nil;
11995
11996 if (mode == PF_MODE_DOCMGT) {
11997 /* last docmgt function yields the meta barrier
11998 */
(gdb) bt
0 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaaca238e8 in MT_sleep_ms (ms=5000) at gdk_posix.c:1770
2 0x00002aaaac788e36 in GDKvmtrim (limit=0x2aaaacd464c0) at gdk_utils.c:1350
3 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
4 0x00000036638ce86d in clone () from /lib64/libc.so.6
5 0x0000000000000000 in ?? ()
(gdb) thre 3
[Switching to thread 3 (Thread 1090525504 (LWP 5039))]0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
(gdb) l
11999 if (*wsid == pf_special) {
12000 pf_special = -1;
12001 } else {
12002 pf_ndocmgt--;
12003 }
12004 if (pf_ndocmgt == 0) {
12005 MT_up_sema(PF_META_BARRIER, "pflock_end: metaBarrier for docmgt");
12006 }
12007 } else {
12008 /* last active meta-information query releases meta-barrier
(gdb) bt
0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
1 0x00002aaaba0bbed0 in MAPIlisten (stk=2, lt=0x125e2e8, res=0x410010e0) at mapi.c:729
2 0x00002aaaabbfd54b in interpret (stk=2, lt=0x125e2e8, res=0x410010e0) at monet_interpreter.c:808
3 0x00002aaaabc2dc48 in handleRequest (t=0x2aaaacf4ca48, q=0x1258088, res=0x410010e0) at monet_queue.c:342
4 0x00002aaaabc2e145 in doRequest (t=0x2aaaacf4ca48, preference=0x0) at monet_queue.c:368
5 0x00002aaaabc846dd in monetInterpreter (status=0x7fffe6997544) at monet_process.c:45
6 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
7 0x00000036638ce86d in clone () from /lib64/libc.so.6
8 0x0000000000000000 in ?? ()
(gdb) thre 4
[Switching to thread 4 (Thread 1098918208 (LWP 5040))]0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
(gdb) l
12009 */
12010 BUN self_passed; /* this query uses meta-information functions? */
12011 BUN others_passed; /* there are multiple such queries active? */
12012
12013 self_passed = BUNlocate(ws_overlaps_ws, wsid, &nil);
12014 BUNdelHead(ws_overlaps_ws, wsid, FALSE); /* release all active info on this query */
12015 others_passed = BUNfnd(BATmirror(ws_overlaps_ws), &nil);
12016 if (self_passed != BUN_NONE && others_passed == BUN_NONE) {
12017 MT_up_sema(PF_META_BARRIER, "pflock_end: metaBarrier");
12018 }
(gdb) bt
0 0x00000036638c7db2 in __select_nocancel () from /lib64/libc.so.6
1 0x00002aaaba52bdda in shttpd_poll (ctx=0x41801920, milliseconds=200) at shttpd.c:2981
2 0x00002aaaba535638 in CMDrpcd_start (port=0x41801b80, open=0x41801b90 "\001", option=0x2aaabc127fd8 "") at xrpc_server.c:1005
3 0x00002aaaba52d037 in CMDrpcd_start_unpack11689948 (argc=4, argv=0x41801b70) at xrpc_server.glue.c:43
4 0x00002aaaabbfed91 in interpret (stk=3, lt=0x11c0418, res=0x418020e0) at monet_interpreter.c:1070
5 0x00002aaaabc2dc48 in handleRequest (t=0x2aaaacf4caf0, q=0x11f4768, res=0x418020e0) at monet_queue.c:342
6 0x00002aaaabc2e145 in doRequest (t=0x2aaaacf4caf0, preference=0x0) at monet_queue.c:368
7 0x00002aaaabc846dd in monetInterpreter (status=0x7fffe6998184) at monet_process.c:45
8 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
9 0x00000036638ce86d in clone () from /lib64/libc.so.6
10 0x0000000000000000 in ?? ()
(gdb) thre 5
[Switching to thread 5 (Thread 1107310912 (LWP 5041))]0 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
(gdb) l
12019
12020 /* last active update query releases update-barrier
12021 */
12022 if (pf_writer == *wsid) {
12023 /* finish in exclusive mode */
12024 pf_writer = -1;
12025 MT_up_sema(PF_UPDATE_BARRIER, "pflock_end: exclusive updateBarrier");
12026 } else if (mode != PF_MODE_RDONLY) {
12027 /* finish in concurrent mode */
12028 if (--pf_nreaders == 0)
(gdb) bt
0 0x000000366440d531 in __nanosleep_nocancel () from /lib64/libpthread.so.0
1 0x00002aaaaca238e8 in MT_sleep_ms (ms=30000) at gdk_posix.c:1770
2 0x00002aaab82c42cf in CMDsleep (secs=0x42001150) at alarm.c:145
3 0x00002aaab82c361a in CMDsleep_unpack2122305048 (argc=2, argv=0x42001140) at alarm.glue.c:43
4 0x00002aaaabbfed91 in interpret (stk=545, lt=0x66e308, res=0x420030e0) at monet_interpreter.c:1070
5 0x00002aaaabc0a3cb in interpret_seqblock (stk=545, lt=0x1363898, res=0x420030e0, scope=1) at monet_interpreter.c:2194
6 0x00002aaaabbfc98b in interpret (stk=546, lt=0x1363898, res=0x420030e0) at monet_interpreter.c:654
7 0x00002aaaabc01244 in interpret_while (stk=546, lt=0x11f07d0, res=0x420030e0) at monet_interpreter.c:1187
8 0x00002aaaabbfcc85 in interpret (stk=546, lt=0x11f07d0, res=0x420030e0) at monet_interpreter.c:721
9 0x00002aaaabc0a3cb in interpret_seqblock (stk=546, lt=0x11f0708, res=0x420030e0, scope=1) at monet_interpreter.c:2194
10 0x00002aaaabbfc98b in interpret (stk=4, lt=0x11f0708, res=0x420030e0) at monet_interpreter.c:654
11 0x00002aaaabbfe726 in interpret (stk=4, lt=0x11e5338, res=0x420030e0) at monet_interpreter.c:1044
12 0x00002aaaabc2dc48 in handleRequest (t=0x2aaaacf4cb98, q=0x1376c78, res=0x420030e0) at monet_queue.c:342
13 0x00002aaaabc2e145 in doRequest (t=0x2aaaacf4cb98, preference=0x0) at monet_queue.c:368
14 0x00002aaaabc846dd in monetInterpreter (status=0x7fffe6998ea4) at monet_process.c:45
15 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
16 0x00000036638ce86d in clone () from /lib64/libc.so.6
17 0x0000000000000000 in ?? ()
(gdb) thre 23
[Switching to thread 23 (Thread 1124096320 (LWP 5202))]0 0x000000366440c0ed in sem_wait () from /lib64/libpthread.so.0
(gdb) l
12029 MT_up_sema(PF_UPDATE_BARRIER, "pflock_end: updateBarrier");
12030 }
12031 }
12032 return GDK_SUCCEED;
12033 }
12034
12035 /* we are going to use a meta-information function that returns all collections/documents
12036 * thus we must block all new docmgt queries and wait for all active ones to finish
12037 */
12038 int CMDpflock_meta(lng *wsid)
(gdb) bt
0 0x000000366440c0ed in sem_wait () from /lib64/libpthread.so.0
1 0x00002aaab871e4da in CMDpflock_begin (wsid=0x42ffdd30) at pf_support.c:11959
2 0x00002aaab86e65ec in CMDpflock_begin_unpack57322442 (argc=2, argv=0x42ffdd20) at pf_support.glue.c:1906
3 0x00002aaaabbfed91 in interpret (stk=3185, lt=0x2aab5502c078, res=0x43003dc0) at monet_interpreter.c:1070
4 0x00002aaaabc0a3cb in interpret_seqblock (stk=3185, lt=0x2aab57e414b8, res=0x43003dc0, scope=1) at monet_interpreter.c:2194
5 0x00002aaaabbfc98b in interpret (stk=3571, lt=0x2aab55ef1228, res=0x43003dc0) at monet_interpreter.c:654
6 0x00002aaaabc0a3cb in interpret_seqblock (stk=3571, lt=0x2aab4dfe9308, res=0x43003dc0, scope=1) at monet_interpreter.c:2194
7 0x00002aaaabbfc98b in interpret (stk=3683, lt=0x2aab4dfe9308, res=0x43003dc0) at monet_interpreter.c:654
8 0x00002aaaabbfe726 in interpret (stk=3683, lt=0x2aab4e221688, res=0x43003dc0) at monet_interpreter.c:1044
9 0x00002aaaabc0a0cc in interpret_assignment (stk=3683, lt=0x2aab4e221638, res=0x43003dc0) at monet_interpreter.c:2146
10 0x00002aaaabbfc8fa in interpret (stk=3683, lt=0x2aab4e221638, res=0x43003dc0) at monet_interpreter.c:638
11 0x00002aaaabc0a3cb in interpret_seqblock (stk=3683, lt=0x2aab562f9580, res=0x43003dc0, scope=1) at monet_interpreter.c:2194
12 0x00002aaaabbfc98b in interpret (stk=1, lt=0x2aab562f9580, res=0x43003dc0) at monet_interpreter.c:654
13 0x00002aaaab1a2667 in CMDcatch (stk=1, lt=0x2aab562f9558, res=0x43003dc0) at builtin.c:1064
14 0x00002aaaabbfd54b in interpret (stk=1, lt=0x2aab562f9558, res=0x43003dc0) at monet_interpreter.c:808
15 0x00002aaaabc0a0cc in interpret_assignment (stk=1, lt=0x2aab562f9508, res=0x43003dc0) at monet_interpreter.c:2146
16 0x00002aaaabbfc8fa in interpret (stk=1, lt=0x2aab562f9508, res=0x43003dc0) at monet_interpreter.c:638
17 0x00002aaaabc0a3cb in interpret_seqblock (stk=1, lt=0x2aab557a6f88, res=0x43003dc0, scope=0) at monet_interpreter.c:2194
18 0x00002aaaabbfc98b in interpret (stk=1, lt=0x2aab4e1a3218, res=0x43003dc0) at monet_interpreter.c:654
19 0x00002aaab9b5c48d in xquery_tree_exec (ctx=0x155a1c8, t=0x2aab4e1a3218, repeat=0) at pathfinder.c:247
20 0x00002aaab9b5c9ee in xquery_mil_exec (ctx=0x155a1c8,
buf=0x2aab5c069880 "var tijah_scoreDB;\nvar tijah_ftiTape;\ntijah_ftiTape := new (str, bat);\nvar time_load;\nvar time_query;\nvar time_print;\nvar a0000;\nvar a0001;\nvar a0002;\nvar a0003;\nvar a0004;\nvar a0005;\nvar a0006;\nvar a"...) at pathfinder.c:305
21 0x00002aaab9b5d299 in xquery_compile_exec (ctx=0x155a1c8, options=2, url=0x161de49 "pf:del-doc(\"prepared67113.data\")\n", is_url=0, prologue=0x43004330,
query=0x43004328, epilogue=0x43004320, nsurl=0x0) at pathfinder.c:439
22 0x00002aaab9b63065 in xquery_prepare (ctx=0x155a1c8, usec=5233816459, query=0x161de49 "pf:del-doc(\"prepared67113.data\")\n") at pathfinder.c:2113
23 0x00002aaab9b63694 in xquery_client_engine (mc=0x2aaaba2bf0a8) at pathfinder.c:2256
24 0x00002aaaba0baf7a in mapi_client_engine (FC=0x2aaaba2bf0a8) at mapi.c:316
25 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
26 0x00000036638ce86d in clone () from /lib64/libc.so.6
27 0x0000000000000000 in ?? ()
(gdb) thre 62
[Switching to thread 62 (Thread 1149274432 (LWP 1400))]0 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
(gdb) l
12039 {
12040 int mode = ((*wsid) & (3LL << 30)) >> 30;
12041 lng nil = lng_nil;
12042 BUN others_passed; /* there are multiple such queries active? */
12043
12044 MT_set_lock(PF_SHORT_LOCK, "pflock_meta: shortLock precheck");
12045 if (*wsid == pf_special || BUNlocate(ws_overlaps_ws, wsid, &nil) != BUN_NONE) {
12046 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock precheck");
12047 return GDK_SUCCEED; /* already got permission to proceed */
12048 }
(gdb) bt
0 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
1 0x00000036644088b5 in _L_mutex_lock_107 () from /lib64/libpthread.so.0
2 0x0000003664408343 in pthread_mutex_lock () from /lib64/libpthread.so.0
3 0x00002aaab871ef20 in CMDpflock_meta (wsid=0x44800010) at pf_support.c:12066
4 0x00002aaab86e6782 in CMDpflock_meta_unpack40025922 (argc=2, argv=0x44800000) at pf_support.glue.c:1948
5 0x00002aaaabbfed91 in interpret (stk=1641, lt=0x7556ec8, res=0x44801e70) at monet_interpreter.c:1070
6 0x00002aaaabbfcb0f in interpret (stk=1641, lt=0xca27f08, res=0x44801e70) at monet_interpreter.c:683
7 0x00002aaaabc0a3cb in interpret_seqblock (stk=1641, lt=0xfddb428, res=0x44801e70, scope=1) at monet_interpreter.c:2194
8 0x00002aaaabbfc98b in interpret (stk=3889, lt=0xfddb428, res=0x44801e70) at monet_interpreter.c:654
9 0x00002aaaabc0a3cb in interpret_seqblock (stk=3889, lt=0x6768148, res=0x44801e70, scope=1) at monet_interpreter.c:2194
10 0x00002aaaabbfc98b in interpret (stk=1589, lt=0x6768148, res=0x44801e70) at monet_interpreter.c:654
11 0x00002aaaabbfe726 in interpret (stk=1589, lt=0x67b47d0, res=0x44801e70) at monet_interpreter.c:1044
12 0x00002aaaabbfb887 in interpret_params (stk=1589, lt=0xecdff98, params=0x448020a0, fcn_nme=0xd7253c8 "cross") at monet_interpreter.c:282
13 0x00002aaaabbfddcd in interpret (stk=1589, lt=0xecdff78, res=0x44806dc0) at monet_interpreter.c:884
14 0x00002aaaabc0a0cc in interpret_assignment (stk=1589, lt=0xecdff28, res=0x44806dc0) at monet_interpreter.c:2146
15 0x00002aaaabbfc8fa in interpret (stk=1589, lt=0xecdff28, res=0x44806dc0) at monet_interpreter.c:638
16 0x00002aaaabc0a3cb in interpret_seqblock (stk=1589, lt=0xbf86300, res=0x44806dc0, scope=1) at monet_interpreter.c:2194
17 0x00002aaaabbfc98b in interpret (stk=6, lt=0xbf86300, res=0x44806dc0) at monet_interpreter.c:654
18 0x00002aaaab1a2667 in CMDcatch (stk=6, lt=0xbf862d8, res=0x44806dc0) at builtin.c:1064
19 0x00002aaaabbfd54b in interpret (stk=6, lt=0xbf862d8, res=0x44806dc0) at monet_interpreter.c:808
20 0x00002aaaabc0a0cc in interpret_assignment (stk=6, lt=0xbf86288, res=0x44806dc0) at monet_interpreter.c:2146
21 0x00002aaaabbfc8fa in interpret (stk=6, lt=0xbf86288, res=0x44806dc0) at monet_interpreter.c:638
22 0x00002aaaabc0a3cb in interpret_seqblock (stk=6, lt=0xdb31d18, res=0x44806dc0, scope=0) at monet_interpreter.c:2194
23 0x00002aaaabbfc98b in interpret (stk=6, lt=0xc825908, res=0x44806dc0) at monet_interpreter.c:654
24 0x00002aaab9b5c48d in xquery_tree_exec (ctx=0xc293788, t=0xc825908, repeat=0) at pathfinder.c:247
25 0x00002aaab9b5c9ee in xquery_mil_exec (ctx=0xc293788,
buf=0xf1f3fd0 "var tijah_scoreDB;\nvar tijah_ftiTape;\nvar time_load;\nvar time_query;\nvar time_print;\nvar a0000;\nvar a0001;\nvar a0002;\nvar a0003;\nvar a0004;\nvar a0005;\nvar a0006;\nvar a0007;\nvar a0008;\nvar a0009;\nvar a"...) at pathfinder.c:305
26 0x00002aaab9b5d299 in xquery_compile_exec (ctx=0xc293788, options=2, url=0xd6e5aa9 "count(pf:collections()[.=\"cons02_log.xml\"])", is_url=0,
prologue=0x44807330, query=0x44807328, epilogue=0x44807320, nsurl=0x0) at pathfinder.c:439
27 0x00002aaab9b63065 in xquery_prepare (ctx=0xc293788, usec=5271918731, query=0xd6e5aa9 "count(pf:collections()[.=\"cons02_log.xml\"])") at pathfinder.c:2113
28 0x00002aaab9b63694 in xquery_client_engine (mc=0x2aaaba2bf2b0) at pathfinder.c:2256
29 0x00002aaaba0baf7a in mapi_client_engine (FC=0x2aaaba2bf2b0) at mapi.c:316
30 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
31 0x00000036638ce86d in clone () from /lib64/libc.so.6
32 0x0000000000000000 in ?? ()
(gdb) thre 66
[Switching to thread 66 (Thread 1166059840 (LWP 1404))]0 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
(gdb) l
12049 if (mode == PF_MODE_DOCMGT) {
12050 /* SPECIAL CASE: a meta function inside a docmgt function.
12051 * now we must wait for potential other docmgts to finish first
12052 */
12053 int reapply_barrier = (pf_ndocmgt > 1);
12054 if (reapply_barrier) pf_ndocmgt--;
12055 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: metaLock precheck");
12056 if (reapply_barrier) {
12057 MT_down_sema(PF_META_BARRIER, "pflock_meta: metaBarrier for convert");
12058 MT_set_lock(PF_SHORT_LOCK, "pflock_meta: shortLock special");
(gdb) bt
0 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
1 0x00000036644088b5 in _L_mutex_lock_107 () from /lib64/libpthread.so.0
2 0x0000003664408343 in pthread_mutex_lock () from /lib64/libpthread.so.0
3 0x00002aaab871e3a8 in CMDpflock_begin (wsid=0x45802d30) at pf_support.c:11954
4 0x00002aaab86e65ec in CMDpflock_begin_unpack57322442 (argc=2, argv=0x45802d20) at pf_support.glue.c:1906
5 0x00002aaaabbfed91 in interpret (stk=1577, lt=0xeb91088, res=0x45808dc0) at monet_interpreter.c:1070
6 0x00002aaaabc0a3cb in interpret_seqblock (stk=1577, lt=0x30d93c8, res=0x45808dc0, scope=1) at monet_interpreter.c:2194
7 0x00002aaaabbfc98b in interpret (stk=1322, lt=0x8fea0e8, res=0x45808dc0) at monet_interpreter.c:654
8 0x00002aaaabc0a3cb in interpret_seqblock (stk=1322, lt=0x8fea308, res=0x45808dc0, scope=1) at monet_interpreter.c:2194
9 0x00002aaaabbfc98b in interpret (stk=1667, lt=0x8fea308, res=0x45808dc0) at monet_interpreter.c:654
10 0x00002aaaabbfe726 in interpret (stk=1667, lt=0x5e42748, res=0x45808dc0) at monet_interpreter.c:1044
11 0x00002aaaabc0a0cc in interpret_assignment (stk=1667, lt=0x5e426f8, res=0x45808dc0) at monet_interpreter.c:2146
12 0x00002aaaabbfc8fa in interpret (stk=1667, lt=0x5e426f8, res=0x45808dc0) at monet_interpreter.c:638
13 0x00002aaaabc0a3cb in interpret_seqblock (stk=1667, lt=0x5843be0, res=0x45808dc0, scope=1) at monet_interpreter.c:2194
14 0x00002aaaabbfc98b in interpret (stk=10, lt=0x5843be0, res=0x45808dc0) at monet_interpreter.c:654
15 0x00002aaaab1a2667 in CMDcatch (stk=10, lt=0x5843bb8, res=0x45808dc0) at builtin.c:1064
16 0x00002aaaabbfd54b in interpret (stk=10, lt=0x5843bb8, res=0x45808dc0) at monet_interpreter.c:808
17 0x00002aaaabc0a0cc in interpret_assignment (stk=10, lt=0x5843b68, res=0x45808dc0) at monet_interpreter.c:2146
18 0x00002aaaabbfc8fa in interpret (stk=10, lt=0x5843b68, res=0x45808dc0) at monet_interpreter.c:638
19 0x00002aaaabc0a3cb in interpret_seqblock (stk=10, lt=0x73351c8, res=0x45808dc0, scope=0) at monet_interpreter.c:2194
20 0x00002aaaabbfc98b in interpret (stk=10, lt=0x3afd8b8, res=0x45808dc0) at monet_interpreter.c:654
21 0x00002aaab9b5c48d in xquery_tree_exec (ctx=0x11fc808, t=0x3afd8b8, repeat=0) at pathfinder.c:247
22 0x00002aaab9b5c9ee in xquery_mil_exec (ctx=0x11fc808,
buf=0xf2209f0 "var tijah_scoreDB;\nvar tijah_ftiTape;\ntijah_ftiTape := new (str, bat);\nvar time_load;\nvar time_query;\nvar time_print;\nvar a0000;\nvar a0001;\nvar a0002;\nvar a0003;\nvar a0004;\nvar a0005;\nvar a0006;\nvar a"...) at pathfinder.c:305
23 0x00002aaab9b5d299 in xquery_compile_exec (ctx=0x11fc808, options=2,
url=0x7e18e19 "for $d in pf:documents()[@collection='cons02_log.xml']//text() return pf:del-doc($d)\n", is_url=0, prologue=0x45809330, query=0x45809328,
epilogue=0x45809320, nsurl=0x0) at pathfinder.c:439
24 0x00002aaab9b63065 in xquery_prepare (ctx=0x11fc808, usec=5281945585,
query=0x7e18e19 "for $d in pf:documents()[@collection='cons02_log.xml']//text() return pf:del-doc($d)\n") at pathfinder.c:2113
25 0x00002aaab9b63694 in xquery_client_engine (mc=0x2aaaba2bf450) at pathfinder.c:2256
26 0x00002aaaba0baf7a in mapi_client_engine (FC=0x2aaaba2bf450) at mapi.c:316
27 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
28 0x00000036638ce86d in clone () from /lib64/libc.so.6
29 0x0000000000000000 in ?? ()
(gdb) thre 67
[Switching to thread 67 (Thread 1157667136 (LWP 14091))]0 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
(gdb) l
12059 pf_special = *wsid;
12060 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock special");
12061 }
12062 return GDK_SUCCEED;
12063 }
12064 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock precheck");
12065
12066 MT_set_lock(PF_META_LOCK, "pflock_meta: metaLock");
12067 MT_set_lock(PF_SHORT_LOCK, "pflock_meta: shortLock insert");
12068 others_passed = BUNfnd(BATmirror(ws_overlaps_ws), &nil);
(gdb) bt
0 0x000000366440c888 in __lll_mutex_lock_wait () from /lib64/libpthread.so.0
1 0x00000036644088b5 in _L_mutex_lock_107 () from /lib64/libpthread.so.0
2 0x0000003664408343 in pthread_mutex_lock () from /lib64/libpthread.so.0
3 0x00002aaab871e3a8 in CMDpflock_begin (wsid=0x45001d30) at pf_support.c:11954
4 0x00002aaab86e65ec in CMDpflock_begin_unpack57322442 (argc=2, argv=0x45001d20) at pf_support.glue.c:1906
5 0x00002aaaabbfed91 in interpret (stk=1373, lt=0xaabdec8, res=0x45007dc0) at monet_interpreter.c:1070
6 0x00002aaaabc0a3cb in interpret_seqblock (stk=1373, lt=0x4022388, res=0x45007dc0, scope=1) at monet_interpreter.c:2194
7 0x00002aaaabbfc98b in interpret (stk=3307, lt=0xed39118, res=0x45007dc0) at monet_interpreter.c:654
8 0x00002aaaabc0a3cb in interpret_seqblock (stk=3307, lt=0x9864c88, res=0x45007dc0, scope=1) at monet_interpreter.c:2194
9 0x00002aaaabbfc98b in interpret (stk=3409, lt=0x9864c88, res=0x45007dc0) at monet_interpreter.c:654
10 0x00002aaaabbfe726 in interpret (stk=3409, lt=0x98006a8, res=0x45007dc0) at monet_interpreter.c:1044
11 0x00002aaaabc0a0cc in interpret_assignment (stk=3409, lt=0x9800658, res=0x45007dc0) at monet_interpreter.c:2146
12 0x00002aaaabbfc8fa in interpret (stk=3409, lt=0x9800658, res=0x45007dc0) at monet_interpreter.c:638
13 0x00002aaaabc0a3cb in interpret_seqblock (stk=3409, lt=0xa082db0, res=0x45007dc0, scope=1) at monet_interpreter.c:2194
14 0x00002aaaabbfc98b in interpret (stk=5, lt=0xa082db0, res=0x45007dc0) at monet_interpreter.c:654
15 0x00002aaaab1a2667 in CMDcatch (stk=5, lt=0xa082d88, res=0x45007dc0) at builtin.c:1064
16 0x00002aaaabbfd54b in interpret (stk=5, lt=0xa082d88, res=0x45007dc0) at monet_interpreter.c:808
17 0x00002aaaabc0a0cc in interpret_assignment (stk=5, lt=0xa082d38, res=0x45007dc0) at monet_interpreter.c:2146
18 0x00002aaaabbfc8fa in interpret (stk=5, lt=0xa082d38, res=0x45007dc0) at monet_interpreter.c:638
19 0x00002aaaabc0a3cb in interpret_seqblock (stk=5, lt=0xdc50e98, res=0x45007dc0, scope=0) at monet_interpreter.c:2194
20 0x00002aaaabbfc98b in interpret (stk=5, lt=0xc0eb0b8, res=0x45007dc0) at monet_interpreter.c:654
21 0x00002aaab9b5c48d in xquery_tree_exec (ctx=0xb41c0f8, t=0xc0eb0b8, repeat=0) at pathfinder.c:247
22 0x00002aaab9b5c9ee in xquery_mil_exec (ctx=0xb41c0f8,
buf=0xed6be40 "var tijah_scoreDB;\nvar tijah_ftiTape;\ntijah_ftiTape := new (str, bat);\nvar time_load;\nvar time_query;\nvar time_print;\nvar a0000;\nvar a0001;\nvar a0002;\nvar a0003;\nvar a0004;\nvar a0005;\nvar a0006;\nvar a"...) at pathfinder.c:305
23 0x00002aaab9b5d299 in xquery_compile_exec (ctx=0xb41c0f8, options=2,
url=0xf8faf39 "for $d in pf:documents()[@collection='cons02_log.xml']//text() return pf:del-doc($d)\n", is_url=0, prologue=0x45008330, query=0x45008328,
epilogue=0x45008320, nsurl=0x0) at pathfinder.c:439
24 0x00002aaab9b63065 in xquery_prepare (ctx=0xb41c0f8, usec=235526232460,
query=0xf8faf39 "for $d in pf:documents()[@collection='cons02_log.xml']//text() return pf:del-doc($d)\n") at pathfinder.c:2113
25 0x00002aaab9b63694 in xquery_client_engine (mc=0x2aaaba2bf248) at pathfinder.c:2256
26 0x00002aaaba0baf7a in mapi_client_engine (FC=0x2aaaba2bf248) at mapi.c:316
27 0x00000036644062f7 in start_thread () from /lib64/libpthread.so.0
28 0x00000036638ce86d in clone () from /lib64/libc.so.6
29 0x0000000000000000 in ?? ()
## Comment 10620
Date: 2008-11-24 15:57:47 +0100
From: @peterboncz
The trace shows the following:
(1) MIL server thread
(2) BBPtrim thread
(3) xrpc background server
(4) checkpoint background thread
(5) pf:del-doc("prepared67113.data")
(6) count(pf:collections()[.="cons02_log.xml"])
(7) for $d in pf:documents()[@collection='cons02_log.xml']//text() return pf:del-doc($d)
(8) for $d in pf:documents()[@collection='cons02_log.xml']//text() return pf:del-doc($d)
The first question for NFI is why threads (7) and (8) are removing the same documents concurrently. Maybe thread (5) is even removing a document covered by both (7) and (8) This will necessarily lead to (correct) runtime errors.
analysis continues.. NFI feedback appreciated
## Comment 10621
Date: 2008-11-24 17:43:17 +0100
From: @peterboncz
For clarity, now useing the gdb thread numbers:
(1) Mserver MIL console, blocked on read()
(2) Mserver vmtrim() thread, blocked on timer
(3) MIL interpreter, blocked on socket
(4) XRPC server, blocked on socket
(5) pf_logmanager() checkpoint thread (pathfinder.mx), blocked on timer
(23) pf:del-doc("prepared67113.data"), blocked on PFlock_begin on PF_META_BARRIER (11959)
(63) count(pf:collections()[.="cons02_log.xml"]), blocked in PFlock_meta() on
sema PF_LOCK_META (12066)
(66) for $d in pf:documents()[@collection='cons02_log.xml']//text() return
pf:del-doc($d), blocked in PFlock_begin() on PF_LOCK_META
(67) for $d in pf:documents()[@collection='cons02_log.xml']//text() return
pf:del-doc($d), blocked in PFlock_begin() on PF_LOCK_META
code is below. So the last three queries are blocked because the meta-lock is taken. It is held by the pf:del-doc query, which is help up unexpectedly by getting the meta semaphore.
The problem thus is that some query has left (maybe with an error) that had the meta semaphore, but did not give it back..
11944 /* query execution starts */
11945 int CMDpflock_begin(lng *wsid)
11946 {
11947 int mode = ((*wsid) & (3LL << 30)) >> 30;
11948 if (mode == PF_MODE_RDONLY)
11949 return GDK_SUCCEED;
11950
11951 if (mode == PF_MODE_DOCMGT) {
11952 /* multiple docmgts may be active in parallel. the first takes the meta-barrier */
11953 int take_barrier;
11954 MT_set_lock(PF_META_LOCK, "pflock_begin: metaLock for mgmt");
11955 MT_set_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for mgmt");
11956 take_barrier = (pf_ndocmgt++ == 0);
11957 MT_unset_lock(PF_SHORT_LOCK, "pflock_begin: shirtLock for mgmt");
11958 if (take_barrier) {
11959 MT_down_sema(PF_META_BARRIER, "pflock_begin: metaBarrier");
11960 }
11961 MT_unset_lock(PF_META_LOCK, "pflock_begin: metaLock for mgmt");
11962 return GDK_SUCCEED;
11963 }
11964
11965 /* we only have update queries below this point; first check if we are in exclusive retry mode */
11966 MT_set_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for convoy"); /* protects pf_convoy */
11967 if (mode == PF_MODE_RETRY) {
11968 pf_convoy += PF_CONVOY; /* re-try: schedule a convoy */
11969 } else if (pf_convoy > 0) {
11970 mode = PF_MODE_RETRY; pf_convoy--; /* convert to exclusive execution due to convoy */
11971 }
11972 MT_unset_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for convoy");
11973
11974 if (mode == PF_MODE_UPDATE) {
11975 /* update in concurrent mode */
11976 MT_set_lock(PF_UPDATE_LOCK, "pflock_begin: updateLock for update");
11977 if (pf_nreaders++ == 0)
11978 MT_down_sema(PF_UPDATE_BARRIER, "pflock_begin: updateBarrier for update");
11979 MT_unset_lock(PF_UPDATE_LOCK, "pflock_begin: updateLock for update");
11980 } else {
11981 /* update in exclusive mode */
11982 MT_down_sema(PF_UPDATE_BARRIER, "pflock_begin: updateBarrier for retry");
11983 MT_set_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for writer");
11984 pf_writer = *wsid;
11985 MT_unset_lock(PF_SHORT_LOCK, "pflock_begin: shortLock for writer");
11986 }
11987 return GDK_SUCCEED;
11988 }
12035 /* we are going to use a meta-information function that returns all collections/documents
12036 * thus we must block all new docmgt queries and wait for all active ones to finish
12037 */
12038 int CMDpflock_meta(lng *wsid)
12039 {
12040 int mode = ((*wsid) & (3LL << 30)) >> 30;
12041 lng nil = lng_nil;
12042 BUN others_passed; /* there are multiple such queries active? */
12043
12044 MT_set_lock(PF_SHORT_LOCK, "pflock_meta: shortLock precheck");
12045 if (*wsid == pf_special || BUNlocate(ws_overlaps_ws, wsid, &nil) != BUN_NONE) {
12046 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock precheck");
12047 return GDK_SUCCEED; /* already got permission to proceed */
12048 }
12049 if (mode == PF_MODE_DOCMGT) {
12050 /* SPECIAL CASE: a meta function inside a docmgt function.
12051 * now we must wait for potential other docmgts to finish first
12052 */
12053 int reapply_barrier = (pf_ndocmgt > 1);
12054 if (reapply_barrier) pf_ndocmgt--;
12055 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: metaLock precheck");
12056 if (reapply_barrier) {
12057 MT_down_sema(PF_META_BARRIER, "pflock_meta: metaBarrier for convert");
12058 MT_set_lock(PF_SHORT_LOCK, "pflock_meta: shortLock special");
12059 pf_special = *wsid;
12060 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock special");
12061 }
12062 return GDK_SUCCEED;
12063 }
12064 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock precheck");
12065
12066 MT_set_lock(PF_META_LOCK, "pflock_meta: metaLock");
12067 MT_set_lock(PF_SHORT_LOCK, "pflock_meta: shortLock insert");
12068 others_passed = BUNfnd(BATmirror(ws_overlaps_ws), &nil);
12069 BUNins(ws_overlaps_ws, wsid, &nil, FALSE);
12070 MT_unset_lock(PF_SHORT_LOCK, "pflock_meta: shortLock insert");
12071 if (others_passed == BUN_NONE) {
12072 /* first query with meta function: get barrier */
12073 MT_down_sema(PF_META_BARRIER, "pflock_meta: metaBarrier");
12074 }
12075 MT_unset_lock(PF_META_LOCK, "pflock_meta: metaLock");
12076 return GDK_SUCCEED;
12077 }
## Comment 10622
Date: 2008-11-25 01:10:39 +0100
From: @peterboncz
race was found. BUGFIX 2338542
fixes race condition when a docmgt query with a meta-command like:
for $d in pf:documents() return pf:del-doc($d)
is followed shortly by another docmgt query:
pf:del-doc("x")
problem is that because the docmgt counter is increased by
the second query arriving (though the first one prevents it
using a META barrier from starting), the increase of that counter
makes the pflock_end of the first query (its upgrade fromdocmgt
to meta query makes it a "special") fail to yield that META
barrier -- it should in fact do so for every special query
finishing no matter the docmgt count.
FIX IS NOT APPLIED IN STABLE YET (0_24) ONLY HEAD. NFI: do not use HEAD now, it is too raw!! Rather get 0-24 and apply:
-bash-3.1$ cvs diff pf_support.mx
Index: pf_support.mx
===================================================================
RCS file: /cvsroot/monetdb/pathfinder/runtime/pf_support.mx,v
retrieving revision 1.299.2.9
diff -r1.299.2.9 pf_support.mx
8209a8210
> MT_up_sema(PF_META_BARRIER, "pflock_end: metaBarrier for special docmgt");
8212,8213d8212
< }
< if (pf_ndocmgt == 0) {
-bash-3.1$
## Comment 10623
Date: 2008-11-25 12:04:09 +0100
From: @lsidir
The bugfix has also been applied to the Nov2008 branch (but not part of the release, it will be in a upcoming bugfix release). However, the nightly builds include the fix.
## Comment 10624
Date: 2009-02-16 13:37:59 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test.
## Comment 10625
Date: 2009-02-17 11:41:08 +0100
From: @lsidir
Stefan, I don't think we can find a test for this problem. It is a race condition that I doubt if it makes any sense to try to reproduce it automatically during night tests.
## Comment 10626
Date: 2009-02-17 12:13:03 +0100
From: @drstmane
I agree with Lefteris that an automatic test is not really feasible for this one.
Thanks for the check and comment!
## Comment 10627
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2338524 at http://sourceforge.net/support/tracker.php?aid=2338524
| Deadlock on barrier | https://api.github.com/repos/MonetDB/MonetDB/issues/1885/comments | 0 | 2020-11-30T10:06:01Z | 2024-06-27T11:33:36Z | https://github.com/MonetDB/MonetDB/issues/1885 | 753,338,114 | 1,885 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-23 08:16:49 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-02-16 10:16:32 +0100
## Comment 10614
Date: 2008-11-23 20:16:49 +0100
From: @skinkie
I'm sorry I cannot provide more details; I get a segmentation fault after trying to load a big batch, which fails again. And when I try to connect to a just started monetdb server with mclient, mserver5 segfaults.
(gdb) bt
0 0x00007f0b2c3c93c0 in temp_create () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
1 0x00007f0b2c3c75fd in load_delta () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
2 0x00007f0b2c3bdaf6 in load_table () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
3 0x00007f0b2c3be132 in load_trans () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
4 0x00007f0b2c3c2a17 in store_init () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
5 0x00007f0b2c39b413 in mvc_init () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
6 0x00007f0b2c3465a0 in SQLinit () from /opt/monetdb/lib/MonetDB5/lib/lib_sql.so
7 0x00007f0b3e338283 in initScenario () from /opt/monetdb/lib/libmonetdb5.so.0
8 0x00007f0b3e30a56d in MSscheduleClient () from /opt/monetdb/lib/libmonetdb5.so.0
9 0x00007f0b2f14bcb4 in doChallenge () from /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.so
10 0x00007f0b2f14c947 in SERVERlistenThread () from /opt/monetdb/lib/MonetDB5/lib/lib_mal_mapi.so
11 0x00007f0b3c805097 in start_thread () from /lib/libpthread.so.0
12 0x00007f0b3b52bcad in clone () from /lib/libc.so.6
13 0x0000000000000000 in ?? ()
## Comment 10615
Date: 2009-02-11 21:04:25 +0100
From: @njnes
fixed
## Comment 10616
Date: 2009-02-16 10:49:22 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test for this one.
## Comment 10617
Date: 2009-02-16 22:16:32 +0100
From: @njnes
given the limited amount of info on the bug report adding a test seems close to impossible. So closing.
## Comment 10618
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2334283 at http://sourceforge.net/support/tracker.php?aid=2334283
| segfault in temp_create | https://api.github.com/repos/MonetDB/MonetDB/issues/1884/comments | 0 | 2020-11-30T10:05:58Z | 2024-06-27T11:33:35Z | https://github.com/MonetDB/MonetDB/issues/1884 | 753,338,072 | 1,884 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-23 03:26:59 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-12-16 10:59:46 +0100
## Comment 10611
Date: 2008-11-23 15:26:59 +0100
From: @skinkie
I don't know if I understand the specs;
select bla as y from (select 'hello' as bla) as q where y = 'hello';
!SELECT: identifier 'y' unknown
Shouldn't that work the same as:
select bla as y from (select 'hello' as bla) as q where bla = 'hello';
## Comment 10612
Date: 2008-12-16 10:59:46 +0100
From: @romulogoncalves
This is not considered a bug. The right way to write your query is like the second the query.
bla as y
It is used when you return the result to rename the column name. You can't use this alias in the where clause ;)
I will close this bug and set it as invalid...
## Comment 10613
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2333119 at http://sourceforge.net/support/tracker.php?aid=2333119
| SQL92? 'AS' | https://api.github.com/repos/MonetDB/MonetDB/issues/1883/comments | 0 | 2020-11-30T10:05:55Z | 2024-06-28T13:27:49Z | https://github.com/MonetDB/MonetDB/issues/1883 | 753,338,031 | 1,883 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-20 01:33:33 +0100
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-02-16 10:20:31 +0100
## Comment 10602
Date: 2008-11-20 01:33:33 +0100
From: @skinkie
Before anyone starts about 'I cannot reproduce this bug'; you can request (or already have) an account to this machine.
What I do;
START TRANSACTION;
CREATE TABLE nodes_legacy (id serial, long integer, lat integer, username varchar(255), timestamp timestamptz);
CREATE TABLE node_tags (node integer, k varchar(255), v varchar(1024), primary key (node, k), foreign key(node) references nodes_legacy);
COPY 6330269 RECORDS INTO nodes_legacy from '/tmp/import/nodes.csv' USING DELIMITERS ',', '\n', '''';
COPY 5768152 RECORDS INTO node_tags from '/tmp/import/node_tags.csv' USING DELIMITERS ',', '\n', '''';
COMMIT;
Sample of nodes.csv:
123350, 608491291, 51499150, 'raskas', 2007-05-31T19:44:09Z
123351, 608610167, 51501482, 'raskas', 2007-05-31T19:44:08Z
123352, 608639476, 51508729, 'raskas', 2007-05-31T19:44:09Z
Sample of node_tags.csv
123379, 'created_by', 'YahooApplet 1.0'
123382, 'created_by', 'YahooApplet 1.0'
123383, 'created_by', 'YahooApplet 1.0'
gdb --args /opt/monetdb/bin/mserver5 --daemon=yes --dbinit="include sql;"
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) run
Starting program: /opt/monetdb/bin/mserver5 --daemon=yes --dbinit=include\ sql\;
[Thread debugging using libthread_db enabled]
[New Thread 0xb6f726c0 (LWP 18157)]
[New Thread 0xb3771b90 (LWP 18160)]
MonetDB server v5.9.0, based on kernel v1.27.0
Serving database 'demo', using 1 thread
Compiled for i686-pc-linux-gnu/32bit with 32bit 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 /opt/monetdb/etc/monetdb5.conf)
[New Thread 0xb27a3b90 (LWP 18162)]
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
MonetDB/SQL module v2.27.0 loaded
mserver5: ../../../src/gdk/gdk_bat.mx:1746: void_inplace: Assertion `BATcount(b) > (id -b->H->seq)' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb27a3b90 (LWP 18162)]
0xb800d424 in __kernel_vsyscall ()
(gdb) bt
0 0xb800d424 in __kernel_vsyscall ()
1 0xb6fe5670 in raise () from /lib/libc.so.6
2 0xb6fe6eb8 in abort () from /lib/libc.so.6
3 0xb6fde64e in __assert_fail () from /lib/libc.so.6
4 0xb7b38c24 in void_inplace (b=0x87dc100, id=164, val=0x8e9ad6c, force=1 '\001') at ../../../src/gdk/gdk_bat.mx:1746
5 0xb7b38f44 in void_replace_bat (b=0x87dc100, u=0x87e3ad8, force=1 '\001') at ../../../src/gdk/gdk_bat.mx:1771
6 0xb234213d in load_delta (bat=0x8e99458, bid=147, ubid=284, type=13) at ../../../../src/storage/bat/bat_storage.mx:423
7 0xb23421f4 in load_bat (bat=0x8e99458, type=13) at ../../../../src/storage/bat/bat_storage.mx:440
8 0xb23426c1 in create_col (tr=0x8e532a8, c=0x8e993c0) at ../../../../src/storage/bat/bat_storage.mx:543
9 0xb23346fb in bootstrap_create_column (tr=0x8e532a8, t=0x8e920b8, name=0xb2379881 "default",
sqltype=0xb2379b0e "varchar", digi1970-01-01 01:34:08 +0100) at ../../../src/storage/store.mx:1082
10 0xb2335a1f in store_init (debug=0, store=store_bat, logdir=0x87ee3bc "/opt/monetdb/var/MonetDB5/sql_logs",
dbname=0x87ee2cc "demo", stk=0) at ../../../src/storage/store.mx:1304
11 0xb2308c1a in mvc_init (debug=0, store=store_bat, stk=0) at ../../../src/server/sql_mvc.mx:268
12 0xb22aa109 in SQLinit (c=0x804d3fc) at ../../../../src/backends/monet5/sql_scenario.mx:235
13 0xb7f927f4 in initScenario (c=0x804d3fc, s=0xb7fa9888) at ../../../src/mal/mal_scenario.mx:260
14 0xb7f932d4 in setScenario (c=0x804d3fc, nme=0x8d9b323 "sql") at ../../../src/mal/mal_scenario.mx:504
15 0xb7f5b38f in MSscheduleClient (command=0x8d9b2e8 "LIT", challenge=0xb27a32a0 "9S9SSENV", fin=0x87cb0a8,
fout=0x8d98d18) at ../../../src/mal/mal_session.mx:342
16 0xb2ca64a6 in doChallenge (cmd=0x0, in=0x8d1b258, out=0x8d1b808) at ../../../../src/modules/mal/mal_mapi.mx:479
17 0xb2ca671f in SERVERlistenThread (Sock=0x8d1a708) at ../../../../src/modules/mal/mal_mapi.mx:562
18 0xb731f170 in start_thread () from /lib/libpthread.so.0
19 0xb7086dfe in clone () from /lib/libc.so.6
In order to get in to this 'situation' I had an issue with a previous (full-)import because of a duplicate primary key. I expected this did a proper rollback. Then I tried this (partial-)import again, but removed the tables that broke my import.
## Comment 10603
Date: 2008-11-20 12:00:49 +0100
From: @mlkersten
The bug reported seems to be related to the parallel data loader
http://sourceforge.net/support/tracker.php?aid=2261241
The easiest way to confirm this is to load the database using
the setting --set gdk_nr_threads=1 which should not cause this
problem.
## Comment 10604
Date: 2008-11-20 16:17:21 +0100
From: @skinkie
I can reproduce this bug with --set gdk_nr_threads=1. Might be unrelated?
## Comment 10605
Date: 2008-11-20 16:41:59 +0100
From: @romulogoncalves
I did the insertion and I did get any crash except complains about foreign key violation because the ids values from the nodes.csv do not match the node values on node_tags.csv
I decided to make them equal and I used the latest stable version of M5-SQL with normal compilation and no changes related with number of threads....
I select the content of the tables:
% sys.node_tags, sys.node_tags, sys.node_tags table_name
% node, k, v name
% int, varchar, varchar type
% 6, 10, 15 length
[ 123350, "created_by", "YahooApplet 1.0" ]
[ 123351, "created_by", "YahooApplet 1.0" ]
[ 123352, "created_by", "YahooApplet 1.0" ]
% sys.nodes_legacy, sys.nodes_legacy, sys.nodes_legacy, sys.nodes_legacy, sys.nodes_legacy table_name
% id, long, lat, username, timestamp name
% int, int, int, varchar, timestamptz type
% 6, 9, 8, 6, 26 length
[ 123350, 608491291, 51499150, "raskas", 2007-05-31 19:44:09.000000+00:00 ]
[ 123351, 608610167, 51501482, "raskas", 2007-05-31 19:44:08.000000+00:00 ]
[ 123352, 608639476, 51508729, "raskas", 2007-05-31 19:44:09.000000+00:00 ]
I need more content if you do not mind ;)
PS: The same was done for M5-SQL current version....
## Comment 10606
Date: 2008-11-20 16:43:57 +0100
From: @romulogoncalves
"I did the insertion and I did get any crash except complains about foreign
key violation because the ids values from the nodes.csv do not match the
node values on node_tags.csv"
I did not get any crash.... Sorry I forgot the "not"
## Comment 10607
Date: 2009-02-11 21:05:41 +0100
From: @njnes
fixed. We now update keys. This prevents unaligned bats.
## Comment 10608
Date: 2009-02-16 10:47:35 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test for this one.
## Comment 10609
Date: 2009-02-16 22:20:31 +0100
From: @njnes
tested by osm/Tests/delete_alter_bug.sql
## Comment 10610
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2316185 at http://sourceforge.net/support/tracker.php?aid=2316185
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.
| Data corruption bug after copy into | https://api.github.com/repos/MonetDB/MonetDB/issues/1882/comments | 0 | 2020-11-30T10:05:51Z | 2024-06-27T11:33:33Z | https://github.com/MonetDB/MonetDB/issues/1882 | 753,337,990 | 1,882 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-17 04:00:07 +0100
From: @grobian
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-12-28 11:57:38 +0100
## Comment 10598
Date: 2008-11-17 16:00:07 +0100
From: @grobian
Starting a database that has no vaultkey using the monetdb utility will crash merovingian.
### Steps to reproduce:
1. % mserver5 --dbname=crashtest1
2. % merovingian
3. % monetdb start crashtest1
monetdb will return something like:
starting database 'crashtest1'... FAILED:
starting crashtest1 failed: cannot start database 'crashtest1': no .vaultkey found (did you create the database with `monetdb create crashtest1`?)
and merovingian will crash in the background.
## Comment 10599
Date: 2008-11-17 16:01:08 +0100
From: @grobian
The issue has been fixed in CVS.
## Comment 10600
Date: 2008-12-28 23:57:38 +0100
From: @grobian
Nov2008 bugfix release 1 includes this fix.
## Comment 10601
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2305746 at http://sourceforge.net/support/tracker.php?aid=2305746
| merovingian crashes when starting a vaultkeyless database | https://api.github.com/repos/MonetDB/MonetDB/issues/1881/comments | 0 | 2020-11-30T10:05:48Z | 2024-06-27T11:33:32Z | https://github.com/MonetDB/MonetDB/issues/1881 | 753,337,958 | 1,881 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-13 05:18:35 +0100
From: @yzchang
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-11-14 03:04:18 +0100
## Comment 10594
Date: 2008-11-13 17:18:35 +0100
From: @yzchang
In the current stable version, Nov2008.
Happens with both Algebra and MPS frontend.
If 32bits OIDs are used on a 64-bit architecture, following, following-sibling and preceding steps with an empty result will crash Mserver (this causes some XRPC tests to fail on "Fedora8 G.64.32.d.1." and "Fedora8 I.64.32.d.1").
Queries used:
<a/>/following::*
<a/>/following-sibling::*
<a/>/preceding::*
Errors received:
MonetDB>[New Thread 1115703632 (LWP 30455)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1115703632 (LWP 30455)]
0x00002aaab9e3e4a0 in PFll_following_sibling (result=0x427f93c0,
iter_bat=0x11f7788, ctx_bat=0x11fd448, pre_size=0x1456e78,
pre_level=0x129d818, pre_kind=0x145b0a8, _kind_test=0x427f9420 "\200")
at /ufs/zhang/monet/stable/pathfinder/runtime/ll_sibling.mx:505
505 oid lst_item = *(oid*)Tloc(res, BUNlast(res) - 1);
MonetDB>[New Thread 1115703632 (LWP 30587)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1115703632 (LWP 30587)]
0x00002aaab9e37506 in PFll_preceding (result=0x427f93c0, iter_bat=0x11f8308,
ctx_bat=0x14c5c18, doc_pre=0x1407d48, pre_size=0x1290848,
pre_kind=0x11f5f28, _kind_test=0x427f9420 "\200")
at /ufs/zhang/monet/stable/pathfinder/runtime/ll_prec_foll.mx:480
480 oid lst_item = *(oid*)Tloc(res, BUNlast(res) - 1);
Assigned to Stefan, since he seems the main author of these files. Please correct it, if this is not the case.
Kind regards,
Jennie
## Comment 10595
Date: 2008-11-13 23:15:37 +0100
From: @drstmane
Indeed, trying to read the last value from an empty BAT does result in a segfault ...
I attach a patch that fixes the bug --- I'll check it in, once we have a release (which requires that we all help in testing the release candidates that Sjoerd has built and made available for CWI-internal testing) and Sjoerd re-opens the release branches for bug-fix check-ins.
Stefan
File Added: fix-2277120.diff
## Comment 10596
Date: 2008-11-14 15:04:18 +0100
From: @drstmane
Fix is checked in to the Nov2008 branch.
Test has been added in pathfinder/tests/BugTracker/Tests/empty_step_result.SF-2277120.*
Closing.
## Comment 10597
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2277120 at http://sourceforge.net/support/tracker.php?aid=2277120
| XQ: following(-sibling)/preceding cause Mserver to crash | https://api.github.com/repos/MonetDB/MonetDB/issues/1880/comments | 0 | 2020-11-30T10:05:45Z | 2024-06-27T11:33:31Z | https://github.com/MonetDB/MonetDB/issues/1880 | 753,337,924 | 1,880 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-13 02:48:18 +0100
From: Hans <<hans_0_>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-17 10:06:49 +0100
## Comment 10587
Date: 2008-11-13 14:48:18 +0100
From: Hans <<hans_0_>>
This error was raised with the following xquery:
let $indexdoc := <XIRAF>
<link xid="127403" nid="2070022"><properties/></link>
<link xid="127431" nid="2070238"><properties/></link>
<file xid="146327" nid="2367886"><properties><name>name1</name></properties></file>
<folder xid="148892" nid="2408034"><properties><name>name2</name></properties></folder>
</XIRAF>
let $notesdoc := (<root><notes>
<objectnote unixtime="1222247507" user="user1" xid="146327">On 24 Sep 2008 09:11:47 GMT user1 wrote: Interessant </objectnote>
<objectnote unixtime="1216997181" user="user2" xid="148892">On 25 Jul 2008 16:46:21 GMT user2 wrote: folder name sounds suspicious</objectnote>
<objectnote unixtime="1216652532" user="user2" xid="127403">On 21 Jul 2008 17:02:12 GMT user2 wrote: een hyves account.. </objectnote>
<objectnote unixtime="1216652365" user="user2" xid="127431">On 21 Jul 2008 16:59:25 GMT user2 wrote: Datum van zoekopdracht: 3 Jun 2008 16:10:42 GMT</objectnote>
<objectnote unixtime="1216652301" user="user2" xid="127431">On 21 Jul 2008 16:58:21 GMT user2 wrote: hmmm, </objectnote>
</notes></root>)
let $result := (let $input := ($indexdoc//*[properties])
let $notedxids := distinct-values($notesdoc/notes/objectnote/@xid)
let $notedobjectsresult := $input intersect
(for $notedxid in $notedxids
return $input[@xid=$notedxid])
for $raw in $notedobjectsresult
return $raw
)
let $subresult := subsequence($result, 1, 1000)
let $nobj := count($subresult)
let $out := (
for $i in $subresult
let $note := ($notesdoc/notes/objectnote[@xid=$i/@xid])[1]
return element { name($i) } {
attribute nid { string(exactly-one(pf:nid(exactly-one($i)))) },
$i/@xid,
$i/properties/(name)
,$note
})
return element result {
element matches { count($result) },
element results { $out }
}
<>
Raises the following error report:
MAPI = monetdb@hostname:51240
QUERY = let $indexdoc := <XIRAF>
ERROR = !ERROR: merged_union: tail of first BAT/column of table 3 must be sorted.
!ERROR: CMDmulti_merged_union: operation failed.
Whereas the following xquery:
let $indexdoc := <XIRAF>
<link xid="127403" nid="2070022"><properties/></link>
<link xid="127431" nid="2070238"><properties/></link>
<file xid="146327" nid="2367886"><properties><name>name1</name></properties></file>
<folder xid="148892" nid="2408034"><properties><name>name2</name></properties></folder>
</XIRAF>
let $notesdoc := (<root><notes>
<objectnote unixtime="1222247507" user="user1" xid="146327">On 24 Sep 2008 09:11:47 GMT user1 wrote: Interessant </objectnote>
<objectnote unixtime="1216997181" user="user2" xid="148892">On 25 Jul 2008 16:46:21 GMT user2 wrote: folder name sounds suspicious</objectnote>
<objectnote unixtime="1216652532" user="user2" xid="127403">On 21 Jul 2008 17:02:12 GMT user2 wrote: een hyves account.. </objectnote>
<objectnote unixtime="1216652365" user="user2" xid="127431">On 21 Jul 2008 16:59:25 GMT user2 wrote: Datum van zoekopdracht: 3 Jun 2008 16:10:42 GMT</objectnote>
<objectnote unixtime="1216652301" user="user2" xid="127431">On 21 Jul 2008 16:58:21 GMT user2 wrote: hmmm, </objectnote>
</notes></root>)
let $result := (let $input := ($indexdoc//*[properties])
let $notedxids := distinct-values($notesdoc/notes/objectnote/@xid)
let $notedobjectsresult := $input intersect
(for $notedxid in $notedxids
return $input[@xid=$notedxid])
for $raw in $notedobjectsresult
return $raw
)
let $subresult := subsequence($result, 1, 1000)
let $nobj := count($subresult)
let $out := (
for $i in $subresult
let $note := ($notesdoc/notes/objectnote[@xid=$i/@xid])[1]
return element { name($i) } {
attribute nid { string(exactly-one(pf:nid(exactly-one($i)))) },
$i/@xid,
$i/properties/(name)
,element objectnote {$note/@*, $note/*, $note/text()}
})
return element result {
element matches { count($result) },
element results { $out }
}
<>
Returns:
<result><matches>4</matches>
<results>
<link xid="127403" nid="3"><objectnote xid="127403" user="user2" unixtime="1216652532">On 21 Jul 2008 17:02:12 GMT user2 wrote: een hyves account.. </objectnote></link>
<link xid="127431" nid="5"><objectnote xid="127431" user="user2" unixtime="1216652365">On 21 Jul 2008 16:59:25 GMT user2 wrote: Datum van zoekopdracht: 3 Jun 2008 16:10:42 GMT</objectnote></link>
<file xid="146327" nid="7"><name>name1</name><objectnote xid="146327" user="user1" unixtime="1222247507">On 24 Sep 2008 09:11:47 GMT user1 wrote: Interessant </objectnote></file>
<folder xid="148892" nid="11"><name>name2</name><objectnote xid="148892" user="user2" unixtime="1216997181">On 25 Jul 2008 16:46:21 GMT user2 wrote: folder name sounds suspicious</objectnote></folder>
</results></result>
The only difference in the xquery is in line 31:
,$note
is replaced by:
,element objectnote {$note/@*, $note/*, $note/text()}
I used a compiled version of the MonetDB-Aug2008-SuperBall.tar.bz2 on an Ubuntu 8.04 Linux system.
Regards,
Hans van Rijswijk
Netherlands Forensic Institute
The Hague, Netherlands.
## Comment 10588
Date: 2008-11-13 17:36:42 +0100
From: @drstmane
Hans,
thanks for the report.
With the latest CVS version for the new Nov2008 release branches (the version that will soon become the new Nov2008 release of MonetDB), the query works fine for me, yielding
<result><matches>4</matches><results><link xid="127403" nid="3"/><link xid="127431" nid="5"/><file xid="146327" nid="7"><name>name1</name><objectnote xid="146327" user="user1" unixtime="1222247507">On 24 Sep 2008
09:11:47 GMT user1 wrote: Interessant </objectnote></file><folder xid="148892" nid="11"><name>name2</name></folder></results></result>
Hence, I assume the problem has been fixed (or "eliminated") in CVS since the Aug2008 release and will be solved for you as soon as the upcoming Nov2008 will be available and you will have upgraded to it.
For now, you could try whether the problem is "merely" a property propagtion problem by running Mserver with property checking endabled, i.e.,
`Mserver --debug=10 ...`.
In case you do so, please report your finding here.
Stefan
## Comment 10589
Date: 2008-11-14 08:13:49 +0100
From: Hans <<hans_0_>>
Stefan,
The query result you described in your reply Date: 2008-11-13 16:36 is not complete.
Please compare the my query result to yours and you will see three objectnote nodes are missing.
So, in my opinion the problem has not been fixed.
Regards,
Hans
## Comment 10590
Date: 2008-11-14 09:39:51 +0100
From: Jan Rittinger <<jan.rittinger>>
Hi Hans,
after simplifying your query to
let $notesdoc := <root>
<notes>
<objectnote xid="3">a</objectnote>
<objectnote xid="1">b</objectnote>
<objectnote xid="1">c</objectnote>
</notes>
</root>
for $i in (<link xid="3"></link>, <link xid="1"></link>)
let $note := ($notesdoc/notes/objectnote[@xid=$i/@xid])[1]
return element { name($i) } { $i/@xid, $note }
I detected and fixed two bugs:
1.) In some merged_union settings MonetDB is not able to infer the correct ordering (and we have to help it by triggering order checking manually).
2.) In a scenare were a positional predicate sits on top of a thetajoin, the positional predicate was incorrectly pushed into one thetajoin operand.
Attached you find a diff that fixes both problems in pf 0.25 -- the fix however should also be applicable to the older June release.
(As soon as the release branch is open again -- I will check in the fixes.)
File Added: http://sourceforge.net/support/tracker.php?aid=2276427.diff
## Comment 10591
Date: 2008-11-15 22:30:22 +0100
From: Jan Rittinger <<jan.rittinger>>
Fix committed and test added.
## Comment 10592
Date: 2008-11-18 12:04:24 +0100
From: @drstmane
Test is available in
pathfinder/tests/BugTracker/Tests/multi_merged_union.SF-2276427.*
## Comment 10593
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2276427 at http://sourceforge.net/support/tracker.php?aid=2276427
| CMDmulti_merged_union: operation failed | https://api.github.com/repos/MonetDB/MonetDB/issues/1879/comments | 0 | 2020-11-30T10:05:42Z | 2024-06-27T11:33:30Z | https://github.com/MonetDB/MonetDB/issues/1879 | 753,337,876 | 1,879 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-10 01:51:45 +0100
From: Floris Ouwendijk <<floris233>>
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-04-07 03:43:05 +0200
## Comment 10584
Date: 2008-11-10 13:51:45 +0100
From: Floris Ouwendijk <<floris233>>
I'm working with the nightly build from the stable branch, taken on 2008-10-16 (http://monetdb.cwi.nl/testing/projects/monetdb/Stable/.DailyBuilds./20081016/)
While trying to reproduce a 'BBPdecref: 1000018301_nid_rid does not have pointer fixes.' problem, we pushed a lot of data through the client. After it has produced approx. 9GB of output, mclient terminates. After that mclient crashes occur more frequently.
Since the testdata is rather large, it will be sent to the Monet team separately.
## Comment 10585
Date: 2009-04-07 15:42:55 +0200
From: @peterboncz
This problem has not re-occurred, hence closing.
## Comment 10586
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2255453 at http://sourceforge.net/support/tracker.php?aid=2255453
The original assignee of this bug does not have
an account here. Reassigning to the default assignee
for the component, bugs-common@monetdb.org.
Previous assignee was nobody@users.sourceforge.net.
| mclient terminates connection unexpectedly | https://api.github.com/repos/MonetDB/MonetDB/issues/1878/comments | 0 | 2020-11-30T10:05:39Z | 2024-06-27T11:33:29Z | https://github.com/MonetDB/MonetDB/issues/1878 | 753,337,829 | 1,878 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-10 10:30:21 +0100
From: olivia <<opurvis>>
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:14:39 +0100
## Comment 10579
Date: 2008-11-10 10:30:21 +0100
From: olivia <<opurvis>>
When updating a table with values from another table, the update doesn't work properly.
How to reproduce:
create table table1 (col1 int,col2 int);
create table table2 (col1 int,col2 int);
insert into table1 (col1,col2) values (1,10),(2,20),(3,30);
insert into table2 (col1,col2) values (1,100),(2,200);
sql>select * from table1;
+------+-----+
| col1 |col2 |
+======+=====+
| 1 | 10 |
| 2 | 20 |
| 3 | 30 |
+------+-----+
sql>select * from table2;
+------+-----+
| col1 |col2 |
+======+=====+
| 1 | 100 |
| 2 | 200 |
+------+-----+
update table1 set col2=(select table2.col2 from table2 where table2.col1=table1.col1) where exists (select * from table2 where table1.col1=table2.col1);
sql>select * from table1;
+------+-----+
| col1 |col2 |
+======+=====+
| 1 | 100 |
| 2 | 200 |
| 3 |null |
+------+-----+
The desired result should should be:
sql>select * from table1;
+------+-----+
| col1 |col2 |
+======+=====+
| 1 | 100 |
| 2 | 200 |
| 3 | 30 |
+------+-----+
Only two rows should be affected as demonstrated by a similar select:
sql>select * from table1 where exists (select * from table2 where table1.col1=table2.col1);
+------+-----+
| col1 |col2 |
+======+=====+
| 1 | 10 |
| 2 | 20 |
+------+-----+
## Comment 10580
Date: 2008-11-10 11:37:02 +0100
From: @sjoerdmullender
Test added: src/test/BugTracker-2008 update_error.SF-2254506.
Could this be related to [ 2080207 ] The sub SELECT can't identify the outer table?
## Comment 10581
Date: 2008-12-01 15:59:14 +0100
From: @romulogoncalves
This bug is fixed in the current branch of M5-SQL using or not the algebra
version.
It will not be closed because it is not fixed in the stable branch...
What happen to the propagation? Or was the fix only checked in on the
current branch?
## Comment 10582
Date: 2009-02-09 15:14:39 +0100
From: @romulogoncalves
The bug is fixed as well in the stable so it can be closed.
## Comment 10583
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2254506 at http://sourceforge.net/support/tracker.php?aid=2254506
| Multi-table update produces incorrect results | https://api.github.com/repos/MonetDB/MonetDB/issues/1877/comments | 0 | 2020-11-30T10:05:36Z | 2024-06-27T11:33:28Z | https://github.com/MonetDB/MonetDB/issues/1877 | 753,337,783 | 1,877 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-07 11:23:41 +0100
From: Lucas Serpa Silva <<profetas>>
To: @njnes
Version: -- development
Last updated: 2008-12-01 03:55:49 +0100
## Comment 10573
Date: 2008-11-07 11:23:41 +0100
From: Lucas Serpa Silva <<profetas>>
With the following table:
===================================================
CREATE TABLE "adt"."adt_scene_witness" (
"scene_id" int NOT NULL,
"witness_name" varchar(260) NOT NULL,
"relation" CHARACTER LARGE OBJECT,
"reliability" CHARACTER LARGE OBJECT,
"state" CHARACTER LARGE OBJECT,
CONSTRAINT "adt_scene_witness_scene_id_witness_name_pkey" PRIMARY KEY
("scene_id", "witness_name"),
CONSTRAINT "adt_scene_witness_scene_id_fkey" FOREIGN KEY ("scene_id")
REFERENCES "adt_scene" ("id") ON DELETE CASCADE ON UPDATE CASCADE,
CONSTRAINT "adt_scene_witness_witness_name_fkey" FOREIGN KEY
("witness_name") REFERENCES "adt_witness" ("name") ON DELETE CASCADE
ON UPDATE CASCADE
);
==========================================
The following query will crash the DBMS Server
insert into adt_scene_witness values( (select v.scene_id , i.name from adt_victim v,adt_witness i where v.name like '%Mary Ann Walker%' and i.name like '%Patrick Mulshaw%'),'a','b','c','d');
Result
================================================
MAPI = adt@localhost:50000
ACTION= read_line
QUERY = insert into adt_scene_witness values( (select v.scene_id ,
i.name from adt_victim v,adt_witness i where v.name like '%Mary Ann
Walker%' and i.name like '%Patrick Mulshaw%'),'a','b','c','d');
ERROR = Connection terminated
## Comment 10574
Date: 2008-11-07 11:53:12 +0100
From: @romulogoncalves
It is sql and not MonetDB5 problem....
## Comment 10575
Date: 2008-11-17 18:08:41 +0100
From: @romulogoncalves
The bug can be represented by the following test:
create table t1 (id int NOT NULL);
insert into t1 values ((select id, name from tables));
drop table t1;
The problem is the sub select. It selects 2 columns and in the insertion I am only inserting one attribute value... ;)
## Comment 10576
Date: 2008-11-17 21:22:43 +0100
From: @romulogoncalves
Test added at:
sql/src/test/BugTracker-2008/Tests/sql_command_kills_db.SF-2233677.sql
Once again the name of the bug does not describe the problem. I decided to keep it like that just to simplify the identification of the bug report...
## Comment 10577
Date: 2008-12-01 15:55:49 +0100
From: @romulogoncalves
Bug fixed in all branches....
The fix was checked in:
[Monetdb-sql-checkins] sql/src/server sql_select.mx, Nov2008, 1.250, 1.250.2.1
Modified Files:
Tag: Nov2008
sql_select.mx
Log Message:
make sure we only interpret correlated results as such (ie not simple multi
column results)
Solves sql_command_kills_db.SF-2233677
## Comment 10578
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2233677 at http://sourceforge.net/support/tracker.php?aid=2233677
| SQL Command kills DB | https://api.github.com/repos/MonetDB/MonetDB/issues/1876/comments | 0 | 2020-11-30T10:05:32Z | 2024-06-27T11:33:27Z | https://github.com/MonetDB/MonetDB/issues/1876 | 753,337,729 | 1,876 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-07 10:53:48 +0100
From: Thomas Neumann <<tneumann>>
To: @njnes
Version: -- development
Last updated: 2009-01-20 05:14:18 +0100
## Comment 10566
Date: 2008-11-07 10:53:48 +0100
From: Thomas Neumann <<tneumann>>
Both the mclient client and the monetdb server do not seem to like '\0' (i.e., the ASCII character 0) as part of their input.
The following command causes the client the exit when run with
mclient -l sql
create table strings(id int not null primary key, value varchar(16400) not null);
copy 3 records into "strings" from stdin using delimiters '\t';
1 "some string"
2 "\0"
3 "some other string"
(Note that the "\0" must contain the character 0, not the escape sequence!)
In the context of a larger input statement the server crashed, too.
## Comment 10567
Date: 2008-11-07 11:12:38 +0100
From: @sjoerdmullender
I have already found two places that can't cope with embedded NULs.
In mapi_query_part(Mapi.mx) there is a strncpy to copy the query to a buffer. This stops at the NUL. In this case we even have the length of the query (i.e. also the bit beyond the NUL), but that part is blissfully ignored.
In TABLETload_bulk(tablet.mx) there is a search for the line terminator to see whether more data needs to be loaded. This is done using strstr which stops at the NUL byte.
## Comment 10568
Date: 2008-11-08 09:36:46 +0100
From: @mlkersten
The limitation on the buffer size in mapi_query_part
has been dropped.
## Comment 10569
Date: 2008-11-08 17:22:03 +0100
From: @sjoerdmullender
I interpreted the code in Mapi.mx incorrectly (the strncpy that I mentioned is actually not relevant), but your "fix" is not a fix at all since you still use strncpy. That function stops at the first NUL byte, and since your "fix" still uses strncpy, the copy still stops there.
However, this is totally irrelevant to the problem, since it is not the copied string which is sent to the server, it is the original string, or rather buffer. And that is sent using a count so the NUL byte and anything that follows that is also sent to the server. If you read the comment (that you also changed in the process), you see that the copy is used for error messages only. So there is actually not a problem in mclient.
This last remark is, however, only true if mclient reads from a file which was passed on the command line as command line argument. In that case (and if you use \< in an interactive mclient), the function doFile is used which uses fread to read from the file, and fread works fine with NUL bytes. In the interactive case however, the function doFileByLine is used which uses either the readline library or fgets, both of which do not handle embedded NUL bytes. So in that case the NUL byte will never be sent to the server.
## Comment 10570
Date: 2008-11-17 18:03:19 +0100
From: @romulogoncalves
How can I repeat this bug?
In mclient I get:
sql>copy 3 records into "strings" from stdin using delimiters '\t';
more>"romulo""\0""romulo"
!SQLException:sql:missing sep line 0 field 0
!SQLException:importTable:failed to import table
0 tuples
sql>
(Between the strings I pressed tab (\t))
in the mserver I do:
>copy 3 records into "strings" from stdin using delimiters '\t';
"romulo" "\0" "romulo"
And then there is no way to get the prompt back.
It is my first time doing copy from stdin. I use the latest version of stable branch.
## Comment 10571
Date: 2009-01-20 17:14:18 +0100
From: @sjoerdmullender
I fixed the problem by having mclient check for NULL bytes in the input, as long as mclient gets a file to process (either command line or \< construct). If it finds a NULL byte, it will print an error message to the effect and exit. Since mclient does not have a notion of line numbers, it can't give that information, but at least you would know what to look for.
I also added a test in sql: src/test/BugTracker-2008 insert-null-byte.SF-2233581.
## Comment 10572
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2233581 at http://sourceforge.net/support/tracker.php?aid=2233581
| MonetDB does not like '\0' in its input | https://api.github.com/repos/MonetDB/MonetDB/issues/1875/comments | 0 | 2020-11-30T10:05:29Z | 2024-06-27T11:33:26Z | https://github.com/MonetDB/MonetDB/issues/1875 | 753,337,682 | 1,875 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-07 07:35:38 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-11-09 03:50:41 +0100
## Comment 10563
Date: 2008-11-07 07:35:38 +0100
From: @drstmane
M5 test src/modules/mal/Tests/cluster00.mal fails on MacOS X (Darwin) & Solaris (SunOS); see, e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Darwin9.5.0/src_modules_mal/cluster00.out.00.html
## Comment 10564
Date: 2008-11-10 10:48:11 +0100
From: @drstmane
Indeed appears to work, now --- guess some of Martin's recent changes fixed the problem.
## Comment 10565
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2232940 at http://sourceforge.net/support/tracker.php?aid=2232940
| M5 test cluster00.mal fails on MacOS X & Solaris | https://api.github.com/repos/MonetDB/MonetDB/issues/1874/comments | 0 | 2020-11-30T10:05:26Z | 2024-06-27T11:33:25Z | https://github.com/MonetDB/MonetDB/issues/1874 | 753,337,629 | 1,874 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-07 07:29:18 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-11-07 08:00:52 +0100
## Comment 10560
Date: 2008-11-07 07:29:18 +0100
From: @drstmane
From
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.Int.32.32.d.1-Windows5.1..2008.11.07_00-09-02/test10.out.htmle1
:
Mtest.py: ERROR: ' mserver5 "--config=g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\conf\monetdb5.conf" --debug=10 --set gdk_nr_threads=1 --set "monet_mod_path=g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\compiler\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\compiler;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\optimizer\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\optimizer;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\scheduler\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\scheduler;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\atoms\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\atoms;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\kernel\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\kernel;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\mal\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\mal;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\mal\crackers\.libs;g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\src\modules\mal\crackers" --set "gdk_dbfarm=g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\dbfarm" --set "sql_logdir=g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\sql_logs" --set "xquery_logdir=g:\monet\monet.Int.32.32.d.1.16776\MonetDB5\NT\xquery_logs" --set mapi_open=true --set xrpc_open=true --set mapi_port=37233 --set xrpc_port=48785 --set monet_prompt= --trace --dbname=mTests` failed:
MonetDB server v5.8.0, based on kernel v1.26.0
Serving database 'mTests', using 1 thread
Compiled for i686-pc-win32/32bit with 32bit 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
!MALException:MAL.getAddress:address of 'profiler.CMDgetMemory' not found
## Comment 10561
Date: 2008-11-07 08:00:52 +0100
From: @mlkersten
fixed by addition of the external definitions
## Comment 10562
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2232908 at http://sourceforge.net/support/tracker.php?aid=2232908
| M5 fails to start/work on Windows | https://api.github.com/repos/MonetDB/MonetDB/issues/1873/comments | 0 | 2020-11-30T10:05:22Z | 2024-06-27T11:33:24Z | https://github.com/MonetDB/MonetDB/issues/1873 | 753,337,582 | 1,873 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-06 04:13:54 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-02-09 02:59:05 +0100
## Comment 10554
Date: 2008-11-06 16:13:54 +0100
From: @skinkie
In the category; error at layer 8.
CREATE TABLE "sys"."bigramlex" (
"subtotal" int,
"one" varchar(255) NOT NULL,
"two" varchar(255) NOT NULL,
CONSTRAINT "bigramlex_one_two_pkey" PRIMARY KEY ("one", "two")
);
insert into bigramlex (subtotal, one, two) values (1, 'hello', 'word');
select count(*) from bigramlex order by subtotal limit 10;
The query is plain wrong, that is clear. But it also crashes mserver5.
(gdb) bt
0 0x01d301d0 in ?? ()
1 0x0f96e3d0 in ATOMlen (t=255, src=0x10c88c28) at ../../../src/gdk/gdk_atoms.mx:960
2 0x0f96ebdc in ATOMdup (t=255, p=0x10c88c28) at ../../../src/gdk/gdk_atoms.mx:1064
3 0x0d69ea7c in res_col_create (tr=0x10603018, t=0x10cd30f0, tn=0x10ca9c30 "sys.bigramlex", name=0x10c85c70 "count_",
typename=0x10caa058 "wrd", digi1970-01-01 01:00:32 +0100, scale=0, mtype=255, val=0x10c88c28) at ../../../../src/storage/bat/res_table.mx:88
4 0x0d5fdcb8 in mvc_result_value (m=0x10c4b520, tn=0x10ca9c30 "sys.bigramlex", name=0x10c85c70 "count_",
typename=0x10caa058 "wrd", digi1970-01-01 01:00:32 +0100, scale=0, p=0x10c88c28, mtype=255)
at ../../../../src/backends/monet5/sql_result.mx:1166
5 0x0d5a2da4 in mvc_result_value_wrap (cntxt=0x10016398, mb=0x10c87258, stk=0x10c88a08, pci=0x10c887e0)
at ../../../../src/backends/monet5/sql.mx:1785
6 0x0ff2d234 in runMALsequence (cntxt=0x10016398, mb=0x10c87258, startpc=1, stoppc=0, stk=0x10c88a08, env=0x0,
pcicaller=0x0) at ../../../src/mal/mal_interpreter.mx:1635
7 0x0ff2bc8c in callMAL (cntxt=0x10016398, mb=0x10c87258, env=0x4ca6bbe8, argv=0x4ca6bb98, debug=0 '\0')
at ../../../src/mal/mal_interpreter.mx:423
8 0x0d5eb78c in SQLexecutePrepared (c=0x10016398, be=0x10c91b60, q=0x10cd1fa8)
at ../../../../src/backends/monet5/sql_scenario.mx:1203
9 0x0d5ebd94 in SQLengineIntern (c=0x10016398, be=0x10c91b60) at ../../../../src/backends/monet5/sql_scenario.mx:1314
10 0x0d5ec428 in SQLengine (c=0x10016398) at ../../../../src/backends/monet5/sql_scenario.mx:1432
11 0x0ff65910 in runPhase (c=0x10016398, phase=4) at ../../../src/mal/mal_scenario.mx:591
12 0x0ff65aec in runScenarioBody (c=0x10016398) at ../../../src/mal/mal_scenario.mx:631
13 0x0ff65cbc in runScenario (c=0x10016398) at ../../../src/mal/mal_scenario.mx:656
14 0x0ff29a90 in MSserveClient (dummy=0x10016398) at ../../../src/mal/mal_session.mx:462
15 0x0f07cb0c in start_thread () from /lib/libpthread.so.0
16 0x0ecc5b90 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
## Comment 10555
Date: 2008-11-17 17:51:26 +0100
From: @romulogoncalves
We can reduce the example to this simple one:
CREATE TABLE bigramlex (subtotal int);
select count(subtotal) from bigramlex order by subtotal;
drop TABLE bigramlex;
It only crashed in the algebra version and not in the normal version.
## Comment 10556
Date: 2008-11-17 21:18:29 +0100
From: @romulogoncalves
Test added at:
sql/src/test/BugTracker-2008/Tests/count_with_order_by_and_limit_crashes.SF-2229936.sql
The content of the test is the simple example and not the one used to open this bug...
## Comment 10557
Date: 2008-12-01 15:50:00 +0100
From: @romulogoncalves
This bug is fixed in the algebra version for the stable and current branch of M5-SQL.
I can't close the bug until it is fixed in the normal version as well.
To use the algebra version just call mclient with option "-G":
mclient -G
## Comment 10558
Date: 2009-02-09 14:59:04 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10559
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2229936 at http://sourceforge.net/support/tracker.php?aid=2229936
| [SQL] count(*) with order by and limit crashes | https://api.github.com/repos/MonetDB/MonetDB/issues/1872/comments | 0 | 2020-11-30T10:05:20Z | 2024-06-27T11:33:23Z | https://github.com/MonetDB/MonetDB/issues/1872 | 753,337,546 | 1,872 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-05 08:21:38 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-11-10 07:38:39 +0100
## Comment 10550
Date: 2008-11-05 08:21:38 +0100
From: @drstmane
Tests
MonetDB5/src/modules/mal/Tests/mserver00.mal
MonetDB5/src/modules/mal/Tests/remote02.mal
MonetDB5/src/modules/mal/Tests/remote04.mal
fail on some platforms with
!MALException:mapi.query:remote error: MALException: BBPdecref: monet_environment does not have logical references.
!MALException:remote.put: monet_environment does not have logical references.
cf. (e.g.):
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.64.d.1-RedHat4WS/src_modules_mal/mserver00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/Int.64.64.d.1-RedHat4WS/src_modules_mal/remote02.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.32.32.d.1-Debian4.0/src_modules_mal/remote04.out.00.html
## Comment 10551
Date: 2008-11-09 15:39:45 +0100
From: @mlkersten
Most likely spurious errors due to non-initialized.
## Comment 10552
Date: 2008-11-10 07:38:39 +0100
From: @mlkersten
Closing this one. The remote03 test still requires some further
design/study
## Comment 10553
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2224268 at http://sourceforge.net/support/tracker.php?aid=2224268
| M5: "monet_environment does not have logical references" | https://api.github.com/repos/MonetDB/MonetDB/issues/1871/comments | 0 | 2020-11-30T10:05:16Z | 2024-06-27T11:33:22Z | https://github.com/MonetDB/MonetDB/issues/1871 | 753,337,509 | 1,871 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-05 08:12:28 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-11-09 03:38:54 +0100
## Comment 10547
Date: 2008-11-05 08:12:28 +0100
From: @drstmane
Test MonetDB5/src/optimizer/Tests/remote00.py fails on all platforms:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora8/src_optimizer/remote00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora8/src_optimizer/remote00.err.00.html
## Comment 10548
Date: 2008-11-09 15:38:54 +0100
From: @mlkersten
Access to non-initialized stack elements caused this behavior.
Solved in the kernel.
## Comment 10549
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2224240 at http://sourceforge.net/support/tracker.php?aid=2224240
| M5 test src/optimizer/Tests/remote00.py fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1870/comments | 0 | 2020-11-30T10:05:13Z | 2024-06-27T11:33:21Z | https://github.com/MonetDB/MonetDB/issues/1870 | 753,337,469 | 1,870 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-05 08:08:07 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2008-12-08 03:54:31 +0100
## Comment 10544
Date: 2008-11-05 08:08:07 +0100
From: @drstmane
Most probabaly after / due to recent changes wrt. GDKerror & GDKwarning, test MonetDB4/tests/BugsViaSourgeforce/Tests/ID.914935 fails as follows:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB4/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugsViaSourgeforce/ID.914935.out.00.html
Please note that not only "!WARNING: " has been replaced by "", but also the newline at the end of the message has disappeared, makeling the next output line part of the warning/comment.
## Comment 10545
Date: 2008-12-08 15:54:30 +0100
From: @drstmane
New output has been approved by Sjoerd.
Closing.
## Comment 10546
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2224233 at http://sourceforge.net/support/tracker.php?aid=2224233
| M4 test ID.914935 fails after warning changes | https://api.github.com/repos/MonetDB/MonetDB/issues/1869/comments | 0 | 2020-11-30T10:05:10Z | 2024-06-27T11:33:20Z | https://github.com/MonetDB/MonetDB/issues/1869 | 753,337,427 | 1,869 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-05 07:35:29 +0100
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-11-05 07:58:36 +0100
## Comment 10541
Date: 2008-11-05 07:35:29 +0100
From: @drstmane
There is no stable test output for the cluster00 test. This makes the test
totally useless. Please provide the correct expected output.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora8/src_modules_mal/cluster00.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/MonetDB5/.mTests103/GNU.64.64.d.1-Fedora8/src_modules_mal/cluster00.err.00.html
## Comment 10542
Date: 2008-11-05 07:58:13 +0100
From: @mlkersten
Committed the missing files.
## Comment 10543
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2224134 at http://sourceforge.net/support/tracker.php?aid=2224134
| no test output for cluster00 test | https://api.github.com/repos/MonetDB/MonetDB/issues/1868/comments | 0 | 2020-11-30T10:05:06Z | 2024-06-27T11:33:19Z | https://github.com/MonetDB/MonetDB/issues/1868 | 753,337,366 | 1,868 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-11-03 04:08:46 +0100
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:00:15 +0100
## Comment 10535
Date: 2008-11-03 16:08:46 +0100
From: @skinkie
(not the latest cvs)
CREATE TABLE "sys"."testme" (
"id" int NOT NULL DEFAULT next value for "sys"."seq_4157",
"pos" varchar(8),
"word" varchar(32),
CONSTRAINT "testme_id_pkey" PRIMARY KEY ("id")
);
INSERT INTO testme (pos, word) VALUES ('hello', 'world');
SELECT (SELECT count(word) AS subtotal, pos FROM testme GROUP BY pos);
0x0d62544c in sql_value_exp (sql=0x10894e50, scp=0x108d8ab8, se=0x10931b88, grp=0x0, subset=0x0, f=3, ek={type = 0 '\0', card = 2 '\002', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:1709
1709 h = stmt_dup(s->h->t);
0 0x0d62544c in sql_value_exp (sql=0x10894e50, scp=0x108d8ab8, se=0x10931b88, grp=0x0, subset=0x0, f=3, ek={type = 0 '\0', card = 2 '\002', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:1709
1 0x0d629010 in _column_exp (sql=0x10894e50, scp=0x108d8ab8, column_e=0x10931c28, grp=0x0, subset=0x0, f=3) at ../../../src/server/sql_select.mx:2701
2 0x0d6292bc in sql_column_exp (sql=0x10894e50, scp=0x108d8ab8, column_e=0x10931c28, grp=0x0, subset=0x0, f=3) at ../../../src/server/sql_select.mx:2735
3 0x0d62d290 in sql_simple_select (sql=0x10894e50, scp=0x108d8ab8, sn=0x10931d08) at ../../../src/server/sql_select.mx:3791
4 0x0d61f6d8 in sql_subquery (sql=0x10894e50, scp=0x108d8ab8, sq=0x10931d08, ek={type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:234
5 0x0d61f9a0 in scope_subquery (sql=0x10894e50, scp=0x108d8ab8, sq=0x10931d08, ek={type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:279
6 0x0d62ef0c in selects (sql=0x10894e50, scp=0x0, s=0x10931d08) at ../../../src/server/sql_select.mx:4292
7 0x0d6325e0 in semantic (sql=0x10894e50, scp=0x0, s=0x10931d08) at ../../../src/server/sql_semantic.mx:1160
8 0x0d63287c in output_semantic (sql=0x10894e50, scp=0x0, s=0x10931d08) at ../../../src/server/sql_semantic.mx:1231
9 0x0d59f3c0 in sql_symbol2stmt (c=0x10894e50, sym=0x10931d08) at ../../../../src/backends/monet5/sql.mx:995
10 0x0d5eaddc in SQLparser (c=0x10016398) at ../../../../src/backends/monet5/sql_scenario.mx:1023
11 0x0ff65910 in runPhase (c=0x10016398, phase=1) at ../../../src/mal/mal_scenario.mx:591
12 0x0ff65a50 in runScenarioBody (c=0x10016398) at ../../../src/mal/mal_scenario.mx:622
13 0x0ff65cbc in runScenario (c=0x10016398) at ../../../src/mal/mal_scenario.mx:656
14 0x0ff29a90 in MSserveClient (dummy=0x10016398) at ../../../src/mal/mal_session.mx:462
15 0x0f07cb0c in start_thread () from /lib/libpthread.so.0
16 0x0ecc5b90 in clone () from /lib/libc.so.6
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
## Comment 10536
Date: 2008-11-17 17:34:58 +0100
From: @romulogoncalves
A simple example that covers all the problem:
select (select 1);
:)
## Comment 10537
Date: 2008-11-17 21:12:08 +0100
From: @romulogoncalves
Test added:
sql/src/test/BugTracker-2008/Tests/group_by_in_subquery_fails.SF-2219131.sql
It contain the simple example and not the one used to open this bug....
## Comment 10538
Date: 2008-12-01 15:49:24 +0100
From: @romulogoncalves
This bug is fixed in the algebra version for the stable and current branch of M5-SQL.
I can't close the bug until it is fixed in the normal version as well.
To use the algebra version just call mclient with option "-G":
mclient -G
## Comment 10539
Date: 2009-02-09 14:59:51 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10540
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2219131 at http://sourceforge.net/support/tracker.php?aid=2219131
| group by in subquery fails | https://api.github.com/repos/MonetDB/MonetDB/issues/1867/comments | 0 | 2020-11-30T10:05:03Z | 2024-06-27T11:33:18Z | https://github.com/MonetDB/MonetDB/issues/1867 | 753,337,331 | 1,867 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-31 11:19:28 +0100
From: Jan Rittinger <<jan.rittinger>>
To: Jens Teubner <<teubner>>
Version: 11.1.1 (Mar2011) [obsolete]
Last updated: 2011-04-28 16:38:56 +0200
## Comment 10528
Date: 2008-10-31 11:19:28 +0100
From: Jan Rittinger <<jan.rittinger>>
Hi Jens,
the following query fails due to incorrect typing
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.32.32.d.1-Darwin8.11.0/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.err.00.html
somehow PFty_disjoint (PFty_choice (PFty_xs_anyElement(), PFty_xs_anyElement()), PFty_xs_anyNode ()) returns true;
The problem arises in semantics/typecheck.brg:915
## Comment 10529
Date: 2008-10-31 11:24:12 +0100
From: Jan Rittinger <<jan.rittinger>>
hmpf -- I wasn't finished yet but hit enter with my focus outside the textbox.
Here comes the remainder of the bug report:
true == PFty_disjoint (PFty_choice (PFty_elem (PFqname (PFns_wild, "a"), PFty_xs_anyAttribute()), PFty_elem (PFqname (PFns_wild, "b"), PFty_xs_anyAttribute())), PFty_xs_anyNode())
false == PFty_disjoint (PFty_choice (PFty_elem (PFqname (PFns_wild, "a"), PFty_xs_anyType()), PFty_elem (PFqname (PFns_wild, "b"), PFty_xs_anyType())), PFty_xs_anyNode())
false == PFty_disjoint (PFty_choice (PFty_xs_anyElement(), PFty_xs_anyElement()), PFty_xs_anyNode ())
false == PFty_disjoint (PFty_xs_anyElement(), PFty_xs_anyNode ()))
only the first example (with a nested type being not xs:anyType) returns the incorrect result.
## Comment 10530
Date: 2009-02-16 11:17:01 +0100
From: Jan Rittinger <<jan.rittinger>>
see also:
http://sourceforge.net/tracker2/?func=detail&aid=1637867&group_id=56967&atid=482468
## Comment 10531
Date: 2009-03-15 11:27:18 +0100
From: @drstmane
updated URLs:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.err.00.html
## Comment 10532
Date: 2009-11-07 14:05:09 +0100
From: @drstmane
closing as all related test seem to work fine now/again:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.0-Fedora10/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.0-Fedora10/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.0-Fedora10/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.0-Fedora10/tests_BugTracker/seqcast_opt_int_to_numeric.SF-1637867.err.00.html
## Comment 10533
Date: 2009-11-15 16:11:23 +0100
From: Jan Rittinger <<jan.rittinger>>
The type disjointness is not fixed yet.
The following query e.g., still provides the incorrect result:
for $action in <x><a/><b/></x>/*
return typeswitch ($action)
case element(a) return "case matched"
default return $action
(The expected result is: case matched<b/>.)
The existing tests however all were triggered by a different call to type disjointness (for path steps) that I disabled some time ago.
## Comment 10534
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2211565 at http://sourceforge.net/support/tracker.php?aid=2211565
## Comment 15694
Date: 2011-03-28 17:37:06 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15763
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.
| PF: type disjointness incorrect | https://api.github.com/repos/MonetDB/MonetDB/issues/1866/comments | 0 | 2020-11-30T10:05:00Z | 2024-06-28T13:27:48Z | https://github.com/MonetDB/MonetDB/issues/1866 | 753,337,302 | 1,866 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-30 03:41:19 +0100
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2008-12-08 03:58:27 +0100
## Comment 10523
Date: 2008-10-30 15:41:19 +0100
From: @drstmane
Since Mon Oct 27, i.e., after changes made on Sat Oct 25 and/or Sun Oct 26 (due to compilation problems there are no testing results for Sun Oct 26), most GEOM test fail, i.e., produce different output than before.
See
http://monetdb.cwi.nl/testing/projects/monetdb/Current/geom/.mTests5103/index.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/geom/.mTestsG103/index.html
Since the main differences are in (expected) error messages, I suspect that they are related to Martin's error (-message) handling changes.
## Comment 10524
Date: 2008-11-09 21:17:34 +0100
From: @mlkersten
The GDKwarning in M5 has been removed already. Either it is a proper
error (GDKerror) being turned into an Exception, or it is
a debugging statement, which should be properly packed
in a ifdef _DEBUG_
## Comment 10525
Date: 2008-11-09 21:49:13 +0100
From: @mlkersten
The GDKwarning in M5 has been removed already. Either it is a proper
error (GDKerror) being turned into an Exception, or it is
a debugging statement, which should be properly packed
in a ifdef _DEBUG_
## Comment 10526
Date: 2008-12-08 15:58:27 +0100
From: @drstmane
New stable output has been approved by Sjoerd.
Closing.
## Comment 10527
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2209871 at http://sourceforge.net/support/tracker.php?aid=2209871
| most GEOM test fail after error handling changes | https://api.github.com/repos/MonetDB/MonetDB/issues/1865/comments | 0 | 2020-11-30T10:04:56Z | 2024-06-27T11:33:16Z | https://github.com/MonetDB/MonetDB/issues/1865 | 753,337,247 | 1,865 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-22 10:16:20 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-10-22 12:46:56 +0200
## Comment 10516
Date: 2008-10-22 10:16:20 +0200
From: @drstmane
After yesterdays late(st) changes (see below), mserver5 segfaults as soon as mclient -lsql tried to connect:
0x00002aaabef92a97 in create_col (tr=0x104ace8, c=0x104d3e8) at /ufs/manegold/_/scratch0/Monet/Testing/Current/source/sql/src/storage/bat/bat_storage.mx:531
531 int type = c->type.type->localtype;
(gdb) print c
$1 = (sql_column *) 0x104d3e8
(gdb) print *c
$2 = {base = {wtime = 0, rtime = 0, flag = 1, id = 1061, name = 0x104d458 "id"}, type = {type = 0x0, digits = 0, scale = 0, comp_type = 0x0}, colnr = 0, null = 1 '\001', def = 0x0, unique = 0 '\0', t = 0x104af98, data = 0x0}
(gdb) print c->type
$3 = {type = 0x0, digits = 0, scale = 0, comp_type = 0x0}
(see attached GDB log for details)
Before these changes, it did work fine:
===================================================================
2008/10/21 - mlkersten: MonetDB5/src/modules/mal/cluster.mx,1.4
MonetDB5/src/modules/mal/Tests/cluster00.mal,1.4
Make a guess about the number of (memory) buckets to use for clustering.
===================================================================
2008/10/21 - sjoerd: MonetDB/src/common/stream.mx,1.173
Added function to clear stream error so that we can continue after an
error.
This is needed for mclient.
===================================================================
2008/10/21 - sjoerd: clients/src/mapiclient/MapiClient.mx,1.124
Report write error and clear the stream so that we can continue.
Unfortunately the reason for the write error is lost, so the best we
can do now is to report that there was an error.
Convert command line query according to specified or implied encoding.
===================================================================
2008/10/22 - mlkersten: sql/src/common/sql_keyword.mx,1.13
sql/src/common/sql_string.mx,1.19 sql/src/server/rel_select.mx,1.89
sql/src/server/sql_select.mx,1.249 sql/src/server/sql_semantic.mx,1.189
Added toUpper and avoided name clash. Added all upper case versions
to the symbol table. This accomodates most use cases, if we fail
to find then we re-cast. Savings around 1% on micro-test of Fabian.
===================================================================
## Comment 10517
Date: 2008-10-22 10:18:46 +0200
From: @drstmane
overruling automatic assignment, since Niels is/was not actively involved (Martin and Sjoerd are/were);
Niels "may" of course still have a look at it ... ;-)
## Comment 10518
Date: 2008-10-22 12:01:35 +0200
From: @sjoerdmullender
I see a discrepancy in the code:
in sql/src/common/sql_types.mx the type system is initialized using capitalized names;
in sql/src/storage/store.mx columns are created using lower case type names.
The function that is called to do the comparison (sql_find_subtype) does not do case mapping so doesn't find the type when called from bootstrap_create_column, called from store_init.
## Comment 10519
Date: 2008-10-22 12:24:57 +0200
From: @mlkersten
The find_keyword casted everything to lower before searching.
This was done in place which creates a side-effect of a find.
The keyword_exist call is recasted.
Problem was not detected after a make;make install
over an existing database test run. Testing in progress.
## Comment 10520
Date: 2008-10-22 12:46:56 +0200
From: @mlkersten
Reverted part of the changes. Tests run as expected again.
Sorry for the inconvenience.
## Comment 10521
Date: 2008-10-22 13:19:56 +0200
From: @mlkersten
The changes made to sql_semantics remain, because
mkUpper had confusing semantics compared to mkLower
defined in common/sql_strings.
This has been rectified by keeping mkUpperCopy
and also mkUpper.
## Comment 10522
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2186337 at http://sourceforge.net/support/tracker.php?aid=2186337
| mserver5 segfaults on mclient -lsql connection | https://api.github.com/repos/MonetDB/MonetDB/issues/1864/comments | 0 | 2020-11-30T10:04:53Z | 2024-06-27T11:33:15Z | https://github.com/MonetDB/MonetDB/issues/1864 | 753,337,198 | 1,864 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-21 01:00:44 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:00:59 +0100
## Comment 10505
Date: 2008-10-21 01:00:44 +0200
From: @skinkie
sql>SELECT way WHERE k = 'bridge';
!SELECT: identifier 'k' unknown
0 tuples
sql>SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
mserver5: ../../../src/server/sql_select.mx:475: find_pivot: Assertion `subset->
type == st_ptable' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb1ff2b90 (LWP 1732)]
0xb80b0424 in __kernel_vsyscall ()
(gdb) bt
0 0xb80b0424 in __kernel_vsyscall ()
1 0xb7137670 in raise () from /lib/libc.so.6
2 0xb7138eb8 in abort () from /lib/libc.so.6
3 0xb713064e in __assert_fail () from /lib/libc.so.6
4 0xb25714db in find_pivot (subset=0x9008e40, t=0x90001c8)
at ../../../src/server/sql_select.mx:475
5 0xb2574e8d in sql_column_value (sql=0x8fb2080, scp=0x9008950,
se=0x8fb4340, grp=0x0, subset=0x9008e40, f=3)
at ../../../src/server/sql_select.mx:1571
6 0xb2575436 in sql_value_exp (sql=0x8fb2080, scp=0x9008950, se=0x8fb4340,
grp=0x0, subset=0x9008e40, f=3, ek=
{type = 0 '\0', card = 2 '\002', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:1665
7 0xb2578905 in _column_exp (sql=0x8fb2080, scp=0x9008950,
column_e=0x8fb43b0, grp=0x0, subset=0x9008e40, f=3)
at ../../../src/server/sql_select.mx:2701
8 0xb2578b1b in sql_column_exp (sql=0x8fb2080, scp=0x9008950,
column_e=0x8fb43b0, grp=0x0, subset=0x9008e40, f=3)
at ../../../src/server/sql_select.mx:2735
9 0xb257c64f in sql_simple_select (sql=0x8fb2080, scp=0x9008950,
sn=0x8fb4610) at ../../../src/server/sql_select.mx:3791
10 0xb257cbe8 in sql_select (sql=0x8fb2080, scp=0x9008950, sn=0x8fb4610, ek=
{type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:3907
11 0xb2570830 in sql_subquery (sql=0x8fb2080, scp=0x9008950, sq=0x8fb4610, ek=
{type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:236
12 0xb25709fd in scope_subquery (sql=0x8fb2080, scp=0x9008950, sq=0x8fb4610,
ek={type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:279
13 0xb257548d in sql_value_exp (sql=0x8fb2080, scp=0x8ffb1e0, se=0x8fb4610,
grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:1669
14 0xb257aeed in sql_logical_exp_ (sql=0x8fb2080, scp=0x8ffb1e0,
sc=0x8fb46e0, grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:3370
15 0xb257bde6 in sql_logical_exp (sql=0x8fb2080, scp=0x8ffb1e0, sc=0x8fb46e0,
grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:3628
16 0xb257cc4c in sql_select (sql=0x8fb2080, scp=0x8ffb1e0, sn=0x8fb4790, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:3910
17 0xb2570830 in sql_subquery (sql=0x8fb2080, scp=0x8ffb1e0, sq=0x8fb4790, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:236
18 0xb25709fd in scope_subquery (sql=0x8fb2080, scp=0x8ffb1e0, sq=0x8fb4790,
ek={type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:279
19 0xb257e327 in selects (sql=0x8fb2080, scp=0x0, s=0x8fb4790)
at ../../../src/server/sql_select.mx:4292
20 0xb2580d01 in semantic (sql=0x8fb2080, scp=0x0, s=0x8fb4790)
at ../../../src/server/sql_semantic.mx:1160
21 0xb2580f49 in output_semantic (sql=0x8fb2080, scp=0x0, s=0x8fb4790)
at ../../../src/server/sql_semantic.mx:1231
22 0xb250dfe9 in sql_symbol2stmt (c=0x8fb2080, sym=0x8fb4790)
at ../../../../src/backends/monet5/sql.mx:995
23 0xb2544844 in SQLparser (c=0x804d3f4)
at ../../../../src/backends/monet5/sql_scenario.mx:1023
24 0xb803e74d in runPhase (c=0x804d3f4, phase=1)
at ../../../src/mal/mal_scenario.mx:591
25 0xb803e845 in runScenarioBody (c=0x804d3f4)
at ../../../src/mal/mal_scenario.mx:622
26 0xb803ea43 in runScenario (c=0x804d3f4)
at ../../../src/mal/mal_scenario.mx:656
27 0xb80076b7 in MSserveClient (dummy=0x804d3f4)
at ../../../src/mal/mal_session.mx:462
28 0xb7470170 in start_thread () from /lib/libpthread.so.0
29 0xb71d8dfe in clone () from /lib/libc.so.6
## Comment 10506
Date: 2008-10-21 09:20:57 +0200
From: @drstmane
Works for me (with CVS HEAD of Tue Oct 21 09:19:22 CEST 2008):
sql>create table way_tags (way integer);
0 tuples
sql>SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
!SELECT: identifier 'k' unknown
0 tuples
## Comment 10507
Date: 2008-10-21 09:44:42 +0200
From: @mlkersten
Works for me... so there is more context involved
>SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
!SELECT: no such table 'way_tags'
>create table way_tags(way integer);
&3
>SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
!SELECT: identifier 'k' unknown
>
## Comment 10508
Date: 2008-10-21 16:11:46 +0200
From: @drstmane
(Yet another problem with an insufficiently specified bug report --- *please* give at least also the schema(s) of the table(s) that you use for your quer(y|ies) ... here is why this matters:)
The reported "problematic" query (with no FROM clause in the subquery) works "fine" (i.e., gives a proper error) in case the attribute that is used in the subquery does not exist in the given table:
sql>create table way_tags (way integer);
0 tuples
sql>SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
!SELECT: identifier 'k' unknown
0 tuples
sql>drop table way_tags;
0 tuples
However, in case the attribute does exist in the table, mserver5 aborts as reported:
mclient:
sql>create table way_tags (way integer, k string);
0 tuples
sql>SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
MAPI = monetdb@localhost:50000
ACTION= read_line
QUERY = SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
ERROR = Connection terminated
mserver5 (CVS HEAD of Tue Oct 21 15:55:53 CEST 2008):
$ mserver5 --dbinit='include sql;'
MonetDB server v5.7.0, based on kernel v1.25.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/manegold/_/scratch0/Monet/Testing/Current/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.25.0 loaded
>mserver5: /ufs/manegold/_/scratch0/Monet/Testing/Current/source/sql/src/server/sql_select.mx:475: find_pivot: Assertion `subset->type == st_ptable' failed.
Aborted
(No, I do not feel "personally offended" by incomplete/useless bug reports --- I would appreciate, though, if requests for more information about incomplete/useless bug reports would be answered properly, i.e., providing the requested information, rather than adding (various) non-polite comments
We (try to) take bug reports serious as well as stick to common standards of polite inter-human communication, and do appreciate if our users do so, too.)
## Comment 10509
Date: 2008-10-21 18:47:37 +0200
From: @skinkie
https://sourceforge.net/tracker2/?func=detail&aid=2134428&group_id=56967&atid=482468
Date: 2008-10-09 04:45
Contains the instructions to reproduce the table and all its nodes. You can ignore the fix in the dataset, in the mean time I have updated this already in the original data.
If all the bug reports are incomplete because the table structure was not known, I'm sorry for that. But I think you cannot expect a user (in a normal business critical data structure) to show all its source material. In my case this is different because the source material is publicly available.
## Comment 10510
Date: 2008-10-21 19:46:35 +0200
From: @drstmane
@skinkie:
Patient comes to doctor: "I hear voices, without seeing anybody. Please help me."
After weeks of all kind of physical and mental checks, the doctor does cannot find any problems. The patient is physically and mentally (as far as that can be checked) in perfect health. The doctor is close to giving up his job, but has one final question for the patient: "Could you please tell me when the symptoms occur?"
Patient: "Whenever I make phone calls." ...
This story, http://www.chiark.greenend.org.uk/~sgtatham/bugs.html, today's problems, and "common sense" should give you more than enough convincing examples and arguments, how important clear and complete bug reports as well as likewise communication are to be efficient and make sense ...
If not, I'm afraid, I'm not able to provide any more ...
## Comment 10511
Date: 2008-11-17 17:23:41 +0100
From: @romulogoncalves
SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
Niels,
Should the sub-query read from the table reference by the from clause in the outside SELECT?
## Comment 10512
Date: 2008-11-17 21:08:52 +0100
From: @romulogoncalves
Test added:
sql/src/test/BugTracker-2008/Tests/server_aborts_on_nested_query_without_from_in_subquery.SF-2183292.sql
## Comment 10513
Date: 2008-12-01 15:48:29 +0100
From: @romulogoncalves
This bug is fixed in the algebra version for the stable and current branch of M5-SQL.
I can't close the bug until it is fixed in the normal version as well.
To use the algebra version just call mclient with option "-G":
mclient -G
## Comment 10514
Date: 2009-02-09 15:00:59 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10515
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2183292 at http://sourceforge.net/support/tracker.php?aid=2183292
| SQL: server aborts on nested query without FROM in subquery | https://api.github.com/repos/MonetDB/MonetDB/issues/1863/comments | 0 | 2020-11-30T10:04:49Z | 2024-06-27T11:33:14Z | https://github.com/MonetDB/MonetDB/issues/1863 | 753,337,142 | 1,863 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-21 12:57:05 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-10-21 03:53:52 +0200
## Comment 10496
Date: 2008-10-21 00:57:05 +0200
From: @skinkie
I find many errors that I reported here were based on my incompetence to remember field names, and the use invalid fieldnames. Would it be possible to warn a user if a comparison is done on a field that does not exist in the table, nor is a variable?
Example, I type:
SELECT * FROM way_tags WHERE waysid = 100;
In this table the field waysid does not exist, and the query will also return 0 tuples.
If we advance to a query where this wrong field is used in a comparison with another field that doesn't exist hence:
select * from way_tags as w1, way_tags as w2 where w1.k = 'bridge' and w1.wayid = w2.wayid;
Unexpected behavior occurs.
Now I don't know if this is a bug, or actually a valid principle according to SQL. But if two features on their own return 0 tuples simple because the feature doesn't exist, shouldn't the query at least directly return 0, warn (or better abort!) if such thing is located. I plea guilty, fully, but there are users that like my don't have the precision of working with MonetDB and are rather 'verstrooid'.
## Comment 10497
Date: 2008-10-21 13:48:26 +0200
From: @drstmane
works for me (CVS head of Tue Oct 21 09:19:22 CEST 2008):
sql>create table way_tags (way integer);
0 tuples
sql>SELECT * FROM way_tags WHERE waysid = 100;
!SELECT: identifier 'waysid' unknown
0 tuples
## Comment 10498
Date: 2008-10-21 13:57:15 +0200
From: @drstmane
Ah, here's the actual problem (and I actually consider this a bug):
With
sql>create table way_tags (way integer);
0 tuples
query
sql>SELECT * FROM way_tags WHERE waysid = 100;
^^^^^^
!SELECT: identifier 'waysid' unknown
0 tuples
correctly issues an error,
query
sql>SELECT * FROM way_tags WHERE way_tags.waysid = 100;
^^^^^^^^^^^^^^^
0 tuples
does not.
The difference is most probably related to giving only an attribute name vs. giving <table_name>.<attribute_name> ...
## Comment 10499
Date: 2008-10-21 14:06:10 +0200
From: @drstmane
While MonetDB/SQL correctly issued an error when trying to use a non-existing unqualified column name, it seems to fail to do so in case of non-existing qualified column names:
(with CVS HEAD of Tue Oct 21 09:19:22 CEST 2008, configured with defaults, compiled with gcc 4.1.2 on 64-bit Fedora 8)
sql>select * from t where b = 0;
!SELECT: identifier 'b' unknown
0 tuples
sql>select * from t where t.b = 0;
0 tuples
sql>select * from t where s.a = 0;
!SELECT: no such column 's.a'
0 tuples
## Comment 10500
Date: 2008-10-21 14:11:16 +0200
From: @drstmane
for got this in my previous posting below:
sql>create table t (a integer);
0 tuples
(ps: see my previous posting below as an example how to file a proper useful bug report including minimal instructions to fully reproduce the problem and information about where the problem occurs --- any (successful) attempt to learn from that would be highly appreciated...)
## Comment 10501
Date: 2008-10-21 15:53:52 +0200
From: @drstmane
Fixed by Niels in CVS.
Thanks for the quick fix, Niels!
## Comment 10502
Date: 2008-10-21 18:54:47 +0200
From: @skinkie
Niels, thanks for fixing it.
@Stefan:
"The difference is most probably related to giving only an attribute name
vs. giving <table_name>.<attribute_name> ..."
I think you found something out that I was not mentally aware of at the time of 'seeing' this bug, fundamentally you already knew what was wrong. With mentioning 'unexpected behavior occurs' I was not aware of it.
## Comment 10503
Date: 2008-10-21 19:24:52 +0200
From: @drstmane
@skinkie:
I did not know what was wrong, I simply located and analyzed the problem as follow (you may read and learn, if you want to):
You said:
"
SELECT * FROM way_tags WHERE waysid = 100;
In this table the field waysid does not exist, and the query will also
return 0 tuples.
"
but I found out:
"
sql>create table way_tags (way integer);
0 tuples
sql>SELECT * FROM way_tags WHERE waysid = 100;
!SELECT: identifier 'waysid' unknown
0 tuples
"
(I still don't know, whether you got this error message or not --- I cannot imagine why it should not have occurred in your case, but have no clue why you did not mention it...)
Then, I just looked at the relevant differences between you ("simple") first query and your ("complex") second query, noticed that this might be the qulified vs. non qualified column name in the predicate, tried it, and found the problem (and a very simple way to reproduce it).
Well, I do not necessarily expect that users do all this analysis (though it was trivial and straight forward in this case), but they should at least provide all relevant information in a bug report --- in this case: mentioning clearly whether there was a (correct and to be expected!) error message with the first query and what exactly the "Unexpected behavior" of the second one was --- or not expect any quick or "useful" reply ...
## Comment 10504
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2183288 at http://sourceforge.net/support/tracker.php?aid=2183288
| SQL: no error about invalid *qualified* column name | https://api.github.com/repos/MonetDB/MonetDB/issues/1862/comments | 0 | 2020-11-30T10:04:45Z | 2024-06-27T11:33:13Z | https://github.com/MonetDB/MonetDB/issues/1862 | 753,337,091 | 1,862 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-18 09:58:59 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2009-04-17 11:37:14 +0200
## Comment 10468
Date: 2008-10-18 21:58:59 +0200
From: @skinkie
I presume NLS must be systemwide enabled in order get working 'foreign' output in mclient. What I now see is that probably the pipe to stdout breaks on a foreign characters:
| 22771762 | power | line | 22771762 | 22 | 290062167 | 290062167 | 50.91285649999 | 6.130952899999 | Team_Alpha | 2008-08-22 |
: : : : : : : : 9997 : 9996 : : 06:04:08.000000 :
: : : : : : : : : : : +00:00 :
| 22772346 | power | line | 22772346 | 0 | 244473999 | 244473999 | 50.79486810000 | 6.973957699999 |12315 tuples
sql>select * from way_tags, way_nds, nodes_legacy where k='power' and v='line' and way_tags.way = way_nds.way and way_nds.to_node = nodes_legacy.id;
12315 tuples
## Comment 10469
Date: 2008-10-20 10:33:53 +0200
From: @sjoerdmullender
Please provide details.
Read and internalize <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>.
## Comment 10470
Date: 2008-10-20 12:12:03 +0200
From: @skinkie
I take this as offensive; there is enough information to reproduce the bug on something like UTF8 characters. If even the authors of mclient are not surprised what the output of the second query is <<12315 tuples>> without setting any '>'-option, better to not improve my bug reporting skills.
## Comment 10471
Date: 2008-10-20 12:28:27 +0200
From: @grobian
Unfortunately SF eats whitespace, so I'm not able to see the problem proper, but can it be that you're bitten by mclient breaking up long values in an attempt not to get wider than your terminal size?
## Comment 10472
Date: 2008-10-20 12:38:23 +0200
From: @skinkie
(I'm using the new and improved bugtracker maybe that helps)
The issue is not the white space, the issue is the sudden loss of output to stdout. If you take a peak on the 'line' with 22771762, you notice a string Team_Alpha. Now look forward to '22772346' you notice 12315 tuples. For the reason, that I can positively mark as 'in some way related to my recompiling to -nls' (in gentoo terms), http://openstreetmap.org/api/0.5/node/244473999 where the user-value is set to 'FSürth'.
Now how can I know that I didn't screw up Mserver5, or Mapi in that perspective? Because my alternative lookup mechanism still works, and is working on this same dataset.
http://thuis.konink.de/api/0.5/node/244473999
## Comment 10473
Date: 2008-10-20 20:20:45 +0200
From: @drstmane
Works for me:
sql>create table MyTab (MyAtt string);
0 tuples
sql>insert into MyTab values ('FSürth');
Rows affected 1
sql>select * from MyTab;
+---------+
| myatt |
+=========+
| FSürth |
+---------+
1 tuple
sql>
## Comment 10474
Date: 2008-10-20 23:26:25 +0200
From: @skinkie
I presume you have a Linux distro that has NLS enabled, like I did before I thought I could strip it to save more space for my VM/LiveCD.
SQLrow (len=0x8713698, numeric=0x87136c8, rest=0x87136b0, fields=5, trim=1) at ../../../src/mapiclient/MapiClient.mx:4
408 for (i = 0; i < fields; i++) {
(gdb)
409 if ((t = rest[i]) != NULL && utf8strlen(t) > (size_t) len[i]) {
(gdb)
utf8strlen (s=0x8713610 "FSürth") at ../../../src/mapiclient/MapiClient.mx:370
Considering that; I presume something in stream_printf goes wrong where toConsole is changed. If you want to debug it, of course a quest account is possible within my vm.
## Comment 10475
Date: 2008-10-21 08:44:43 +0200
From: @grobian
what does `locale` say on your system?
## Comment 10476
Date: 2008-10-21 08:56:00 +0200
From: @drstmane
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=nl_NL.UTF-8
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
## Comment 10477
Date: 2008-10-21 09:01:26 +0200
From: @grobian
sorry, I meant
@skinkie: what does `locale` say, and what does `perl -e ''` say?
## Comment 10478
Date: 2008-10-21 09:09:06 +0200
From: @drstmane
I know, but for completeness, I added mine, too ;-)
## Comment 10479
Date: 2008-10-21 14:54:06 +0200
From: @skinkie
locale
------
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER="POSIX"
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
perl -e ''
--------
<< returns nothing >>>
## Comment 10480
Date: 2008-10-21 15:58:21 +0200
From: @grobian
utf-8 chars on a posix/C locale is guaranteed to be problematic, IMO.
## Comment 10481
Date: 2008-10-21 16:20:33 +0200
From: @sjoerdmullender
mclient -lsql -Eiso-8859-1
We had to ask lots of questions for you to finally provide some useful information. If you had internalized the document I pointed you to, that would not have been necessary. If you feel insulted, tough. But please do read that document. We have better things to do than trying to be clairvoyant.
## Comment 10482
Date: 2008-10-21 16:57:56 +0200
From: @skinkie
@sjoerd; personally i would connect non-nls as posix locale but that is me. So still the bug exist, I read the document after you pointed it to me. In this document is also mentioned 'show to the programmer the output of your program' that is the thing I did with the initial posting. I also mentioned what I *thought* would be the problem. But I'll try to be more verbose.
@mr-meltdown; do you agree with me that in this case GDB was not able to output too? while it actually does?
## Comment 10483
Date: 2008-10-21 17:39:40 +0200
From: @drstmane
@skinkie: FYI, here is how I read your initial report --- judge yourself whether is it sufficient information to reproduce and understand your problem:
"
I presume NLS must be systemwide enabled in order get working 'foreign' output in mclient.
"
Ok, so you do have NLS enabled (or not?) on your system --- hm, which (operating) system are you actually using, here?
In fact, what do you refer to with NLS, here? --- See, e.g., http://en.wikipedia.org/wiki/NLS for a list of alternatives; even in "Computing" there are (at least) three (cf., http://en.wikipedia.org/wiki/NLSComputing) --- let's assume "Native Language Support" --- so, what is your native language? --- ah, I happen to know (I guess...): Dutch --- so, you're using a Dutch systems. Good.
Hence, all non-dutch characters are 'foreign" to you? --- hm, 'ë' should work fine, then ...
"
What I now see is that probably the pipe to stdout breaks on a foreign characters:
"
"Now?" --- but at least if works fine when redirecting into a file?
"
| 22771762 | power | line | 22771762 | 22 | 290062167 | 290062167 | 50.91285649999 | 6.130952899999 | Team_Alpha | 2008-08-22 |
: : : : : : : : 9997 : 9996 : : 06:04:08.000000 :
: : : : : : : : : : : +00:00 :
| 22772346 | power | line | 22772346 | 0 | 244473999 | 244473999 | 50.79486810000 | 6.973957699999 |12315 tuples
"
Some output; good.
But what is wrong with that output?
What is / would have been correct?
What did you expect?
Who/what produced that output?
Ok, yet another guessing exercise: Let's assume this is a result of some SQL query, run on some (unknown) data, most probably using some not-specified version of MonetDB/SQL, run via mclient in some terminal or command shell with Dutch NLS (see above).
The queries produces 12315 tuples with 33 attributes each; like the query itself, the first 12313 tuples have not been added to this bug report, the last-ut-one tuple apprears to be complete; the last tuple has been cut off after 9 attribute --- still no indication what kind of 'foreign' character might have been expected and/or cause any problem ...
Since there is no other information, we must assume that the number of result tuples (12315) is correct.
"
sql>select * from way_tags, way_nds, nodes_legacy where k='power' and v='line' and way_tags.way = way_nds.way and way_nds.to_node = nodes_legacy.id;
12315 tuples
"
Ah, now we have a query --- but no indication what so ever, why it appears here...
Is it related to the problem? If so how?
It is identical with / similar to / different from the query that created the above output?
At least is produces the same number of tuples: 12315 --- guess this is correct, again --- isn't it??
For brevity of the report, the user now chose to omit all 12315 tuples; hence, they were most probably what he expected. Good.
So --- What was the actual problem, again?
How was the problem triggered?
How can we reproduce it?
... Oh, the first followup of the user tells us more:
"
[...] there is enough information to reproduce the bug on something like UTF8 characters.
"
Yes? What bug? What information?
"
If even the authors of mclient are not surprised what the output of the second query is <<12315 tuples>> without setting any '>'-option, better to not improve my bug reporting skills.
"
Hm, since you refuse to give the slightest information what kind of data you run your query on, or at least which result you would have expected, how shall be able to guess whether 12315 tuples is correct or not?
And what is a "'>'-option"?
...
Well, I guess, that should be enough to get the picture --- even without http://www.chiark.greenend.org.uk/~sgtatham/bugs.html, common sense might suggest that "showing output" without any indication how that output was produced and/or what is wrong with that output, and what would have been correct is just as much information as showing no output at all.
## Comment 10484
Date: 2008-10-21 18:30:18 +0200
From: @skinkie
sql>create table MyTab (MyAtt string);
!CREATE TABLE: name 'mytab' already in use
0 tuples
sql>insert into MyTab values ('FSürth');
more>select * from MyTab;
more>
This is what you requested. (More important things on my mind right now see private mail). Yes, it was insufficient.
## Comment 10485
Date: 2008-10-21 18:57:48 +0200
From: @skinkie
@Stefan:
And what is a "'>'-option"?
The option to redirect all output of the server to a file?
## Comment 10486
Date: 2008-10-21 20:13:40 +0200
From: @drstmane
Also for input, the encoding used by your mclient must match the encoding of the input data --- with interactive input, this is the encoding that your shell / terminal uses, where you started mclient.
By default, mclient uses (and hence expects) UTF-8 encoding; you can change this by using mclient's "-E"/"--encoding" command line option; see also `mclient --help`.
In case the encoding do not match, the behavior may be "unexpected" as the charaters are interpreted differently than they (seem to) look.
## Comment 10487
Date: 2008-10-21 20:33:47 +0200
From: @skinkie
I can understand the behaviour you that happens when inserting in a 'wrong' encoding as the client in it. Although, shouldn't respect the encoding that the terminal is in? Hence the environment variable.
But the other way around; it seems that data inside the database is able to manipulate the client; it goes to far for me to say it is exploitable, because I don't know where the console output is redirected to upon such character is found (hence I was also unable to see what under the hood goes wrong). But upon the existence of such character a redirect can occur vs uninitialisation of console parameter.
sql>\>/tmp/test
sql>select * from nodes_legacy where id = 244473999;
This result in the right output in the file test.
## Comment 10488
Date: 2008-10-21 22:15:00 +0200
From: @sjoerdmullender
Finally we have enough information to tell what's going on.
Because your locale is POSIX, the character set is ANSI_X3.4-1968. This is a 7-bit encoding, so cannor represent non-ASCII characters. This means that mclient cannot convert non-ASCII characters such as the ü. Because the conversion fails, the output stream refuses to do anything more.
So there is a bug in that if character conversion fails, the error is not properly reported and the stream stops working.
If you want to use non-ASCII characters, don't use the C/POSIX locale but use a locale that actually supports the character set you want to use. mclient uses the locale automatically, but you can override with the -E option, so you could use -Eiso-8859-1. But remember, because of your environment, that is not the locale you're actually using.
## Comment 10489
Date: 2008-10-22 13:53:01 +0200
From: @drstmane
Stefan ("skinkie"),
could you "live" with the below behavior after Sjoerd's yesterday's changes?
If so, please feel free to close this bug report.
===================================================================
2008/10/21 - sjoerd: MonetDB/src/common/stream.mx,1.173
Added function to clear stream error so that we can continue after an
error.
This is needed for mclient.
===================================================================
2008/10/21 - sjoerd: clients/src/mapiclient/MapiClient.mx,1.124
Report write error and clear the stream so that we can continue.
Unfortunately the reason for the write error is lost, so the best we
can do now is to report that there was an error.
Convert command line query according to specified or implied encoding.
===================================================================
Basically, mclient now issues a "write error", if the chosen encoding does not allow mclient to properly output certain (not supported) characters:
========
$ locale
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=nl_NL.UTF-8
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=
$ mclient -lsql
sql>create table MyTab (MyAtt string);
0 tuples
sql>insert into MyTab values ('FSürth');
Rows affected 1
sql>select * from MyTab;
+---------+
| myatt |
+=========+
| FSürth |
+---------+
1 tuple
sql>
$ mclient -lsql -Eiso-8859-1
sql>select * from MyTab;
+---------+
| myatt |
+=========+
| FS�rth |
+---------+
1 tuple
sql>insert into MyTab values ('FSürth');
Rows affected 1
sql>select * from MyTab;
+-----------+
| myatt |
+===========+
| FS�rth |
| FSürth |
+-----------+
2 tuples
sql>
$ mclient -lsql -EANSI_X3.4-1968
sql>select * from MyTab;
+-----------+
| myatt |
+===========+
|2 tuples
write error
sql>insert into MyTab values ('FSürth');
more>;
more>'
more>;
!syntax error, unexpected SCOLON, expecting ')' or ',' in: "insert into mytab values ('FS;
!'
!;"
0 tuples
sql>
$ export LANG=''
$ locale
LANG=
LC_CTYPE="POSIX"
LC_NUMERIC="POSIX"
LC_TIME="POSIX"
LC_COLLATE="POSIX"
LC_MONETARY="POSIX"
LC_MESSAGES="POSIX"
LC_PAPER=nl_NL.UTF-8
LC_NAME="POSIX"
LC_ADDRESS="POSIX"
LC_TELEPHONE="POSIX"
LC_MEASUREMENT="POSIX"
LC_IDENTIFICATION="POSIX"
LC_ALL=
13:45:02 manegold@rig:~/_/scratch0/Monet/Testing/Current $ mclient -lsql
sql>select * from MyTab;
+-----------+
| myatt |
+===========+
|2 tuples
write error
sql>
$ mclient -lsql -EANSI_X3.4-1968
sql>select * from MyTab;
+-----------+
| myatt |
+===========+
|2 tuples
write error
sql>
$ mclient -lsql -Eiso-8859-1
sql>select * from MyTab;
+-----------+
| myatt |
+===========+
| FS�rth |
| FSürth |
+-----------+
2 tuples
sql>
$ mclient -lsql -Een_US.UTF-8
mclient: warning: cannot convert local character set en_US.UTF-8 to UTF-8
mclient: warning: cannot convert UTF-8 to local character set en_US.UTF-8
sql>select * from MyTab;
+-----------+
| myatt |
+===========+
| FSürth |
| FSürth |
+-----------+
2 tuples
sql>
========
## Comment 10490
Date: 2008-10-22 22:12:42 +0200
From: @skinkie
Is it possible the patch has not been propagated in public cvs yet?
I don't see any difference after updating, will try tomorrow too.
## Comment 10491
Date: 2008-11-08 15:54:06 +0100
From: @skinkie
/opt/monetdb/bin/mclient -lsql
sql>create table MyTab (MyAtt string);
0 tuples
sql>insert into MyTab values ('FSürth');
more>!unexpected end of input
0 tuples
/opt/monetdb/bin/mclient -lsql -Eutf8
sql>insert into MyTab values ('FSürth');
Rows affected 1
I guess this is the 'as expected behavior' on a client that is POSIX. It might be even worthwhile to pursuit a fix for Xterm. Hence, the locale should affect what is displayed in the client. Hence if pasting a 'ü' works, but the current locale prohibits it then it should not be pasted *as* an 'ü' in the first place by local rendering rules.
/opt/monetdb/bin/mclient -lsql
sql>select * from MyTab;
+---------+
| myatt |
+=========+
|1 tuple
write error
sql>select * from users;
+---------+---------------+----------------+
| name | fullname | default_schema |
+=========+===============+================+
| monetdb | MonetDB Admin | 1061 |
+---------+---------------+----------------+
1 tuple
/opt/monetdb/bin/mclient -lsql -Eutf-8
sql>select * from MyTab;
+---------+
| myatt |
+=========+
| FSürth |
+---------+
## Comment 10492
Date: 2008-11-08 19:39:00 +0100
From: @mlkersten
Originator approved the resolution
## Comment 10493
Date: 2009-02-17 01:39:52 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test.
## Comment 10494
Date: 2009-04-17 11:37:14 +0200
From: @sjoerdmullender
I extended the test sql/src/test/mapi/Tests/utf8test.SQL.py with a case that covers this issue.
## Comment 10495
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2177734 at http://sourceforge.net/support/tracker.php?aid=2177734
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.
| Output breaks on foreign characters | https://api.github.com/repos/MonetDB/MonetDB/issues/1861/comments | 0 | 2020-11-30T10:04:41Z | 2024-06-27T11:33:12Z | https://github.com/MonetDB/MonetDB/issues/1861 | 753,337,043 | 1,861 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-16 11:26:44 +0200
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2008-10-20 10:56:38 +0200
## Comment 10461
Date: 2008-10-16 11:26:44 +0200
From: @skinkie
As mentioned before there are several things broken related to the daemon mode mentioned in the documentation.
--daemon=yes ; does not work at all, it does not remove the shell, nor does it make mserver5 go to the background
--set monet_daemon; actually removes the shell from the operation, but still a & is needed to make it go to the background.
The easy work around seem to use merovingian, but this would still not solve the commandline issues.
The feature request would be to support automatic backgrounding, without console output.
## Comment 10462
Date: 2008-10-16 12:37:00 +0200
From: @sjoerdmullender
Could you please point out where in the documentation you read about daemon mode?
Normally, Mserver and mserver5 both read commands from stdin. The daemon flag tells the server to not do that. That's it. That is a requirement if you want to be able to run the server as a daemon. If the documentation says otherwise, there is a bug in the documentation. If you think that it should do more (such as if (fork() > 0) exit(0);), it is a feature request.
## Comment 10463
Date: 2008-10-16 12:47:58 +0200
From: @skinkie
skinkie@iBook ~ $ /opt/cherokee/bin/mserver5 --help
Usage: /opt/cherokee/bin/mserver5 [options] [scripts]
--dbname=<database_name>
--dbfarm=<directory>
--dbinit=<stmt> Server prepare statement
--config=<config_file>
*** --daemon=yes|no run in background [no] ***
I think background is very clear, hence not disabling the input only and keep hanging on the console.
## Comment 10464
Date: 2008-10-20 10:55:58 +0200
From: @sjoerdmullender
The help message now says:
--daemon=yes|no Do not read commands from standard input [no]
which is exactly what the option does.
## Comment 10465
Date: 2008-10-20 12:23:42 +0200
From: @skinkie
So the fix is to just changing documentation, instead of picking it up as a bug in the code? Ignorance is bliss. Maybe you can add the feature request yourself, since your feature request will obviously result in something you know how to describe or was it just out of frustration that you[1] changed the strings instead of fixing the actual feature described by it?
[1] http://monetdb.cvs.sourceforge.net/viewvc/monetdb/MonetDB5/src/tools/mserver5.mx?r1=1.51&r2=1.52
## Comment 10466
Date: 2008-10-20 12:26:42 +0200
From: @grobian
The feature is just misnamed, I think you'll have to live with an mserver that cannot properly be daemonised.
## Comment 10467
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2171063 at http://sourceforge.net/support/tracker.php?aid=2171063
| Daemon mode broken | https://api.github.com/repos/MonetDB/MonetDB/issues/1860/comments | 0 | 2020-11-30T10:04:38Z | 2024-06-27T11:33:11Z | https://github.com/MonetDB/MonetDB/issues/1860 | 753,337,002 | 1,860 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-15 12:46:32 +0200
From: @skinkie
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
CC: @sjoerdmullender
Last updated: 2010-07-09 15:11:29 +0200
## Comment 10457
Date: 2008-10-15 12:46:32 +0200
From: @skinkie
This is a version before the latest CVS release, but I am a bit shocked by the amount of errors present at start:
[many more]
!ERROR:
!ERROR: BBPinit: ignore line 774 32 tmp_1406 . 14/1406 36513 2 0 0 0 0 256 0 0 0
0 oid 8 0 1089 0 0 0 0 1002441 0 2048 0 int 4 0 1089 0 0 0 0 1002442 0 1024 0
!ERROR:
!ERROR: BBPinit: ignore line 775 32 tmp_1407 . 14/1407 17127920 2 31 0 0 31 1024
0 0 0 0 void 0 1 1345 0 0 0 0 1002443 0 0 0 int 4 0 1024 0 0 4 0 4002423 124 40
96 0
!ERROR:
!ERROR: BBPinit: ignore line 776 32 tmp_1410 . 14/1410 36506 2 0 0 0 0 256 0 0 0
0 oid 8 0 1089 0 0 0 0 1002150 0 2048 0 str 8 1 1089 0 0 0 0 1002151 0 2048 0 8
192 11272 0
!ERROR:
!ERROR: BBPinit: ignore line 777 32 tmp_1411 . 14/1411 36508 2 0 0 0 0 256 0 0 0
0 oid 8 0 1089 0 0 0 0 1002152 0 2048 0 str 8 1 1089 0 0 0 0 1002153 0 2048 0 8
192 11272 0
!ERROR:
!ERROR: BBPinit: ignore line 778 32 tmp_1412 . 14/1412 36511 2 0 0 0 0 256 0 0 0
0 oid 8 0 1089 0 0 0 0 1002154 0 2048 0 oid 8 0 1089 0 0 0 0 1002155 0 2048 0
!ERROR:
MonetDB Server v5.0.0
Copyright (c) 1993-2007 CWI, all rights reserved
Compiled for x86_64-unknown-linux-gnu/64bit with 64bit OIDs dynamically linked
dbname:demo
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see /opt/monetdb/etc/monetdb5.conf)
At the second start the errors are gone. What does the above 'mean'?
## Comment 10458
Date: 2008-10-15 13:18:08 +0200
From: @drstmane
MonetDB Server v5.0.0
Copyright (c) 1993-2007 CWI, all rights reserved
is *very* old --- lastest release is
MonetDB server v5.6.0, based on kernel v1.24.0
Copyright (c) 1993-2008 CWI, all rights reserved
and lastest development CVS version is
MonetDB server v5.7.0, based on kernel v1.25.0
Copyright (c) 1993-July 2008 CWI.
Copyright (c) August 2008- MonetDB B.V., all rights reserved
there have been multiple changes in between that made the binary formats incompatible.
Hence, it is neither possible to run an "old" MonetDB on new database nor vice versa.
Up-(/down-)grading requires dump & restore of the database(s) as described in the respective release notes on the MonetDB website.
## Comment 10459
Date: 2008-10-15 13:25:34 +0200
From: @skinkie
Clearly my skills in executing the right mserver binary on my system also suck :(
## Comment 10460
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2168123 at http://sourceforge.net/support/tracker.php?aid=2168123
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14325
Date: 2010-07-09 15:11:29 +0200
From: @sjoerdmullender
Bug was DELETED in SF.
| Errors at startup | https://api.github.com/repos/MonetDB/MonetDB/issues/1859/comments | 0 | 2020-11-30T10:04:34Z | 2024-06-28T13:27:48Z | https://github.com/MonetDB/MonetDB/issues/1859 | 753,336,949 | 1,859 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-14 11:30:23 +0200
From: @lsidir
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-10-14 06:24:11 +0200
## Comment 10454
Date: 2008-10-14 11:30:23 +0200
From: @lsidir
After the checkins of 13/10 in the head of algebra, the following tests fail:
tests/BugTracker/replace-corrupts.SF-1758902
tests/XQuery/element4
tests/XQuery/element6
with the error:
!ERROR: missing matches. The result requires the same number of tuples as the first two input arguments
## Comment 10455
Date: 2008-10-14 18:24:11 +0200
From: Jan Rittinger <<jan.rittinger>>
Fixed in CVS.
## Comment 10456
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2165793 at http://sourceforge.net/support/tracker.php?aid=2165793
| XQ: missing matches | https://api.github.com/repos/MonetDB/MonetDB/issues/1858/comments | 0 | 2020-11-30T10:04:31Z | 2024-06-27T11:33:09Z | https://github.com/MonetDB/MonetDB/issues/1858 | 753,336,918 | 1,858 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-14 09:02:34 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2010-05-04 11:05:29 +0200
## Comment 10450
Date: 2008-10-14 09:02:34 +0200
From: @skinkie
skinkie@iBook /usr/src/skinkie/monetdb $ gdb /opt/cherokee/bin/mserver5
GNU gdb 6.8
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "powerpc-unknown-linux-gnu"...
(gdb) run
Starting program: /opt/cherokee/bin/mserver5
[Thread debugging using libthread_db enabled]
[New Thread 0x48021820 (LWP 669)]
[New Thread 0x4bd6c4b0 (LWP 672)]
MonetDB server v5.7.0, based on kernel v1.25.0
Serving database 'demo', using 1 thread
Compiled for powerpc-unknown-linux-gnu/32bit with 32bit 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
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x48021820 (LWP 669)]
0x00000000 in ?? ()
(gdb) bt
0 0x00000000 in ?? ()
1 0x0ff6cf8c in SABAOTHinit (dbfarm=0x1002c83c "", dbname=0x1002f8b0 "demo") at ../../../src/mal/mal_sabaoth.mx:104
Backtrace stopped: frame did not save the PC
(gdb)
Congratulations with incorporating MonetDB B.V., legally for every publication of MonetDB B.V. a registration number of the Camber of Commerce need to be presented. I hope sourceforge users will get their support and bug tickets for free ;)
As might noted from the first line this is a PPC, I had compiled the latest version of MonetDB this night with profiling enabled, this didn't result in a pleasant experience. Looking at strace it was busy waiting, I don't care for profiling now, but I do care about the possibility to start the server :)
## Comment 10451
Date: 2008-10-14 09:15:23 +0200
From: @skinkie
I'm hitting the same 'compilation' issue as before... libraries are probably not compatible.
## Comment 10452
Date: 2008-10-14 09:45:32 +0200
From: @skinkie
My compiling skills suck.
## Comment 10453
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2165518 at http://sourceforge.net/support/tracker.php?aid=2165518
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.
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
| SABAOTHinit fails on PPC | https://api.github.com/repos/MonetDB/MonetDB/issues/1857/comments | 0 | 2020-11-30T10:04:28Z | 2024-06-28T13:27:47Z | https://github.com/MonetDB/MonetDB/issues/1857 | 753,336,874 | 1,857 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-12 01:55:52 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-10-12 02:23:40 +0200
## Comment 10447
Date: 2008-10-12 13:55:52 +0200
From: @drstmane
TestTools/extract_error_messages fails to report (via email) the following errors with `make rpm`:
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB4/.GNU.64.64.d.1-Fedora8..2008.10.12_00-09-02/rpm.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/MonetDB5/.GNU.64.64.d.1-Fedora8..2008.10.12_00-09-02/rpm.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/sql/.GNU.64.64.d.1-Fedora8..2008.10.12_00-09-02/rpm.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.32.d.1-Fedora8..2008.10.12_00-09-02/rpm.out.html
## Comment 10448
Date: 2008-10-12 14:23:16 +0200
From: @grobian
make[5]: x: Command not found
make[5]: [embeddedclient.c] Error 127 (ignored)
The errors are (purposely) ignored, and hence also ignored by extract_error_messages.
## Comment 10449
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2161346 at http://sourceforge.net/support/tracker.php?aid=2161346
| TestTools/extract_error_messages fails to report rpm errors | https://api.github.com/repos/MonetDB/MonetDB/issues/1856/comments | 0 | 2020-11-30T10:04:25Z | 2024-06-28T07:37:08Z | https://github.com/MonetDB/MonetDB/issues/1856 | 753,336,833 | 1,856 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-12 10:30:28 +0200
From: @mlkersten
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-10-12 06:05:03 +0200
## Comment 10444
Date: 2008-10-12 10:30:28 +0200
From: @mlkersten
Merovingian assumes var/log to exist on platforms to store its file merovingian.log. The path creation should be added and the file should be moved to var/MonetDB5/
## Comment 10445
Date: 2008-10-12 18:05:02 +0200
From: @mlkersten
restore the situation and solve it differently,
e.g. more robust error handling
## Comment 10446
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2161047 at http://sourceforge.net/support/tracker.php?aid=2161047
| Merovingian does not handle missing dir | https://api.github.com/repos/MonetDB/MonetDB/issues/1855/comments | 0 | 2020-11-30T10:04:21Z | 2024-06-28T07:37:07Z | https://github.com/MonetDB/MonetDB/issues/1855 | 753,336,789 | 1,855 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-09 09:11:27 +0200
From: Peter M. Murray <<yarrumretep>>
To: @njnes
Version: -- development
Last updated: 2008-10-09 09:43:48 +0200
## Comment 10441
Date: 2008-10-09 21:11:27 +0200
From: Peter M. Murray <<yarrumretep>>
In trying to emulate the SQL:2003 WITH CUBE clause by permuting group by elements and joining multiple selects with UNION ALL, we ran into this issue. It seems that when using NULL in the select statement to align the columns for UNION ALL, the queries sometimes return no results or erroneous results. Here is a small SQL script that illustrates this:
create table testola (color varchar(128), count integer);
insert into testola values ('blue', 12);
insert into testola values ('red', 2);
select color, null, sum(count) from testola group by color;
I would expect the results to be:
blue, null, 12
red, null, 2
but instead monetdb returns no results for this query. If you remove the null, it works fine.
## Comment 10442
Date: 2008-10-09 21:44:47 +0200
From: @njnes
This bug was already fixed in cvs (both stable and current). Added a test anyway in
groupby_with_NULL.SF-2155606.sql
## Comment 10443
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2155606 at http://sourceforge.net/support/tracker.php?aid=2155606
| GROUP BY query returns no results | https://api.github.com/repos/MonetDB/MonetDB/issues/1854/comments | 0 | 2020-11-30T10:04:18Z | 2024-06-27T11:33:05Z | https://github.com/MonetDB/MonetDB/issues/1854 | 753,336,742 | 1,854 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-09 04:39:49 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-11-09 09:53:41 +0100
## Comment 10433
Date: 2008-10-09 04:39:49 +0200
From: @skinkie
I was checking out my previous bug. That is still creating a segmentation fault. But I am very surprised that with this segmentation fault my complete (just inserted) table was lost.
...trivial to add. But I could do better things with my time.
## Comment 10434
Date: 2008-10-20 11:01:27 +0200
From: @sjoerdmullender
Details, details. How on earth do you think we can ever hope to fix any bugs when you don't provide even the merest hint of what you were doing and what happened.
## Comment 10435
Date: 2008-10-20 12:08:13 +0200
From: @skinkie
I'm sorry, I'm not going to add more comments if you cannot parse basic English text and solve bugs by making them 'by design' and fix documentation accordingly.
If you cannot interpreted table lost after segmentation fault I clearly doubt the willingness to fix the problem in the first place. It doesn't really matter what exactly I am doing if there is no signal handler that actually makes sure the data is safe.
## Comment 10436
Date: 2008-10-20 20:26:53 +0200
From: @drstmane
Transaction semantics demand that non-committed changes have no effect if the transaction is aborted (e.g.) due to a crash.
## Comment 10437
Date: 2008-10-20 23:45:17 +0200
From: @skinkie
If I recall correctly I already did a query after using copy into. Do I understand your comment right that there is actually possibility that there are non committed changes *after* a transaction took place? (Hence the insert was finished, otherwise I couldn't do my crashing query.)
The trashing query doesn't crash anymore, it is nicely handled, so I hope more code improvements have been made to prevent dataloss.
## Comment 10438
Date: 2008-10-20 23:59:15 +0200
From: @drstmane
Yes, database systems do allow more than one transaction; hence, there can be non-committed changes in a (not yet committed) transaction that follows a previous committed or aborted transaction.
## Comment 10439
Date: 2008-11-09 21:53:41 +0100
From: @mlkersten
Given the remarks made at 2008-10-20 I consider this
bug as being closed.
There is not enough information to re-construct
the errors and cast it into a nightly test.
## Comment 10440
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2154236 at http://sourceforge.net/support/tracker.php?aid=2154236
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.
| On server crash last added table was lost | https://api.github.com/repos/MonetDB/MonetDB/issues/1853/comments | 0 | 2020-11-30T10:04:15Z | 2024-06-28T07:37:07Z | https://github.com/MonetDB/MonetDB/issues/1853 | 753,336,697 | 1,853 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-08 11:41:14 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-10-09 02:00:25 +0200
## Comment 10429
Date: 2008-10-08 23:41:14 +0200
From: @skinkie
/bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../src/mal -I../.. -I../../../src/mal -I../optimizer -I../../../src/mal/../optimizer -I../scheduler -I../../../src/mal/../scheduler -I../modules/kernel -I../../../src/mal/../modules/kernel -I/opt/osm/include/MonetDB -I/opt/osm/include/MonetDB/common -I/opt/osm/include/MonetDB/gdk -DLIBMAL -Wall -Wextra -std=c99 -g -pg -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c -o libmonetdb5_la-mal_instruction.lo `test -f 'mal_instruction.c' || echo '../../../src/mal/'`mal_instruction.c
libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../src/mal -I../.. -I../../../src/mal -I../optimizer -I../../../src/mal/../optimizer -I../scheduler -I../../../src/mal/../scheduler -I../modules/kernel -I../../../src/mal/../modules/kernel -I/opt/osm/include/MonetDB -I/opt/osm/include/MonetDB/common -I/opt/osm/include/MonetDB/gdk -DLIBMAL -Wall -Wextra -std=c99 -g -pg -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c mal_instruction.c -fPIC -DPIC -o .libs/libmonetdb5_la-mal_instruction.o
../../../src/mal/mal_instruction.mx: In functie ‘instruction2str’:
../../../src/mal/mal_instruction.mx:2700: fout: expected ‘)’ before ‘BUNFMT’
## Comment 10430
Date: 2008-10-09 00:53:25 +0200
From: @skinkie
I see in this include thing some strange location of headers. I'll try to recompile everything now.
## Comment 10431
Date: 2008-10-09 02:00:25 +0200
From: @skinkie
Stupid header problems...
## Comment 10432
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2153852 at http://sourceforge.net/support/tracker.php?aid=2153852
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.
| MonetDB5 compilation failure (mal) | https://api.github.com/repos/MonetDB/MonetDB/issues/1852/comments | 0 | 2020-11-30T10:04:12Z | 2024-06-28T07:37:07Z | https://github.com/MonetDB/MonetDB/issues/1852 | 753,336,655 | 1,852 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-08 11:20:35 +0200
From: @skinkie
To: GDK devs <<bugs-common>>
Version: -- development
Last updated: 2008-10-08 11:41:40 +0200
## Comment 10422
Date: 2008-10-08 23:20:35 +0200
From: @skinkie
ibtool: compile: gcc -DHAVE_CONFIG_H -I. -I../../../src/monetdb5 -I../.. -I../../../src/monetdb5 -I/opt/osm/include/MonetDB -I/opt/osm/include/MonetDB/common -I/opt/osm/include/MonetDB/gdk -I/opt/osm/include/MonetDB5/atoms -I/opt/osm/include/MonetDB5/compiler -I/opt/osm/include/MonetDB5/kernel -I/opt/osm/include/MonetDB5/mal -I/opt/osm/include/MonetDB5/optimizer -I/opt/osm/include/MonetDB5/scheduler -I/opt/osm/include/MonetDB5 -I/usr/include -I../lib -I../../../src/monetdb5/../lib -DLIBGEOM -Wall -Wextra -std=c99 -g -pg -Werror-implicit-function-declaration -Werror -Wpointer-arith -Wdeclaration-after-statement -Wundef -Wp,-D_FORTIFY_SOURCE=2 -D_REENTRANT -c geom.c -fPIC -DPIC -o .libs/lib_geom_la-geom.o
../../../src/monetdb5/geom.mx: In functie ‘wkb_size’:
../../../src/monetdb5/geom.mx:544: fout: ‘VAR_MAX’ undeclared (first use in this function)
../../../src/monetdb5/geom.mx:544: fout: (Each undeclared identifier is reported only once
../../../src/monetdb5/geom.mx:544: fout: for each function it appears in.)
make[5]: *** [lib_geom_la-geom.lo] Fout 1
(yes, I'm recompiling MonetDB)
## Comment 10423
Date: 2008-10-08 23:32:45 +0200
From: @sjoerdmullender
Update your MonetDB. VAR_MAX is defined in gdk.h (once you have updated).
## Comment 10424
Date: 2008-10-08 23:34:07 +0200
From: @drstmane
If you are using the latest CVS head of GEOM, you also need to use the latest CVS head of MonetDB, MonetDB5 & SQL
(we need to check the dependencies in the configure script).
If you're using the latest release branches of MonetDB, you also need to use the latest release branch of GEOM
(see the release notes on the MonetDB web site for details.
## Comment 10425
Date: 2008-10-08 23:37:29 +0200
From: @drstmane
resotring Sjoerd's settings after concurrent update (bug tracker is not transactional correct)
## Comment 10426
Date: 2008-10-08 23:38:59 +0200
From: @skinkie
Yes people, I am using the latest MonetDB... or at least, my massive update script is updating every directory. I'll try to do an make install in an empty directory and see if it still borks.
cd buildtools
rm -r Linux
./de-bootstrap
cvs up -dP
./bootstrap
mkdir Linux
cd Linux
../configure --prefix=/opt/cherokee --enable-debug --enable-assert --enable-profile
make && make install
cd ..
export PYTHONPATH=/opt/cherokee/lib64/python2.5/site-packages
cd MonetDB
rm -r Linux
./de-bootstrap
cvs up -dP
./bootstrap
mkdir Linux
cd Linux
../configure --prefix=/opt/cherokee --enable-debug --enable-assert --enable-profile
make && make install
cd ..
cd clients
rm -r Linux
./de-bootstrap
cvs up -dP
./bootstrap
mkdir Linux
cd Linux
../configure --prefix=/opt/cherokee --enable-debug --enable-assert --enable-profile
make && make install
cd ../..
cd MonetDB5
rm -r Linux
./de-bootstrap
cvs up -dP
./bootstrap
mkdir Linux
cd Linux
../configure --prefix=/opt/cherokee --enable-debug --enable-assert --enable-profile
make && make install
cd ../..
cd sql
rm -r Linux
./de-bootstrap
cvs up -dP
./bootstrap
mkdir Linux
cd Linux
../configure --prefix=/opt/cherokee --enable-debug --enable-assert --enable-profile
make && make install
cd ../..
cd geom
rm -r Linux
./de-bootstrap
cvs up -dP
./bootstrap
mkdir Linux
cd Linux
../configure --prefix=/opt/cherokee --enable-debug --enable-assert --enable-profile
make && make install
cd ../..
## Comment 10427
Date: 2008-10-08 23:40:41 +0200
From: @skinkie
See other bug.
## Comment 10428
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2153837 at http://sourceforge.net/support/tracker.php?aid=2153837
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.
| GEOM fails to compile VAR_MAX undeclared | https://api.github.com/repos/MonetDB/MonetDB/issues/1851/comments | 0 | 2020-11-30T10:04:08Z | 2024-06-28T07:37:07Z | https://github.com/MonetDB/MonetDB/issues/1851 | 753,336,614 | 1,851 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-08 06:41:01 +0200
From: Loredana Afanasiev <<lafanasi>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-17 06:30:21 +0100
## Comment 10415
Date: 2008-10-08 18:41:01 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi,
These seem like small bugs.
1.
[lafanasi@zookst4 ~]$ mclient -lx -s 'fn:string(<a><b/></a>/*)'
MAPI = monetdb@localhost:50000
QUERY = fn:string(<a><b/></a>/*)
ERROR = !fatal error: attribute 'pos' with type '0x4000' not found in environment
2.
[lafanasi@zookst4 ~]$ mclient -lx -s 'let $doc := <a><b>bla</b></a> return fn:substring($doc/*, 1,1)'
"b"
[lafanasi@zookst4 ~]$ mclient -lx -s 'let $doc := <a><b>bla</b></a> return fn:substring($doc/*, 1)'
MAPI = monetdb@localhost:50000
QUERY = let $doc := <a><b>bla</b></a> return fn:substring($doc/*, 1)
ERROR = !type error: no variant of function fn:substring accepts the given argument type(s): string?; integer
!type error: maybe you meant:
!type error: fn:substring (string?, double) as string
!type error: fn:substring (string?, double, double) as string
!type error: illegal arguments for function fn:substring
thanks,
l.
## Comment 10416
Date: 2008-10-08 18:43:52 +0200
From: @drstmane
Lefteris,
could you please check, and get Jan involved, if necessary?
Thanks!
Stefan
## Comment 10417
Date: 2008-11-10 21:49:55 +0100
From: @peterboncz
Hi Jan,
both problems appear to be compiler related, the first obviously in the algebra backend, and the second somewhere in the automatic casting and signature matching in the core part.
The problems seem easy to reproduce - are they also easy to fix?
Peter
## Comment 10418
Date: 2008-11-11 17:49:25 +0100
From: Jan Rittinger <<jan.rittinger>>
I fixed a bug in the type-checking phase (during function overloading some flags were not properly reset). All three test cases now compile again.
## Comment 10419
Date: 2008-11-11 17:57:42 +0100
From: @drstmane
Thanks for the fix, Jan!
Re-opened to remind us that (as usually) we still want to add a test ...
## Comment 10420
Date: 2008-11-18 12:02:03 +0100
From: @drstmane
Test is now indeed available in
pathfinder/tests/BugTracker/Tests/string_substring.SF-2153484.*
## Comment 10421
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2153484 at http://sourceforge.net/support/tracker.php?aid=2153484
| XQ: string() and substring() | https://api.github.com/repos/MonetDB/MonetDB/issues/1850/comments | 0 | 2020-11-30T10:04:05Z | 2024-06-27T11:33:00Z | https://github.com/MonetDB/MonetDB/issues/1850 | 753,336,575 | 1,850 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-08 03:53:01 +0200
From: @lsidir
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-10-13 06:43:20 +0200
## Comment 10408
Date: 2008-10-08 15:53:01 +0200
From: @lsidir
After shredding the attached document2.xml and running the 4 update queries in the attached xquery2.xq file the document gets corrupted.
Update query 3 tries to replace a node with a new one. However it fails to do so, the resulting document has at the end:
<folder name="lsidir">
<bookmark-definition name="Third comment" project="*" shared="true">
<query/>
</bookmark-definition>
</folder>
when it should have:
<folder name="lsidir">
<bookmark-definition name="Third comment" project="*" shared="true">
<query/>
<description>Description One</description>
<note>Note 1</note>
</bookmark-definition>
</folder>
The forth query mess up the document even more, but most notable it makes description and note elements to re-appear with wrong attributes and wrong nesting:
<folder name="lsidir">
<bookmark-definition name="Third comment" project="*" shared="true">
<query/>
<bookmark-definition shared="true" project="*" name="CopyOf Third comment">
<query/>
<description name="Third comment" project="*" shared="true">Description One</description>
<note>Note 1</note>
</bookmark-definition>
</bookmark-definition>
</folder>
the correct output should be:
folder name="lsidir">
<bookmark-definition name="Third comment" project="*" shared="true">
<query/>
<description>Description One</description>
<note>Note 1</note>
</bookmark-definition>
<bookmark-definition shared="true" project="*" name="CopyOf Third comment">
<query/>
<description>Description One</description>
<note>Note 1</note>
</bookmark-definition>
</folder>
## Comment 10409
Date: 2008-10-09 11:44:49 +0200
From: @sjoerdmullender
Fixed.
The problem was indeed the replace query. Internally it first deletes the node being replaced and then inserts the new node. When inserting the new node, it didn't adjust the ancestor sizes since all ancestors now ended with a hole which was created by the deletion, and the check whether the ancestor sizes needed to be adjusted didn't cater for them ending with a hole.
Lefteris can you check the stable output that I provided with the test. The test was added in tests/Update as replacenode-corruption.SF-2153245.
## Comment 10410
Date: 2008-10-09 17:08:27 +0200
From: @sjoerdmullender
Jan, I am assigning this to you since the bug isn't quite fixed yet, and I'm afraid it's in the algebra generation where it goes wrong (i.e. before this gets to UpdateTape).
There are two problems in the algebra generation, one serious, one performance.
The performance problem is that you should use the function get_attr_own to query the ATTR_OWN table. ATTR_OWN consists of a shared and a private part (because of updates), and the shared part has a hash to speed up accesses. The function knows how to deal with this. Direct access to ATTR_OWN does not use the hash.
The real problem is a confusion between PRE numbers and NIDs. This happens in milgen.brg around line 6878 (stable branch). Here is some MIL code that shows what should be generated:
a0003 := select(a0005.fetch (7),oid_nil,oid_nil);
var x := a0003.hmark(0@0).leftfetchjoin(a0005.fetch (8));
a0003 := get_attr_own(ws, mposjoin(a0003.tmark(0@0), x, ws.fetch(PRE_NID)), x);
This should come in place of the line which is actually generated by the referenced code:
a0003 := mvaljoin (a0005.fetch (7), a0005.fetch (8), ws.fetch (ATTR_OWN));
What is done here is to remove the nil values from the PRE table (why are there nils anyway?) and then use mposjoin to look up the PRE values in the PRE_NID table to translate them to NID values.
Note that this fixed code also uses get_attr_own already.
Peter and I don't know how to integrate these changes into milgen.brg.
## Comment 10411
Date: 2008-10-13 16:13:41 +0200
From: Jan Rittinger <<jan.rittinger>>
Sjoerd, I added your proposed fix to the algebra. Please have a look if everything works as expected.
## Comment 10412
Date: 2008-10-13 16:46:25 +0200
From: @sjoerdmullender
The test works now and the code you generate looks a bit like the code I suggested, so I'm happy.
Lefteris, do you want to check this out?
I'm propagating as we speak.
## Comment 10413
Date: 2008-10-13 18:43:20 +0200
From: @lsidir
I checked it also, and also checked the rest of the update tests just to be sure. It looks ok:)
Thank you.
Closing the bug.
## Comment 10414
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2153245 at http://sourceforge.net/support/tracker.php?aid=2153245
| XQ: corrupted document after replace node | https://api.github.com/repos/MonetDB/MonetDB/issues/1849/comments | 0 | 2020-11-30T10:04:02Z | 2024-06-27T11:33:00Z | https://github.com/MonetDB/MonetDB/issues/1849 | 753,336,536 | 1,849 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-03 09:18:10 +0200
From: marspluto <<juntezhang>>
To: @yzchang
Version: -- development
Last updated: 2009-08-06 03:40:52 +0200
## Comment 10397
Date: 2008-10-03 21:18:10 +0200
From: marspluto <<juntezhang>>
I am trying to restore a database that was backed up.
I used the admin GUI, but it is not very stable, likely because of my libxml2 version...
So I am trying to do it directly in the mclient.
The backup seems to be going ok.
$mclient -lx
xquery>import module namespace adm =
"http://monetdb.cwi.nl/XQuery/admin/" at
"/home/xxx/mdb/share/MonetDB/xrpc/admin/admin.xq";
adm:backup("backup1")
more><>
I then delete everything in the current database, which was in my case the collection "KB".
xquery>import module namespace adm =
"http://monetdb.cwi.nl/XQuery/admin/" at
"/home/xxx/mdb/share/MonetDB/xrpc/admin/admin.xq"; adm:del-col("KB")
more><>
Then I try to restore the backed up database. However, I get an error when I try to restore:
import module namespace adm = "http://monetdb.cwi.nl/XQuery/admin/" at
"/home/xxx/mdb/share/MonetDB/xrpc/admin/admin.xq";
adm:restore("backup1", 10)
more><>
ERROR = !ERROR: CMDtj_throw2collection: operation failed.
I noticed that this error was occurring after I was figuring out why a backed up database was not working when importing it on another computer using the Admin GUI (only giving me errors while executing queries). I tried to restore the database on the same computer using the Admin GUI, and it was also not working. So I used the mclient directly, and it gave me that error.
I would like to backup a database. I also would like to share that database with someone else, and share it between computers with different versions of MonetDB.
The sum size of my files is about 1GB, consisting of a few million library records in pretty flat structure.
Thanks,
junte
## Comment 10398
Date: 2008-10-07 11:20:41 +0200
From: @yzchang
Hello Junte,
I tried your query on with the stable version (compiled from cvs source) on a 64bits AMD machine with Fedora 8, but I could not reproduce your problem. Could you please give us more information about
- how did you install monetdb/xquery?
- which OS are you using
- specification of your machine.
Regards,
Jennie
## Comment 10399
Date: 2008-10-15 13:10:56 +0200
From: marspluto <<juntezhang>>
Hi Jennie,
- how did you install monetdb/xquery?
I installed the June release from CVS.
- which OS are you using
Fedora Core 6 (desktop) and FC 9 on the server.
- specification of your machine.
Desktop: Intel D 3GHZ, 2GB main memory, 250GB harddisk.
Server: Quad Core, 16GB main memory, 6x500GB.
If you need more information, let me know.
junte
## Comment 10400
Date: 2009-02-15 21:38:38 +0100
From: @drstmane
Jennie,
since you already tried to reproduce the problem, you you please add a test for it?
Then we can see how it works with the upcoming release ...
Thanks!
## Comment 10401
Date: 2009-02-17 12:39:10 +0100
From: @yzchang
Thanks for the reminder. However, there is no need to add a test for this case, as it is already covered by the admin function tests.
## Comment 10402
Date: 2009-02-17 13:08:43 +0100
From: @drstmane
So, what do the xrpc admin tests say then?
Is this problem reproducible, or does it work as expected?
In the first case, please poin to the failing test the reproduces the problem,
in the latter case, point to the succeeding test and close this one, e.g., with "works for me".
Thanks.
## Comment 10403
Date: 2009-02-17 16:29:32 +0100
From: @yzchang
This case is tested by the test: runtime/xrpc/admin/backup_restore
This test times out om Fedora 8 variants:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.32.d.1-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.0-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.s.1-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.64.32.d.1-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.64.64.d.1-Fedora8/runtime_xrpc_admin/backup_restore.err.00.html
On Windows, it fails with a syntax error
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.32.32.d.1-Windows5.1/runtime_xrpc_admin/db_stats_noxrpc.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/Int.64.32.d.1-Windows5.2/runtime_xrpc_admin/db_stats_noxrpc.err.00.html
These problems are related with the other bug:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2406824&group_id=56967
## Comment 10404
Date: 2009-08-05 13:55:18 +0200
From: @sjoerdmullender
Given that the xrpc/admin tests seem to work (except for order differences on Fedora10, GNU.64.64.d.0), what is the status of this bug?
## Comment 10405
Date: 2009-08-06 15:40:43 +0200
From: @yzchang
The problem is not showing up in the systems currently tested, hence, closing
I think the output is normal, because I get the same output by directly calling pf:documents-unsafe($colname) using MPS and Algebra.
How can I mark the order differences as acceptable?
## Comment 10406
Date: 2009-08-11 11:17:19 +0200
From: @drstmane
The order differences occur only without property checking (i.e., "-d0" instead of "-d1[0]");
hence, I guess they are triggered by some sortedness property only being set with property checking enabled.
There is no (easy) way to make testing ignore the order differences (assuming they are indeed acceptable, i.e., semantically correct).
One solution would be to ensure deterministic order in all cases, i.e., by adding an "order by" ...
## Comment 10407
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2144912 at http://sourceforge.net/support/tracker.php?aid=2144912
| ERROR = !ERROR: CMDtj_throw2collection: operation failed. | https://api.github.com/repos/MonetDB/MonetDB/issues/1848/comments | 0 | 2020-11-30T10:03:58Z | 2024-06-27T11:32:59Z | https://github.com/MonetDB/MonetDB/issues/1848 | 753,336,482 | 1,848 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-03 06:25:27 +0200
From: Loredana Afanasiev <<lafanasi>>
To: Lefteris Sidirourgos <<lsidir>>
Version: -- development
Last updated: 2008-11-14 12:22:20 +0100
## Comment 10382
Date: 2008-10-03 18:25:27 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi Lefteris,
as discussed on Thu, I add this as a bug, so that you can close it soon :)
[lafanasi@zookst4 xq]$ mclient -lx -s 'fn:collection("MotiesTweedeKamer")'
MAPI = monetdb@localhost:50000
QUERY = fn:collection("MotiesTweedeKamer")
ERROR = !fatal error: Algebra implementation for function `fn:collection' unknown.
Thanks,
l.
## Comment 10383
Date: 2008-10-08 15:13:27 +0200
From: Loredana Afanasiev <<lafanasi>>
Subject: fn:collection() vs pf:collection()
Hi Lefteris and all,
I think this relevant to this bug report.
I get huge performance times difference when switching from fn:collection() to pf:collection(). I can you please advise me how to avoid the long times while running on algebra version?
thanks in advance,
l.
[lafanasi@zookst4 xq]$ more q9-fn.xq
let $col := fn:collection("MotiesTweedeKamer")
for $y in distinct-values(for $y in $col//hiddendatum return substring-before(fn:str
ing($y),'.'))
let $thisyear := $col//document
[substring-before(fn:string(.//hiddendatum[1]),'.')=$y]
let $partij := distinct-values($thisyear//partij)
for $p in $partij
let $aantalingediendemoties :=
count($thisyear[.//indienergnlod//partij=$p])
let $aantalmedeingediendemoties :=
count($thisyear[.//medeindienergnlod//partij=$p])
order by $y descending,
$aantalingediendemoties descending,
$aantalmedeingediendemoties descending
return
<aantal jaar='{$y}'
partij='{$p}'
aantalingediendemoties='{$aantalingediendemoties}'
aantalmedeingediendemoties='{$aantalmedeingediendemoties}'
/>
[lafanasi@zookst4 xq]$ mclient -lx -g -t q9-fn.xq
Trans 35.174 msec
Shred 0.000 msec
Query 4401.659 msec
Print 2.680 msec
Timer 4487.610 msec
[lafanasi@zookst4 xq]$ more q9-pf.xq
let $col := pf:collection("MotiesTweedeKamer")
for $y in distinct-values(for $y in $col//hiddendatum return substring-before(fn:str
ing($y),'.'))
let $thisyear := $col//document
[substring-before(fn:string(.//hiddendatum[1]),'.')=$y]
let $partij := distinct-values($thisyear//partij)
for $p in $partij
let $aantalingediendemoties :=
count($thisyear[.//indienergnlod//partij=$p])
let $aantalmedeingediendemoties :=
count($thisyear[.//medeindienergnlod//partij=$p])
order by $y descending,
$aantalingediendemoties descending,
$aantalmedeingediendemoties descending
return
<aantal jaar='{$y}'
partij='{$p}'
aantalingediendemoties='{$aantalingediendemoties}'
aantalmedeingediendemoties='{$aantalmedeingediendemoties}'
/>
[lafanasi@zookst4 xq]$ mclient -lx -t q9-pf.xq
Timer 584185.070 msec
[lafanasi@zookst4 xq]$ diff q9-fn.xq q9-pf.xq
1c1
< let $col := fn:collection("MotiesTweedeKamer")
---
> let $col := pf:collection("MotiesTweedeKamer")
Besides this there is something strange happening with pf:collection(). The website says:
"
pf:collection() returns a single special collection node, whose immediate children are the document nodes. Therefore, fn:collection("my-collection") is roughly equivalent to pf:collection("my-collection")/*.
"
While I get:
[lafanasi@zookst4 xq]$ mclient -lx -g -s 'count(fn:collection("MotiesTweedeKamer"))'
27946
[lafanasi@zookst4 xq]$ mclient -lx -g -s 'count(pf:collection("MotiesTweedeKamer"))'
1
[lafanasi@zookst4 xq]$ mclient -lx -g -s 'count(pf:collection("MotiesTweedeKamer")/*)'
0
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("MotiesTweedeKamer")/*)'
0
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("MotiesTweedeKamer")/*/*)'
0
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("MotiesTweedeKamer")/*/document)'
0
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("MotiesTweedeKamer")//document)'
27946
## Comment 10384
Date: 2008-10-08 15:31:11 +0200
From: @drstmane
Loredana,
(1)
The performance differences you experience are most probably not caused by fn:collection() vs. pf:collection() but by ALG vs. MPS (see also (2)) --- just try MPS with pf:collection() and it should show the same performance as MPS with fn:collection().
(2)
Since MPS and ALG use quite different ways & techniques to translate and optimize queries, it is expected that they show performance differences (sometimes severe ones) on the same query; we (plus the Pathfinder folks in Tübingen) have to check, what goes wrong with ALG in case of your query ...
Thanks for reporting it.
(3)
We also have to check the unexpected(?) behaviour of pf:collection().
Thanks for reporting it.
## Comment 10385
Date: 2008-10-08 15:54:15 +0200
From: @drstmane
It seems as if the return type of pf:collection() is not quite correct: string? instead of node :
========
15:50:43 manegold@rig:/tmp $ mclient -lx -s'pf:collections()'
<collection updatable="false" size="120 MiB" numDocs="27946">MotiesTweedeKamer</collection>,
<collection updatable="true" size="237 MiB" numDocs="27946">MotiesTweedeKamer_Updatable</collection>
15:50:46 manegold@rig:/tmp $ mclient -lx -g -s'pf:collections()'
<collection updatable="false" size="120 MiB" numDocs="27946">MotiesTweedeKamer</collection>,
<collection updatable="true" size="237 MiB" numDocs="27946">MotiesTweedeKamer_Updatable</collection>
15:50:47 manegold@rig:/tmp $ mclient -lx -s'count(pf:collection("MotiesTweedeKamer"))'
1
15:51:01 manegold@rig:/tmp $ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer"))'
1
15:51:06 manegold@rig:/tmp $ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")//document)'
27946
15:51:20 manegold@rig:/tmp $ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer")//document)'
27946
15:51:26 manegold@rig:/tmp $ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/*)'
0
15:51:34 manegold@rig:/tmp $ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer")/*)'
0
15:51:39 manegold@rig:/tmp $ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/*/*)'
0
15:51:44 manegold@rig:/tmp $ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer")/*/*)'
0
15:51:47 manegold@rig:/tmp $ mclient -lx -s'doc(pf:collection("MotiesTweedeKamer")/*)'
MAPI = monetdb@localhost:50000
QUERY = doc(pf:collection("MotiesTweedeKamer")/*)
ERROR = !type error: no variant of function fn:doc accepts the given argument type(s): string?
!type error: maybe you meant:
!type error: fn:doc (string?) as document { node }?
!type error: illegal arguments for function fn:doc
15:51:57 manegold@rig:/tmp $ mclient -lx -g -s'doc(pf:collection("MotiesTweedeKamer")/*)'
MAPI = monetdb@localhost:50000
QUERY = doc(pf:collection("MotiesTweedeKamer")/*)
ERROR = !type error: no variant of function fn:doc accepts the given argument type(s): string?
!type error: maybe you meant:
!type error: fn:doc (string?) as document { node }?
!type error: illegal arguments for function fn:doc
15:52:04 manegold@rig:/tmp $ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/node())'
27946
15:52:13 manegold@rig:/tmp $ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer")/node())'
27946
15:52:18 manegold@rig:/tmp $ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/node()/document)'
27946
15:52:25 manegold@rig:/tmp $ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer")/node()/document)'
27946
========
!??
## Comment 10386
Date: 2008-10-08 16:11:10 +0200
From: @lsidir
The pf:collection returns correctly 1 node. The (string?) error message is misleading here, fn:doc wants a string?, not that pf:collection is giving one. I think what it does not like is the cardinality, since you are giving a *.
## Comment 10387
Date: 2008-10-08 16:26:36 +0200
From: @drstmane
$ mclient -lx -s'count(pf:collection("MotiesTweedeKamer"))'
1
and
$ mclient -lx -g -s'count(pf:collection("MotiesTweedeKamer"))'
1
are indeed correct. no point.
But
$ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/*)'
0
and
$ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/*)'
0
are (at least) "unexpected".
And since
$ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/node())'
27946
and
$ mclient -lx -s'count(pf:collection("MotiesTweedeKamer")/node())'
27946
(mind the "/node()" instead of "/*"!)
appear to work correctly, too,
I tried to find out why the "/*" yields "unexpected" results;
hence, my "layman's" attempt to check the type returned by "pf:collection(<colname>)/*":
$ mclient -lx -s'doc(pf:collection("MotiesTweedeKamer")/*)'
MAPI = monetdb@localhost:50000
QUERY = doc(pf:collection("MotiesTweedeKamer")/*)
ERROR = !type error: no variant of function fn:doc accepts the given argument type(s): string?
!type error: maybe you meant:
!type error: fn:doc (string?) as document { node }?
!type error: illegal arguments for function fn:doc
and
$ mclient -lx -g -s'doc(pf:collection("MotiesTweedeKamer")/*)'
MAPI = monetdb@localhost:50000
QUERY = doc(pf:collection("MotiesTweedeKamer")/*)
ERROR = !type error: no variant of function fn:doc accepts the given argument type(s): string?
!type error: maybe you meant:
!type error: fn:doc (string?) as document { node }?
!type error: illegal arguments for function fn:doc
...
## Comment 10388
Date: 2008-10-08 16:31:06 +0200
From: @drstmane
and here the "proof" that pf:collection() does not cause any performance degradation --- the problem is indeed the ALG translation ...
$ cat q9-fn.xq
let $col := fn:collection("MotiesTweedeKamer")
for $y in distinct-values( for $y in $col//hiddendatum return substring-before(fn:string($y),'.') )
let $thisyear := $col//document[substring-before(fn:string(.//hiddendatum[1]),'.')=$y]
let $partij := distinct-values($thisyear//partij)
for $p in $partij
let $aantalingediendemoties := count($thisyear[.//indienergnlod//partij=$p])
let $aantalmedeingediendemoties := count($thisyear[.//medeindienergnlod//partij=$p])
order by $y descending, $aantalingediendemoties descending, $aantalmedeingediendemoties descending
return
<aantal jaar='{$y}'
partij='{$p}'
aantalingediendemoties='{$aantalingediendemoties}'
aantalmedeingediendemoties='{$aantalmedeingediendemoties}'
/>
$ diff q9-{fn,pf}.xq
1c1
< let $col := fn:collection("MotiesTweedeKamer")
---
> let $col := pf:collection("MotiesTweedeKamer")
$ mclient -t -lx -g q9-fn.xq | grep -v '^<aantal .*/>'
Trans 32.156 msec
Shred 0.000 msec
Query 3272.690 msec
Print 1.598 msec
Timer 3339.119 msec
$ mclient -t -lx -g q9-pf.xq | grep -v '^<aantal .*/>'
Trans 27.816 msec
Shred 0.000 msec
Query 3247.053 msec
Print 1.594 msec
Timer 3308.713 msec
$ mclient -t -lx q9-pf.xq | grep -v '^<aantal .*/>'
[makes Mserver grow >> 13 GB and (hence) runs very long ...]
## Comment 10389
Date: 2008-10-08 23:41:23 +0200
From: Jan Rittinger <<jan.rittinger>>
Answer to 'why does count(pf:collection(...)/*) return 0':
I don't know the behavior of pf:collection but I assume it returns a magical node that sits on top of all root nodes in the collection. If the collection like in Loredanas case only consists of documents the children of the magical node naturally are all document nodes. Thus the element tagname test * does not return any results.
Answer to 'why is there a performance difference between algebra and MPS version':
As always if there is a big difference a join is not detected in the one or other variant. In the stable branch we had to avoid some error message (about running out of column names) and thus are not able to apply all optimizations necessary to detect the value-based join. If you use pf to compile the query you'll see a warning that some optimizations could not be applied.
## Comment 10390
Date: 2008-11-01 20:03:15 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi Jan,
sorry for taking so long..
> pf:collection(...)/*
of course! "*" doesn't cover document nodes. thx!
> performance difference between alg and MPS version
I tried compiling with pf
($pf q9-pf.xq)
but I didn't get any warning message. If you know a way to make this query run faster on the alg version, please let me know.
thanks!
l.
## Comment 10391
Date: 2008-11-02 11:35:16 +0100
From: Jan Rittinger <<jan.rittinger>>
Hi Loredana,
I analyzed the query and it turned out that the incorrect implementation of pf:collection() makes an important rewrite rule to fail. I checked in a fix that makes the rewrite less restrictive and thus leads to a plan where the performance should be acceptable.
For pf:collection and fn:collection probably a new algebra operator like the doc_tbl operator is needed as some rewrite rules rely on the fragment information. Perhaps a variant of fn:doc would do the job...
## Comment 10392
Date: 2008-11-03 17:43:40 +0100
From: Loredana Afanasiev <<lafanasi>>
Hi Jan,
I reinstalled and run the q9 queries again. Now the performance time is around 4644.881 msec for both algebra (pf:collection()) and MPS (fn:collection()) versions. Thanks for the fix!!!
> For pf:collection and fn:collection probably a new algebra operator like
> the doc_tbl operator is needed as some rewrite rules rely on the fragment
> information. Perhaps a variant of fn:doc would do the job...
I dont' follow this fully, so I take it, this is not for my ears. :)
l.
## Comment 10393
Date: 2008-11-13 16:11:30 +0100
From: @lsidir
Hi,
I checked in the development branch a fix for pf:collection. Now, pf:collection uses the doc_tbl operator for better and more correct optimization, as Jan suggested. Also fn:collection is now implemented as pf:collection and a child-step. The checkin is tagged with fn_collection_before and fn_collection_after for easier back porting to the stable branch if Sjoerd chooses to do so.
I changed the resolution to fixed, but not closing the bug yet. Loredana will do some test of her own and also check the new execution times, and I will also wait for the nightly testing.
lefteris
## Comment 10394
Date: 2008-11-14 12:22:14 +0100
From: @lsidir
closing this bug since the nightly testing was successful
## Comment 10395
Date: 2008-11-14 12:46:50 +0100
From: @drstmane
Are there any tests for fn:collection() that are not disabled for the Algebra back-end?
Did you by any chance re-enable tests for the Algebra back-end that were disabled for it because fn:collection() was not (yet) available?
$ find pathfinder/ -type f -name All | xargs grep --color 'NOT_ALGEBRA?'
pathfinder/tests/BugTracker/Tests/All:NOT_ALGEBRA?pfmil_prints_garbage.SF-2015232
pathfinder/tests/BugTracker/Tests/All:NOT_ALGEBRA?pfmil_loses_last_bun.SF-2015219
pathfinder/tests/BugTracker/Tests/All:NOT_ALGEBRA?pfmil_and_nil_in_results_1.SF-2015135
pathfinder/tests/BugTracker/Tests/All:NOT_ALGEBRA?pfmil_and_nil_in_results_2.SF-2015135
pathfinder/tests/BugTracker/Tests/All:NOT_ALGEBRA?fn_collection_after_delete.SF-2141000
I'll re-enable the fn_collection_after_delete.SF-2141000 test (also) for the Algebra version and enclose the changes in your fn_collection_before and fn_collection_after tags.
## Comment 10396
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2144639 at http://sourceforge.net/support/tracker.php?aid=2144639
| XQ: fn:collection() in algebra version | https://api.github.com/repos/MonetDB/MonetDB/issues/1847/comments | 0 | 2020-11-30T10:03:55Z | 2024-06-27T11:32:58Z | https://github.com/MonetDB/MonetDB/issues/1847 | 753,336,430 | 1,847 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-03 01:12:39 +0200
From: @drstmane
To: Fabian Groffen <<fabian>>
Version: -- development
Last updated: 2008-10-28 01:44:04 +0100
## Comment 10376
Date: 2008-10-03 13:12:39 +0200
From: @drstmane
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/The-JDBC-Library.htmlThe-JDBC-Library
contains outdated and incomplete documentation about the MonetDB/JDBC driver:
JDBC is no longer located in (and hence built with) the SQL modules, but it is now (has been for some time) in the (new) Java module.
To compiler, JDBC indeed requires at least Java 1.4, but also at most Java 1.5 (Java 1.6 and newer does not work).
## Comment 10377
Date: 2008-10-07 16:42:21 +0200
From: @sjoerdmullender
Assigned to Fabian.
## Comment 10378
Date: 2008-10-28 10:47:45 +0100
From: @grobian
I can't find where it comes from since it is generated. It's hard to fix that way.
## Comment 10379
Date: 2008-10-28 11:15:57 +0100
From: @drstmane
$ find monetweb -type f | xargs grep --color 'MonetDB JDBC Driver' 2>/dev/null
monetweb/Docs/MonetDB/jdbcmanual.texi:@section MonetDB JDBC Driver
## Comment 10380
Date: 2008-10-28 13:44:04 +0100
From: @grobian
thanks, cleaned up that piece of text.
## Comment 10381
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2144123 at http://sourceforge.net/support/tracker.php?aid=2144123
| Web: outdated Java/JDBC documentation | https://api.github.com/repos/MonetDB/MonetDB/issues/1846/comments | 0 | 2020-11-30T10:03:52Z | 2024-06-27T11:32:57Z | https://github.com/MonetDB/MonetDB/issues/1846 | 753,336,392 | 1,846 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-03 11:06:20 +0200
From: @mlkersten
To: @mlkersten
Version: -- development
Last updated: 2009-07-20 09:17:20 +0200
## Comment 10371
Date: 2008-10-03 11:06:20 +0200
From: @mlkersten
Documentation is broken
http://monetdb.cwi.nl/projects/monetdb/SQL/Documentation/Embedded-Server.htmlEmbedded-Server
## Comment 10372
Date: 2008-10-10 15:31:41 +0200
From: @sjoerdmullender
The embedded servers now all work and the web page source has been updated.
Martin, can you check?
## Comment 10373
Date: 2009-02-15 21:40:08 +0100
From: @drstmane
Martin,
could you please check, whether the documentation is correct, now?
Thanks!
Stefan
## Comment 10374
Date: 2009-07-20 21:17:20 +0200
From: @mlkersten
This seems been fixed since. (modulo content checks)
## Comment 10375
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2143956 at http://sourceforge.net/support/tracker.php?aid=2143956
| SQL: embedded applications | https://api.github.com/repos/MonetDB/MonetDB/issues/1845/comments | 0 | 2020-11-30T10:03:49Z | 2024-06-27T11:32:56Z | https://github.com/MonetDB/MonetDB/issues/1845 | 753,336,349 | 1,845 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-02 04:28:44 +0200
From: Floris Ouwendijk <<floris233>>
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-17 10:07:28 +0100
## Comment 10364
Date: 2008-10-02 16:28:44 +0200
From: Floris Ouwendijk <<floris233>>
We've found a bug that causes results to be returned multiple times.
I've been able to reduce the data and query to manageable proportions, see files below.
When you run the xquery script, it will return 8, while 4 is expected.
If the lines in the result that are commented are included, the correct result is given, while all they do is count the number of items produced in intermediary stages.
<testd>
<test a="1"><sub1/><sub2/></test>
<test a="1"><sub1/><sub2/></test>
<test a="1" b="1"><sub1/><sub2/></test>
<test a="1" b="1"><sub1/><sub2/></test>
<test b="1"><sub1/><sub2/></test>
<test b="1"><sub1/><sub2/></test>
<test><sub1/><sub2/></test>
<test><sub1/><sub2/></test>
</testd>
let $input1 := (doc("file:///path_to_test_xml")//test)
let $hits1 := (doc("file:///path_to_test_xml")//test[@a])
let $input2 := ($input1 intersect $hits1)
let $input3 := for $raw in $input2 where not(empty(for $t in $raw//* return $t)) return $raw
let $hits3 := (doc("file:///path_to_test_xml")//test[@a])
let $result := ($input3 intersect $hits3)
return element result {
(:element input1 {count($input1)} ,
element hits1 {count($hits1)} ,
element input2 {count($input2)} ,
element input3 {count($input3)} ,
element hits3 {count($hits3)} ,:)
element result {count($result)}
}
## Comment 10365
Date: 2008-10-03 13:17:51 +0200
From: @sjoerdmullender
Added test tests/BugTracker/Tests/duplicates_error.SF-2142522.
## Comment 10366
Date: 2008-11-10 21:53:47 +0100
From: @peterboncz
Hi Lefteris,
Maybe have a short look at this one. It is quite likely that Jan will have to look at it..
Peter
## Comment 10367
Date: 2008-11-12 11:44:51 +0100
From: Jan Rittinger <<jan.rittinger>>
found the problem (incorrect property inference for intersect) -- as soon as I'm allowed to check in again I will fix it.
## Comment 10368
Date: 2008-11-15 22:31:51 +0100
From: Jan Rittinger <<jan.rittinger>>
Fix committed and test added.
## Comment 10369
Date: 2008-11-18 12:03:21 +0100
From: @drstmane
Tests are available in
pathfinder/tests/BugTracker/Tests/duplicates_error.SF-2142522.*
and
pathfinder/tests/BugTracker/Tests/intersect_duplicates.SF-2142522.*
(!?)
## Comment 10370
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2142522 at http://sourceforge.net/support/tracker.php?aid=2142522
| XQ: Duplicates when not using intermediate result | https://api.github.com/repos/MonetDB/MonetDB/issues/1844/comments | 0 | 2020-11-30T10:03:46Z | 2024-06-27T11:32:55Z | https://github.com/MonetDB/MonetDB/issues/1844 | 753,336,300 | 1,844 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-01 10:13:45 +0200
From: Loredana Afanasiev <<lafanasi>>
To: @sjoerdmullender
Version: -- development
Last updated: 2009-04-08 11:19:55 +0200
## Comment 10344
Date: 2008-10-01 22:13:45 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi,
I have two identical in content collections, but one is read only the other is updatable. I have two queries, which are identical with the exception of one line that indicates the queried collection. Query 1 retrieves results, query 2 produces the error. I don't have any good guesses why..
[lafanasi@zookst4 xq]$ diff tmp1.xq tmp2.xq
1c1
< let $col := fn:collection("MotiesTweedeKamer")
---
> let $col := fn:collection("MotiesTweedeKamer_Updatable")
[lafanasi@zookst4 xq]$ mclient -lx -g tmp1.xq
<result count="1" year=""/>,
...
lafanasi@zookst4 xq]$ mclient -lx -g tmp2.xq
MAPI = monetdb@localhost:50000
QUERY = let $col := fn:collection("MotiesTweedeKamer_Updatable")
ERROR = !ERROR: err:FORG0003: function fn:zero-or-one expects at most one value.
cheers,
l.
## Comment 10345
Date: 2008-10-01 22:50:48 +0200
From: @drstmane
Loredana,
could you please provide us with (e.g., attach) the complete queries, and possible also with (access to) the document collections you are using?
Thanks in advance!
Stefan
## Comment 10346
Date: 2008-10-03 18:49:09 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi Stefan,
here's the data:
http://staff.science.uva.nl/~lafanasi/data.tgz
and the queries are:
::::::::::::::
tmp1.xq
::::::::::::::
let $col := fn:collection("MotiesTweedeKamer")
let $years := fn:distinct-values(
for $date in $col//hiddendatum
return fn:substring(fn:string($date),1,4))
for $y in $years
order by $y ascending
return <result year="{$y}" count="{
count($col//document[fn:substring(fn:string(.//hiddendatum),1,4) = $y])}"/>
::::::::::::::
tmp2.xq
::::::::::::::
let $col := fn:collection("MotiesTweedeKamer_Updatable")
let $years := fn:distinct-values(
for $date in $col//hiddendatum
return fn:substring(fn:string($date),1,4))
for $y in $years
order by $y ascending
return <result year="{$y}" count="{
count($col//document[fn:substring(fn:string(.//hiddendatum),1,4) = $y])}"/>
Thanks,
l.
## Comment 10347
Date: 2008-10-07 17:36:45 +0200
From: @sjoerdmullender
I can reproduce the error in the development version after I loaded all data. I didn't try the stable version (yet).
## Comment 10348
Date: 2008-12-09 00:46:20 +0100
From: @peterboncz
I did:
$ ls | wc
27946 27946 335352
$ ls *xml | awk 'BEGIN { print "<a>"} { printf "<b p=\"/export/scratch0/boncz/bug/XML/%s\" f=\"%s\"/>\n", $1, $1 } END { print "</a>" }' > /tmp/g.xml
Then I see that in algebra mode, fn:collection() returns the wrong count for the updatable collection:
more>for $d in doc("/tmp/g.xml")//b return pf:add-doc(exactly-one($d/@p), exactly-one($d/@f), "rdonly")
more><>
xquery>count(fn:collection("rdonly"))
more><>
27946
xquery>for $d in doc("/tmp/g.xml")//b return pf:add-doc(exactly-one($d/@p), concat(exactly-one($d/@f),"_"), "wr", 10)
more><>
xquery>count(fn:collection("wr"))
more><>
28012
That is, the child step does not work correctly from the pf:collection() node:
xquery>count(pf:collection("wr")/child::text())
more><>
42
xquery>count(pf:collection("wr")/child::attribute())
more><>
0
xquery>count(pf:collection("wr")/child::element())
more><>
38
xquery>count(pf:collection("wr")/child::node())
more><>
28012
(this holds for both mps and alg)
Funny thing is that 27946 + 38 + 42 = 28026, not 28012 ???
I think the child step should be fixed to properly support the collection node...
## Comment 10349
Date: 2008-12-11 23:56:49 +0100
From: @peterboncz
Stefan: I also asked Lefteris to look at this, but the problem here is that the child staircase join does not handle NIL tuples that occur in updatable documents.
It should ignore these, and filter them out.. Could you maybe help?
## Comment 10350
Date: 2008-12-12 01:10:35 +0100
From: Loredana Afanasiev <<lafanasi>>
I also bumped the problem with counting:
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("HAN")/node())'
19820
(this is the real collection size)
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("HAN_Updatable")/*)'
48
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("HAN_Updatable")/node())'
19904
[lafanasi@zookst4 xq]$ mclient -lx -s 'count(pf:collection("HAN_Updatable")/node()/*)'
19906
## Comment 10351
Date: 2008-12-12 12:37:53 +0100
From: @drstmane
There might of course be a place in the ll_child implementation where I forgot to put a check for holes (i.e., highest bit of size value is set...
What I recall is that ll_child and ll_descendant (may be other ll steps as well) assume that they do receive "sound" and "sane" context sets as input, i.e., the context sets only contain real (existing) nodes with valid sizes, but (obviously?) not entries that point to holes ...
## Comment 10352
Date: 2008-12-12 18:20:10 +0100
From: @drstmane
After an exhaustive (and -ing) debugging session with combined forces of Lefteris, Sjoerd and Stefan, we found that the problem is not in the staircase join code, but rather in the shredder that seems to not properly handle the (admittedly rare, but apparently not impossible) case that one shredded document happens to end just before a hole on a page, and the next (to be) shredded document hence begins on a new virgin page.
PRE table
-------------------------------------------------------------------------------------------------------------------------
pre nid size level prop kind tag cont name
void oid int chr oid str str oid type
-------------------------------------------------------------------------------------------------------------------------
...
Begin of document (15792th document in this case) that happens to end just before the supposed hole starts:
[ 4176025@0, 3759973@0, 0, '\001', 0@0, "TEXT", nil, 1@0 ]
[ 4176026@0, 3759974@0, 1893, 'ÿ', nil, "DOCUMENT", nil, 1@0 ]
[ 4176027@0, 3759975@0, 1892, '\000', 0@0, "ELEMENT", "||document", 1@0 ]
[ 4176028@0, 3759976@0, 0, '\001', 0@0, "TEXT", nil, 1@0 ]
...
End of that document and start of the next one (15792th document in this case) --- inside the hole instead of on the next page:
[ 4176280@0, 3760228@0, 0, '\002', 119205@0, "TEXT", nil, 1@0 ]
[ 4176281@0, 3760229@0, 1638, '\001', 0@0, "TEXT", nil, 1@0 ]
[ 4176282@0, 3760230@0, 284, 'ÿ', nil, "DOCUMENT", nil, 1@0 ]
[ 4176283@0, 3760231@0, 283, '\000', 0@0, "ELEMENT", "||document", 1@0 ]
[ 4176284@0, 3760232@0, 0, '\001', 0@0, "TEXT", nil, 1@0 ]
...
Next page boundary:
[ 4177919@0, 3761867@0, 0, '\003', 0@0, "TEXT", nil, 1@0 ]
[ 4177920@0, 3761868@0, 2, '\003', 38@0, "ELEMENT", "||actie", 1@0 ]
Re-assigning to the "Mr. shredder": Jan Flokstra.
## Comment 10353
Date: 2008-12-15 14:33:16 +0100
From: Jan Flokstra <<jflokstra>>
I tried to fix it in the shredder but I'm not shure if it fixes the problem. The update code is pretty hairy and a lot of people having been changing things since I last had a look at it. I now check before I start shredding if the pre is in a hole and when this is the case I create a proper hole and make the next pre the first pre after the new hole.Because of the experimental character I checked it in in "Current". When I get reports it fixes the problem I will properly do the fix in Stable,
JanF.
## Comment 10354
Date: 2008-12-15 14:33:59 +0100
From: Jan Flokstra <<jflokstra>>
I tried to fix it in the shredder but I'm not shure if it fixes the problem. The update code is pretty hairy and a lot of people having been changing things since I last had a look at it. I now check before I start shredding if the pre is in a hole and when this is the case I create a proper hole and make the next pre the first pre after the new hole.Because of the experimental character I checked it in in "Current". When I get reports it fixes the problem I will properly do the fix in Stable,
JanF.
## Comment 10355
Date: 2008-12-15 14:58:58 +0100
From: @drstmane
Jan F.,
thanks for the attempt to fix the problem.
The report should contain enough information to test whether the fix does work.
Loredana, Lefteris,
assuming that you do have a setup ready where you can easily check Jan's fix, could you please do so, too, and report here?
Thank you all in advance!
Stefan
## Comment 10356
Date: 2008-12-15 15:22:36 +0100
From: @drstmane
Jan F.,
once/if you fix this properly in the Nov2008 release branch, please recall to also undo your preliminary fix the development trunk to avoid conflicts during (semi-)automa[gnt]ic propagation.
Thanks!
Stefan
## Comment 10357
Date: 2008-12-15 18:39:34 +0100
From: @sjoerdmullender
As discussed in the PF skype meeting, I tried fixing this bug in the stable branch.
## Comment 10358
Date: 2008-12-18 15:23:30 +0100
From: @lsidir
After the last check-in in the stable branch from Sjoerd the problem seems to be solved.
## Comment 10359
Date: 2008-12-18 15:29:41 +0100
From: @sjoerdmullender
A test was added that tests the specific thing that went wrong: tests/BugTracker 1pagedoc.SF-2141012.
Closing as fixed.
## Comment 10360
Date: 2009-02-16 01:06:30 +0100
From: @drstmane
re-opened as the test triggers a BATfetchjoin error with boh ALG & MPS:
ERROR = !ERROR: BATfetchjoin(tmp_32127,tmp_31766) does not hit always (|bn|=0 != 1=|l|) => can't use fetchjoin.
!ERROR: CMDleftfetchjoin: operation failed.
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTests103/GNU.64.64.d.1-Fedora8/tests_BugTracker/1pagedoc.SF-2141012.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/pathfinder/.mTestsg103/GNU.64.64.d.1-Fedora8/tests_BugTracker/1pagedoc.SF-2141012.err.00.html
## Comment 10361
Date: 2009-04-07 18:03:59 +0200
From: @sjoerdmullender
The current error looks like a document management bug.
The test first creates a collection with 6 documents. It then, in a single query, queries several of the documents. Due to the way this is translated, the documents being queried are opened one at a time. When the first of the queried documents is opened (doc_tbl() calls ws_opendoc), the whole collection is necessarily loaded. The document names are added to ws[OPEN_NAME], but, and here is the problem, apparently *not* to ws[OPEN_DOCID]. When the second document is queried in the same query, the document is found in ws[OPEN_NAME] and this is then joined (using leftfetchjoin) with ws[OPEN_DOCID] where the document is missing. Hence the error.
The reason why the documents aren't added to ws[OPEN_DOCID] seems to be because the values in the docpre_nme variable in ws_docfilter() don't match the values in ws[FRAG_ROOT], and so the join that is done between these two doesn't hit the documents, so they don't get added. Perhaps this has to do with the way the documents were constructed: they were constructed to occupy exactly one page when shredded with 10% slack space.
I printed the values of docpre_nme and ws[FRAG_ROOT] in ws_docfilter() when the first document is opened:
-----------------------------------------
h t name
oid str type
-----------------------------------------
[ 1@0, "1pagedoc-1.xml" ]
[ 16384@0, "1pagedoc-2.xml" ]
[ 31129@0, "1pagedoc-3.xml" ]
[ 47512@0, "1pagedoc-4.xml" ]
[ 63895@0, "1pagedoc-5.xml" ]
---------------------------------
h t name
oid oid type
---------------------------------
[ 1000000000@0, 1@0 ]
[ 1000000001@0, 14746@0 ]
[ 1000000002@0, 29491@0 ]
[ 1000000003@0, 44236@0 ]
[ 1000000004@0, 58981@0 ]
[ 1000000005@0, 73726@0 ]
## Comment 10362
Date: 2009-04-08 11:19:55 +0200
From: @sjoerdmullender
Fixed.
ws_docfilter adds the extra documents that were read because another document in the collection is opened to the working set. It did a join between a table with the PRE numbers of the roots of those documents with the FRAG_ROOT table. However, the latter contains NID numbers, so a conversion from NID to PRE was needed. This conversion was missing.
## Comment 10363
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2141012 at http://sourceforge.net/support/tracker.php?aid=2141012
| XQ: unclear error | https://api.github.com/repos/MonetDB/MonetDB/issues/1843/comments | 0 | 2020-11-30T10:03:42Z | 2024-06-27T11:32:54Z | https://github.com/MonetDB/MonetDB/issues/1843 | 753,336,259 | 1,843 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-01 10:05:02 +0200
From: Loredana Afanasiev <<lafanasi>>
To: @sjoerdmullender
Version: -- development
Last updated: 2008-10-10 05:50:18 +0200
## Comment 10337
Date: 2008-10-01 22:05:02 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi,
Deleting a document from a collection seems to be buggy, see the following sequence of steps:
bulk-loading a collection
xquery$
for $d in doc("/scratch/PolitiekeData/MotiesTweedeKamer/xq/dir.xml")//doc
return
pf:add-doc(fn:concat("/scratch/PolitiekeData/MotiesTweedeKamer/XML/",$d/@name), fn:string($d/@name), "MotiesTweedeKamer", 0)
adding a document to the collection, by mistake
xquery$
pf:add-doc(fn:concat("/scratch/PolitiekeData/MotiesTweedeKamer/","allemoties.xml"),"MotiesTweedeKamer")
noticed the mistake
xquery$ pf:collections()
<collection updatable="false" size="217 MiB" numDocs="27947">MotiesTweedeKamer</collection>,
delete the document from the collection
xquery$ pf:del-doc("MotiesTweedeKamer")
now, is this doc deleted? The number of document in the collection indeed decreased with one, but then the size of the collection is the same.
xquery$ pf:collections()
<collection updatable="false" size="217 MiB" numDocs="27946">MotiesTweedeKamer</collection>,
lets' test it again. oops.
xquery$ fn:count(fn:collection("MotiesTweedeKamer")//document)
55892
:) I am sure there is a quicker way to getting this bug.
cheers,
l.
## Comment 10338
Date: 2008-10-01 22:56:30 +0200
From: @drstmane
Loredana,
the (physical) size of the collection remains the same after deleting a single document as it would be too expensive to "clean-up" the physical storage, which would require copying the whole collection.
The deleted document should (logically) not be visible anymore, though, and that seems to be correct given the values of the "numDoc" attribute in the results of both pf:collections() calls.
Not knowing your collection I cannot interpret what you last query is supposed to show --- I only see that 55892 = 2 * 27946 ...
Moreover which version of MonetDB/XQuery (resp. Pathfinder) are you using?
You did not indicate that via the "Group:" selection in the header of this bug report.
Stefan
## Comment 10339
Date: 2008-10-02 12:37:07 +0200
From: Loredana Afanasiev <<lafanasi>>
Forgot to say:
Installation packadge: MonetDB-Aug2008-SuperBall.tar.bz2
## Comment 10340
Date: 2008-10-03 18:41:52 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi Stefan,
thanks for the reply.
> Not knowing your collection I cannot interpret what you last query is supposed to show --- I only see that 55892 = 2 * 27946 ...
Right. My collection contains 27946 documents each having "document" as root. I created one big document that lists all these docs under a new root "moties" and added it to the initial collection. Now there are 55892 "document" elements in the collection. Then I delete the big document. There should be 27946 "document" elements in the collection, but there are still 55892 "document" elements.
> Moreover which version of MonetDB/XQuery (resp. Pathfinder) are you
using? You did not indicate that via the "Group:" selection in the header of this
bug report.
done.
## Comment 10341
Date: 2008-10-03 19:01:11 +0200
From: @drstmane
While fn:collection() in the (old and deprecated) MPS back-end indeed seems to be broken (fn:collection() is not yet available in the new ALGebra back-end),
pf:collection() appears to be working correctly in both the MPS and the ALGebra back-end:
$ mclient -lx -s'pf:collections()'
$ cat /tmp/x.xml
<a>
<b/>
</a>
$ mclient -lx -s'pf:add-doc("/tmp/x.xml","MyDoc1","MyColl")'
$ mclient -lx -s'pf:collections()'
<collection updatable="false" size="100 KiB" numDocs="1">MyColl</collection>
$ mclient -lx -s'pf:add-doc("/tmp/x.xml","MyDoc2","MyColl")'
$ mclient -lx -s'pf:collections()'
<collection updatable="false" size="100 KiB" numDocs="2">MyColl</collection>
$ mclient -lx -s'pf:add-doc("/tmp/x.xml","MyDoc3","MyColl")'
$ mclient -lx -s'pf:collections()'
<collection updatable="false" size="100 KiB" numDocs="3">MyColl</collection>
$ mclient -lx -g -s'fn:count(fn:collection("MyColl")//a)'
3
$ mclient -lx -g -s'fn:count(fn:collection("MyColl")//b)'
3
$ mclient -lx -g -s'fn:count(pf:collection("MyColl")//a)'
3
$ mclient -lx -g -s'fn:count(pf:collection("MyColl")//b)'
3
$ mclient -lx -s'fn:count(pf:collection("MyColl")//a)'
3
$ mclient -lx -s'fn:count(pf:collection("MyColl")//b)'
3
$ mclient -lx -s'pf:del-doc("MyDoc3")'
$ mclient -lx -s'pf:collections()'
<collection updatable="false" size="100 KiB" numDocs="2">MyColl</collection>
$ mclient -lx -g -s'fn:count(fn:collection("MyColl")//a)'
3 ! WRONG -> Should be 2 !
$ mclient -lx -g -s'fn:count(fn:collection("MyColl")//b)'
3 ! WRONG -> Should be 2 !
$ mclient -lx -s'fn:count(pf:collection("MyColl")//a)'
2
$ mclient -lx -s'fn:count(pf:collection("MyColl")//b)'
2
$ mclient -lx -g -s'fn:count(pf:collection("MyColl")//a)'
2
$ mclient -lx -g -s'fn:count(pf:collection("MyColl")//b)'
2
Hence, for now, simply use pf:collection().
For details, see also
http://monetdb.cwi.nl/projects/monetdb/Development/Releases/Version4.24/index.htmlXQuery
http://monetdb.cwi.nl/projects/monetdb/XQuery/QuickTour/DOCMGT/index.htmlopenall
http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/Separate-Documents-vs-Document-Collections.html
http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/Metadata-Functions.html
http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/The-Collection-Node.html
## Comment 10342
Date: 2008-10-10 17:50:18 +0200
From: @sjoerdmullender
Fixed fn:collection() in CVS.
Test added as tests/BugTracker fn_collection_after_delete.SF-2141000.
## Comment 10343
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2141000 at http://sourceforge.net/support/tracker.php?aid=2141000
| XQ: fn:collection() broken in MPS back-end | https://api.github.com/repos/MonetDB/MonetDB/issues/1842/comments | 0 | 2020-11-30T10:03:38Z | 2024-06-27T11:32:53Z | https://github.com/MonetDB/MonetDB/issues/1842 | 753,336,215 | 1,842 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-10-01 10:01:49 +0200
From: Loredana Afanasiev <<lafanasi>>
To: XQuery devs <<bugs-xquery>>
Version: -- development
Last updated: 2008-10-03 06:26:24 +0200
## Comment 10333
Date: 2008-10-01 22:01:49 +0200
From: Loredana Afanasiev <<lafanasi>>
[lafanasi@zookst4 xq]$ less q8.xq
for $x in (2,1,3)
for $y in (20,10,30)
order by $x,$y
return <p>{($x,$y)}</p>
Non-algebra version:
[lafanasi@zookst4 xq]$ mclient -lx -g q8.xq
<p>2 10</p>,
<p>2 20</p>,
<p>2 30</p>,
<p>1 10</p>,
<p>1 20</p>,
<p>1 30</p>,
<p>3 10</p>,
<p>3 20</p>,
<p>3 30</p>
Algebra version:
[lafanasi@zookst4 xq]$ mclient -lx q8.xq
<p>1 10</p>,
<p>1 20</p>,
<p>1 30</p>,
<p>2 10</p>,
<p>2 20</p>,
<p>2 30</p>,
<p>3 10</p>,
<p>3 20</p>,
<p>3 30</p>
## Comment 10334
Date: 2008-10-01 22:44:08 +0200
From: @drstmane
Loredana,
given that the non-algebra ("milprint_summer") back-end is deprecated, I'm not sure whether there is much hope that this bug will be fixed. Citing Peter's comment from
https://sourceforge.net/tracker/index.php?func=detail&aid=1835745&group_id=56967&atid=482468
"
nested order by in milprint-summer is buggy (see some W3C tests that have
been failing for a long time).
this will not be fixed. the algebra backend does not have these problems.
".
How "severe" is this problem for you?
Could you move to the (new & default) Algebra back-end, instead?
Stefan
## Comment 10335
Date: 2008-10-04 09:49:55 +0200
From: @drstmane
Just for completeness:
added test in pathfinder/tests/BugTracker/Tests/order_by.SF-2140992.*
## Comment 10336
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2140992 at http://sourceforge.net/support/tracker.php?aid=2140992
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: "order by" doesn't work in the non-algebra version | https://api.github.com/repos/MonetDB/MonetDB/issues/1841/comments | 0 | 2020-11-30T10:03:34Z | 2024-06-28T07:37:06Z | https://github.com/MonetDB/MonetDB/issues/1841 | 753,336,172 | 1,841 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-30 03:18:51 +0200
From: Andrew Volkov <<andriiv>>
To: @njnes
Version: -- development
Last updated: 2009-11-22 10:11:57 +0100
## Comment 10326
Date: 2008-09-30 15:18:51 +0200
From: Andrew Volkov <<andriiv>>
While executing count(*) on 130M table with 2 int columns the following FATAL error occurs and server exits.
!FATAL: GDKmallocmax: failed for 531804336 bytes
OS Vista: 32bit [Version 6.0.6001]
MonetDB server v5.6.0, based on kernel v1.24.0
Serving database 'demo'
Compiled for i686-pc-win32/32bit with 32bit OIDs dynamically linked
## Comment 10327
Date: 2008-10-03 11:09:36 +0200
From: @mlkersten
Can you be more precise on the SQL query
and what was in the table, e.g. unique
numbers or not?
## Comment 10328
Date: 2008-10-03 15:10:57 +0200
From: Andrew Volkov <<andriiv>>
table is type(int), val(int).
table has 130M rows, and 20K unique types
select count(distinct type) from voc.test crashes the db.
even count(*) is pretty fast (less than 0.5sec), count (type) or count(val) take almost 10 seconds (could be memory related).
any query with math function on column type kill DB as well, e.g. select type, avg(val) as m_val from voc.test group by type order by m_val desc
below is the out from memory debugger. before dying the DB stops at the last line and then eventually crashes.
GDKmemchk (memcur=48,memmax=2616192040) (vmcur=0,vmmax=1610612736)
GDKmemchk (memcur=317568,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=369832,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
MonetDB server v5.6.0, based on kernel v1.24.0
Serving database 'demo'
Compiled for i686-pc-win32/32bit with 32bit OIDs dynamically linked
Copyright (c) 1993-2008 CWI, all rights reserved
Visit http://monetdb.cwi.nl/ for further information
warning: please don't forget to set your vault key!
(see C:\Program Files\CWI\MonetDB5\etc\monetdb5.conf)
GDKmemchk (memcur=578680,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=647968,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=714296,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=775376,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=837296,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=903256,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=968128,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1029128,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1090064,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1151032,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1213208,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1275368,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1337832,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1399824,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1462624,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1524704,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1590216,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1648960,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1707368,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1767912,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1833392,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1894584,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=1962648,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2025656,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2091040,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2150824,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2210368,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2270056,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2329544,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2389352,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2449136,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2509760,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2568200,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2626032,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2683640,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2744696,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2804824,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2865808,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2930408,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=2997192,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3062952,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3125224,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3188840,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3253712,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3307232,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3367648,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3428640,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3497240,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3563000,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3629472,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3684584,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3738712,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3793568,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3847784,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3902296,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=3957008,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4016088,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
Listening for connection requests on mapi:monetdb://127.0.0.1:50000/
GDKmemchk (memcur=4096088,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4154928,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4213336,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4271696,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4329744,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
MonetDB/SQL module v2.24.0 loaded
>GDKmemchk (memcur=4408568,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4628400,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4651584,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4674056,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4696528,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4719032,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4741528,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4764184,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4786816,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4809528,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4832352,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4856208,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=4906288,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=5337968,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=6067880,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=6559160,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=7016184,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=7469688,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=8096960,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=8622248,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=9145864,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=9699744,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=10141080,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=10578680,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=11040408,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=11483680,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=11920696,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
GDKmemchk (memcur=12139920,memmax=2616192040) (vmcur=58720256,vmmax=1610612736)
!FATAL: GDKmallocmax: failed for 531804336 bytes
## Comment 10329
Date: 2008-10-07 13:37:36 +0200
From: @njnes
Your running on a 32bit windows system. Could you also tell us the amount of memory in it? The server stops because it cannot allocate .5G. It will need .5 per column so a distinct will require a hash table which does need 1G in this case. So 1.5G is taken.
## Comment 10330
Date: 2009-08-14 14:09:32 +0200
From: @drstmane
tagged subject
## Comment 10331
Date: 2009-11-22 22:11:57 +0100
From: @njnes
out of memory (on 32 bit system). we are working to improve this situation. A small test for this bug seems impossible
## Comment 10332
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2138231 at http://sourceforge.net/support/tracker.php?aid=2138231
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| SQL server exits (FATAL) while performing count(*) operation | https://api.github.com/repos/MonetDB/MonetDB/issues/1840/comments | 0 | 2020-11-30T10:03:31Z | 2024-06-28T07:37:06Z | https://github.com/MonetDB/MonetDB/issues/1840 | 753,336,126 | 1,840 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-28 07:59:08 +0200
From: @skinkie
To: @njnes
Version: -- development
Last updated: 2008-10-21 02:38:16 +0200
## Comment 10312
Date: 2008-09-28 19:59:08 +0200
From: @skinkie
1) It is not the latest monetdb CVS version
2) If you cannot reproduce it I'll upgrade later
select w1.wayid from way_tags as w1, way_tags as w2 where w1.wayid=w2.wayid and w1.k='bridge' and w2.k<>'layers';
or
select * from way_tags as w1, way_tags as w2 where w1.k = 'bridge' and w1.wayid = w2.wayid;
Result in:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x43a56950 (LWP 6885)]
0x00007fc6f55fc969 in CMD_EQ_oid (ret=0x2b73688, l=0x2b73668, r=0x2b73678)
at ../../../../src/modules/kernel/batcalc.mx:1112
1112 *o = (*p @2 *t);
(gdb) bt
0 0x00007fc6f55fc969 in CMD_EQ_oid (ret=0x2b73688, l=0x2b73668, r=0x2b73678)
at ../../../../src/modules/kernel/batcalc.mx:1112
1 0x00007fc7018ebfd5 in DFLOWstep (t=0x2baaa78, fs=0x41618298)
at ../../../src/mal/mal_interpreter.mx:1523
2 0x00007fc7018f0610 in runDFLOWworker (t=0x2baaa78)
at ../../../src/mal/mal_interpreter.mx:810
3 0x00007fc6ffdc9067 in start_thread () from /lib/libpthread.so.0
4 0x00007fc6fef03edd in clone () from /lib/libc.so.6
5 0x0000000000000000 in ?? ()
## Comment 10313
Date: 2008-10-07 13:38:35 +0200
From: @njnes
please add the full sql (create table statements).
## Comment 10314
Date: 2008-10-07 14:16:48 +0200
From: @skinkie
What do you want me to add here? The full openstreetmap dataset, the table description?
sql>\d ways
CREATE TABLE "sys"."ways" (
"id" int NOT NULL DEFAULT next value for "sys"."seq_3903",
"username" varchar(255),
"timestamp" timestamptz(7),
CONSTRAINT "ways_id_pkey" PRIMARY KEY ("id")
);
sql>\d way_tags
CREATE TABLE "sys"."way_tags" (
"way" int NOT NULL,
"k" varchar(255) NOT NULL,
"v" varchar(1024),
CONSTRAINT "way_tags_way_k_pkey" PRIMARY KEY ("way", "k"),
CONSTRAINT "way_tags_way_fkey" FOREIGN KEY ("way") REFERENCES "ways" ("id")
);
## Comment 10315
Date: 2008-10-07 15:31:42 +0200
From: @njnes
Sofar I cannot reproduce it. I think also some (or all) data is needed for this query to fail.
## Comment 10316
Date: 2008-10-07 17:12:13 +0200
From: @skinkie
printf("CREATE TABLE nodes_legacy (id serial, x double, y double, username varchar(255), timestamp timestamptz);\n");
printf("CREATE TABLE node_tags (node integer, k varchar(255), v varchar(1024), primary key (node, k), foreign key(node) references nodes_legacy);\n");
printf("CREATE TABLE ways (id serial,username varchar(255), timestamp timestamptz);\n");
printf("CREATE TABLE way_tags (way integer, k varchar(255), v varchar(1024), primary key (way, k), foreign key(way) references ways);\n");
printf("CREATE TABLE way_nds (way integer, idx integer, to_node integer, foreign key(way) references ways, foreign key(to_node) references nodes_legacy, primary key(way, idx));\n");
printf("CREATE TABLE relations(id serial, username varchar(255), timestamp timestamptz);\n");
printf("CREATE TABLE relation_members_node (relation integer, idx integer, to_node integer, role varchar(255), foreign key(relation) references relations, foreign key(to_node) references nodes_legacy, primary key(relation, idx));\n");
printf("CREATE TABLE relation_members_relation (relation integer, idx integer, to_relation integer, role varchar(255), foreign key(relation) references relations, foreign key(to_relation) references relations, primary key(relation, idx));\n");
printf("CREATE TABLE relation_members_way (relation integer, idx integer, to_way integer, role varchar(255), foreign key(relation) references relations, foreign key(to_way) references ways, primary key(relation, idx));\n");
printf("CREATE TABLE relation_tags (relation integer, k varchar(255), v varchar(1024), foreign key(relation) references relations, primary key(relation, k));\n");
This is the program code that was used to generate the initial table. I hope you mean this, and not the other 74GB.
## Comment 10317
Date: 2008-10-07 20:01:30 +0200
From: @njnes
I need data to run the query. Probably a small number or records will do.
## Comment 10318
Date: 2008-10-09 04:45:42 +0200
From: @skinkie
I'll give detailed instructions now...
http://repo.or.cz/w/handlerosm.git?a=blob_plain;f=osmparser.c;hb=HEAD
Download this program. Compile it, it is easy C.
http://hypercube.telascience.org/planet/planet-nl-latest.osm.gz
Now sadly there is a problem in this file. Find way id=7062297, and remove all duplicate tags, or remove the way entirely.
using: osmparser /path/to/your/planet-nl-latest > insert.sql
will result in some *.csv files and an insert.sql
mclient -lsql <insert.sql should automatically work (if you fixed the above artifact).
Execute the following statement:
select * from way_tags as w1, way_tags as w2 where w1.k = 'bridge' and w1.wayid = w2.wayid;
Your gdb session in mserver5 should look like this:
0x00007fd3f83402b6 in CMD_EQ_oid (ret=0x259f3c8, l=0x259f3a8, r=0x259f3b8) at ../../../../src/modules/kernel/batcalc.mx:1128
1128 *o = (*p @2 *t);
(gdb) bt
0 0x00007fd3f83402b6 in CMD_EQ_oid (ret=0x259f3c8, l=0x259f3a8, r=0x259f3b8) at ../../../../src/modules/kernel/batcalc.mx:1128
1 0x00007fd404653455 in DFLOWstep (t=0x253aa08, fs=0x4292cdf0) at ../../../src/mal/mal_interpreter.mx:1523
2 0x00007fd404657a81 in runDFLOWworker (t=0x253aa08) at ../../../src/mal/mal_interpreter.mx:810
3 0x00007fd403e95373 in wrapper_routine (data=0x4292d270) at ../../../src/gdk/gdk_posix.mx:935
4 0x00007fd402b3a027 in start_thread () from /lib/libpthread.so.0
5 0x00007fd401c6afad in clone () from /lib/libc.so.6
6 0x0000000000000000 in ?? ()
(I have a system ready you already are able to login to, with the latest CVS version)
## Comment 10319
Date: 2008-10-20 23:43:38 +0200
From: @skinkie
sql>select * from way_tags as w1, way_tags as w2 where w1.k = 'bridge' and
more>w1.wayid = w2.wayid;
0 tuples
!MALException:algebra.join:GDKerror
!ERROR: GDKload: cannot mmap(): name=27/2705, ext=tail
!OS: Cannot allocate memory
!ERROR: GDKload failed: name=27/2705, ext=tail
0 tuples
This looks like a much better error handling :) :)
But still; why isn't it possible to select two tables at the same time;
First select from table one a feature; And try to match the foreign key of this table, on the identical table, to match other features of (in my case) a way.
## Comment 10320
Date: 2008-10-21 00:11:44 +0200
From: @drstmane
It is possible, unless (e.g.) some intermediate result or the end result exceeds the available address space, or available disk space.
## Comment 10321
Date: 2008-10-21 00:40:29 +0200
From: @skinkie
I wish there was a day where i would *just* accept your answer and behave like someone that didn't care.
Do you agree from a functional point of view that:
1) The query can be rewritten into a Query, With Subquery
2) The amount of memory should never exceed the amount of memory it would take for only one of those subqueries to succeed.
Ok I tricked you. Or MonetDB tricked me to hide something:
1) SELECT * FROM way_tags WHERE way IN (SELECT way WHERE k = 'bridge');
I hope you agree with me on that.
2)
[New Thread 0xb2331b90 (LWP 1705)]
[New Thread 0xb1f30b90 (LWP 1706)]
mserver5: ../../../src/server/sql_select.mx:475: find_pivot: Assertion `subset->type == st_ptable' failed.
Program received signal SIGABRT, Aborted.
[Switching to Thread 0xb1f30b90 (LWP 1706)]
0xb7fee424 in __kernel_vsyscall ()
(gdb) bt
0 0xb7fee424 in __kernel_vsyscall ()
1 0xb7075670 in raise () from /lib/libc.so.6
2 0xb7076eb8 in abort () from /lib/libc.so.6
3 0xb706e64e in __assert_fail () from /lib/libc.so.6
4 0xb24af4db in find_pivot (subset=0xa568e40, t=0xa5601c8)
at ../../../src/server/sql_select.mx:475
5 0xb24b2e8d in sql_column_value (sql=0xa512080, scp=0xa568950,
se=0xa514340, grp=0x0, subset=0xa568e40, f=3)
at ../../../src/server/sql_select.mx:1571
6 0xb24b3436 in sql_value_exp (sql=0xa512080, scp=0xa568950, se=0xa514340,
grp=0x0, subset=0xa568e40, f=3, ek=
{type = 0 '\0', card = 2 '\002', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:1665
7 0xb24b6905 in _column_exp (sql=0xa512080, scp=0xa568950,
column_e=0xa5143b0, grp=0x0, subset=0xa568e40, f=3)
at ../../../src/server/sql_select.mx:2701
8 0xb24b6b1b in sql_column_exp (sql=0xa512080, scp=0xa568950,
column_e=0xa5143b0, grp=0x0, subset=0xa568e40, f=3)
at ../../../src/server/sql_select.mx:2735
9 0xb24ba64f in sql_simple_select (sql=0xa512080, scp=0xa568950,
sn=0xa514610) at ../../../src/server/sql_select.mx:3791
10 0xb24babe8 in sql_select (sql=0xa512080, scp=0xa568950, sn=0xa514610, ek=
{type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
---Type <return> to continue, or q <return> to quit---
at ../../../src/server/sql_select.mx:3907
11 0xb24ae830 in sql_subquery (sql=0xa512080, scp=0xa568950, sq=0xa514610, ek=
{type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:236
12 0xb24ae9fd in scope_subquery (sql=0xa512080, scp=0xa568950, sq=0xa514610,
ek={type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:279
13 0xb24b348d in sql_value_exp (sql=0xa512080, scp=0xa55b1e0, se=0xa514610,
grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 3 '\003', reduce = 0 '\0'})
at ../../../src/server/sql_select.mx:1669
14 0xb24b8eed in sql_logical_exp_ (sql=0xa512080, scp=0xa55b1e0,
sc=0xa5146e0, grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:3370
15 0xb24b9de6 in sql_logical_exp (sql=0xa512080, scp=0xa55b1e0, sc=0xa5146e0,
grp=0x0, subset=0x0, f=1, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:3628
16 0xb24bac4c in sql_select (sql=0xa512080, scp=0xa55b1e0, sn=0xa514790, ek=
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:3910
17 0xb24ae830 in sql_subquery (sql=0xa512080, scp=0xa55b1e0, sq=0xa514790, ek=
---Type <return> to continue, or q <return> to quit---
{type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:236
18 0xb24ae9fd in scope_subquery (sql=0xa512080, scp=0xa55b1e0, sq=0xa514790,
ek={type = 0 '\0', card = 4 '\004', reduce = 1 '\001'})
at ../../../src/server/sql_select.mx:279
19 0xb24bc327 in selects (sql=0xa512080, scp=0x0, s=0xa514790)
at ../../../src/server/sql_select.mx:4292
20 0xb24bed01 in semantic (sql=0xa512080, scp=0x0, s=0xa514790)
at ../../../src/server/sql_semantic.mx:1160
21 0xb24bef49 in output_semantic (sql=0xa512080, scp=0x0, s=0xa514790)
at ../../../src/server/sql_semantic.mx:1231
22 0xb244bfe9 in sql_symbol2stmt (c=0xa512080, sym=0xa514790)
at ../../../../src/backends/monet5/sql.mx:995
23 0xb2482844 in SQLparser (c=0x804d3f4)
at ../../../../src/backends/monet5/sql_scenario.mx:1023
24 0xb7f7c74d in runPhase (c=0x804d3f4, phase=1)
at ../../../src/mal/mal_scenario.mx:591
25 0xb7f7c845 in runScenarioBody (c=0x804d3f4)
at ../../../src/mal/mal_scenario.mx:622
26 0xb7f7ca43 in runScenario (c=0x804d3f4)
at ../../../src/mal/mal_scenario.mx:656
27 0xb7f456b7 in MSserveClient (dummy=0x804d3f4)
at ../../../src/mal/mal_session.mx:462
---Type <return> to continue, or q <return> to quit---
28 0xb73ae170 in start_thread () from /lib/libpthread.so.0
29 0xb7116dfe in clone () from /lib/libc.so.6
It is not the very very latest version, but it is from last week. If it is already fixed you can make me feel bad again.
## Comment 10322
Date: 2008-10-21 00:45:10 +0200
From: @skinkie
Sorry I just see my foolish error that resulted in the abort.
But If I correct my error; I will get results directy (up to the first foreign character, see other bug).
So my question here:
WORKING:
sql>explain select * from way_tags where way IN (select way from way_tags where k = 'bridge');
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| unction user.s1_1():void; |
| _1:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",0); |
| _6:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","way",1); |
| _8{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_1,_6); |
| _1:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _6:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _9:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",2); |
| _11{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_8,_9); |
| _8{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _12{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_11,_9); |
| _11{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _9:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _13:bat[:oid,:oid] {hlb>=1@0:oid,hub<1048577@0:oid} := sql.bind_dbat("sys","way_tags",1); |
| _14{tlb>=1@0:oid,tub<1048577@0:oid} := bat.reverse(_13); |
| _13:bat[:oid,:oid] {hlb>=1@0:oid,hub<1048577@0:oid} := nil:BAT; |
| _15{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kdifference(_12,_14); |
| _16{tlb>=0@0:oid,tub<4978910@0:oid} := bat.reverse(_15); |
| _15{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _17:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",0); |
| _22{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.uselect(_17,"bridge"); |
| _17:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _23:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","k",1); |
| _24{hlb>=4978910@0:oid,hub<6027486@0:oid} := algebra.uselect(_23,"bridge"); |
| _23:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _25{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_22,_24); |
| _22{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _24{hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _26:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",2); |
| _27{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_25,_26); |
| _25{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _28{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.uselect(_26,"bridge"); |
| _26:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _29{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_27,_28); |
| _27{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _28{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _30{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kdifference(_29,_14); |
| _29{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _14{tlb>=1@0:oid,tub<1048577@0:oid} := nil:BAT; |
| _32{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := algebra.markT(_30,0@0); |
| _30{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _33{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := bat.reverse(_32); |
| _32{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := nil:BAT; |
| _34:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",0); |
| _35:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","way",1); |
| _36{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_34,_35); |
| _34:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _35:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _37:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",2); |
| _38{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_36,_37); |
| _36{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _39{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_38,_37); |
| _38{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _37:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _40{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_33,_39); |
| _33{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _39{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _41:bat[:oid,:int] := bat.new(nil:oid,nil:int); |
| bat.append(_41,_40,true); |
| _40{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _46 := bat.reverse(_41); |
| _41:bat[:oid,:int] := nil:BAT; |
| _47{tlb>=0@0:oid,tub<4978910@0:oid} := algebra.semijoin(_16,_46); |
| _16{tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _46 := nil:BAT; |
| _48{hlb>=0@0:oid,hub<4978910@0:oid} := bat.reverse(_47); |
| _47{tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _49{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := algebra.markT(_48,0@0); |
| _48{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _50{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := bat.reverse(_49); |
| _49{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := nil:BAT; |
| _51{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_50,_12); |
| _12{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _52:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",0); |
| _53:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","k",1); |
| _54{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_52,_53); |
| _52:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _53:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _55:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",2); |
| _56{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_54,_55); |
| _54{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _57{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_56,_55); |
| _56{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _55:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _58{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_50,_57); |
| _57{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _59:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","v",0); |
| _61:bat[:oid,:str] {hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","v",1); |
| _62{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_59,_61); |
| _59:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _61:bat[:oid,:str] {hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _63:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","v",2); |
| _64{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_62,_63); |
| _62{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _65{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_64,_63); |
| _64{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _63:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _66{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_50,_65); |
| _50{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _65{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _67 := sql.resultSet(3,1,_51); |
| sql.rsColumn(_67,"sys.way_tags","way","int",32,0,_51); |
| _51{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_67,"sys.way_tags","k","varchar",255,0,_58); |
| _58{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_67,"sys.way_tags","v","varchar",1024,0,_66); |
| _66{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _76 := io.stdout(); |
| sql.exportResult(_76,_67,""); |
| nd s1_1; |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
BROKEN:
sql>explain select * from way_tags as w1, way_tags as w2 where w1.k = 'bridge' and w1.wayid = w2.wayid;
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| unction user.s2_1():void; |
| _1:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",0); |
| _9{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.uselect(_1,"bridge"); |
| _10:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","k",1); |
| _12{hlb>=4978910@0:oid,hub<6027486@0:oid} := algebra.uselect(_10,"bridge"); |
| _13{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_9,_12); |
| _9{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _12{hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _14:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",2); |
| _16{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_13,_14); |
| _13{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _17{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.uselect(_14,"bridge"); |
| _18{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_16,_17); |
| _16{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _17{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _19:bat[:oid,:oid] {hlb>=1@0:oid,hub<1048577@0:oid} := sql.bind_dbat("sys","way_tags",1); |
| _20{tlb>=1@0:oid,tub<1048577@0:oid} := bat.reverse(_19); |
| _19:bat[:oid,:oid] {hlb>=1@0:oid,hub<1048577@0:oid} := nil:BAT; |
| _21{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kdifference(_18,_20); |
| _18{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _22:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",0); |
| _24:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","way",1); |
| _25{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_22,_24); |
| _22:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _24:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _26:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",2); |
| _27{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_25,_26); |
| _25{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _28{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_27,_26); |
| _27{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _26:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _29{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kdifference(_28,_20); |
| _20{tlb>=1@0:oid,tub<1048577@0:oid} := nil:BAT; |
| _30{tlb>=0@0:oid,tub<4978910@0:oid} := bat.reverse(_29); |
| _31{hlb>=0@0:oid,hub<4978910@0:oid} := bat.reverse(_30); |
| _30{tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _32{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.project(_31,0); |
| _31{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _33{tlb>=0@0:oid,tub<4978910@0:oid} := bat.reverse(_32); |
| _32{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _34{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.project(_21,0); |
| _21{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _35{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.join(_34,_33); |
| _34{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _33{tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _37{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := algebra.markT(_35,0@0); |
| _38{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := bat.reverse(_37); |
| _37{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := nil:BAT; |
| _39:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",0); |
| _40:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","way",1); |
| _41{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_39,_40); |
| _39:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _40:bat[:oid,:int] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _42:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","way",2); |
| _43{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_41,_42); |
| _41{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _44{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_43,_42); |
| _43{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _42:bat[:oid,:int] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _45:bat[:oid,:oid] {hlb>=1@0:oid,hub<1048577@0:oid} := sql.bind_dbat("sys","way_tags",1); |
| _46{tlb>=1@0:oid,tub<1048577@0:oid} := bat.reverse(_45); |
| _45:bat[:oid,:oid] {hlb>=1@0:oid,hub<1048577@0:oid} := nil:BAT; |
| _47{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kdifference(_44,_46); |
| _46{tlb>=1@0:oid,tub<1048577@0:oid} := nil:BAT; |
| _48{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := bat.mirror(_47); |
| _47{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _49{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := bat.mirror(_29); |
| _29{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _50{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := bat.mirror(_48); |
| _51{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := bat.mirror(_49); |
| _52{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.join(_50,_51); |
| _50{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _51{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _53{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := algebra.markH(_52,0@0); |
| _54{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := algebra.markT(_52,0@0); |
| _52{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _55{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := bat.reverse(_54); |
| _54{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := nil:BAT; |
| _56{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.join(_55,_48); |
| _55{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _48{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _57{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.join(_53,_49); |
| _49{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _58:bat[:oid,:bit] {hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := batcalc.==(_56,_57); |
| _56{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _57{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _59{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.uselect(_58,true); |
| _58:bat[:oid,:bit] {hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _61{tlb>=0@0:oid,tub<nil:oid,hlb>=0@0:oid,hub<4978910@0:oid} := bat.reverse(_59); |
| _59{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _62{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.join(_61,_53); |
| _61{tlb>=0@0:oid,tub<nil:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _53{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _63{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := bat.reverse(_62); |
| _62{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _64{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.semijoin(_38,_63); |
| _38{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _65{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_64,_44); |
| _44{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _66{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_1,_10); |
| _1:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _10:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _67{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_66,_14); |
| _66{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _68{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_67,_14); |
| _67{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _14:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _69{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_64,_68); |
| _68{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _70:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","v",0); |
| _72:bat[:oid,:str] {hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","v",1); |
| _73{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_70,_72); |
| _70:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _72:bat[:oid,:str] {hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _74:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","v",2); |
| _75{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_73,_74); |
| _73{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _76{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_75,_74); |
| _75{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _74:bat[:oid,:str] {rows=4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _77{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_64,_76); |
| _64{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _78{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := bat.reverse(_35); |
| _35{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _79{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := algebra.markT(_78,0@0); |
| _78{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _80{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := bat.reverse(_79); |
| _79{hlb>=0@0:oid,hub<4978910@0:oid,tlb>=0@0:oid,tub<nil:oid} := nil:BAT; |
| _81{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := algebra.semijoin(_80,_63); |
| _80{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _63{tlb>=0@0:oid,tub<4978910@0:oid,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _82{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_81,_28); |
| _28{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _83:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",0); |
| _84:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := sql.bind("sys","way_tags","k",1); |
| _85{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kunion(_83,_84); |
| _83:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _84:bat[:oid,:str] {notnil,hlb>=4978910@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _86:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := sql.bind("sys","way_tags","k",2); |
| _87{hlb>=0@0:oid,hub<6027486@0:oid} := algebra.kdifference(_85,_86); |
| _85{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _88{hlb>=0@0:oid,hub<4978910@0:oid} := algebra.kunion(_87,_86); |
| _87{hlb>=0@0:oid,hub<6027486@0:oid} := nil:BAT; |
| _86:bat[:oid,:str] {rows=4978910@0:oid,notnil,hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _89{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_81,_88); |
| _88{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _90{hlb>=0@0:oid,hub<nil:oid} := algebra.join(_81,_76); |
| _81{hlb>=0@0:oid,hub<nil:oid,tlb>=0@0:oid,tub<4978910@0:oid} := nil:BAT; |
| _76{hlb>=0@0:oid,hub<4978910@0:oid} := nil:BAT; |
| _91 := sql.resultSet(6,1,_65); |
| sql.rsColumn(_91,"sys.w1","way","int",32,0,_65); |
| _65{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_91,"sys.w1","k","varchar",255,0,_69); |
| _69{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_91,"sys.w1","v","varchar",1024,0,_77); |
| _77{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_91,"sys.w2","way","int",32,0,_82); |
| _82{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_91,"sys.w2","k","varchar",255,0,_89); |
| _89{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| sql.rsColumn(_91,"sys.w2","v","varchar",1024,0,_90); |
| _90{hlb>=0@0:oid,hub<nil:oid} := nil:BAT; |
| _104 := io.stdout(); |
| sql.exportResult(_104,_91,""); |
| nd s2_1; |
+---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
## Comment 10323
Date: 2008-10-21 00:47:53 +0200
From: @skinkie
Never mind; I again am too stupid to type sql queries.
## Comment 10324
Date: 2008-10-21 09:07:34 +0200
From: @drstmane
So, this one can be close, then?
## Comment 10325
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2134428 at http://sourceforge.net/support/tracker.php?aid=2134428
| some issue with 'as' clause | https://api.github.com/repos/MonetDB/MonetDB/issues/1839/comments | 0 | 2020-11-30T10:03:25Z | 2024-06-28T07:37:06Z | https://github.com/MonetDB/MonetDB/issues/1839 | 753,336,063 | 1,839 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-27 09:17:40 +0200
From: Pierre BOIZOT <<pirboazo>>
To: @njnes
Version: -- development
Last updated: 2009-02-11 09:49:09 +0100
## Comment 10309
Date: 2008-09-27 21:17:40 +0200
From: Pierre BOIZOT <<pirboazo>>
When the column is integer or smallint, than the sum of a group is greater than the max value of the type the avg is false .
Bug view on ubuntu 8.04 and windows XP.
Pierre
Example:
sql>alter table car add column iprice integer ;
Timer 8906.000 msec 0 rowssql>alter table car add column iprice integer ;
Timer 8906.000 msec 0 rows
sql>alter table car add column sage smallint ;
Timer 5218.000 msec 0 rows
sql>\d car
CREATE TABLE "pib"."car" (
"age" int,
"gender" char(1),
"price" bigint,
"category" varchar(20),
"class" varchar(20),
"codville" char(3),
"sage" smallint,
"iprice" int
);
sql>update car set iprice=price;
Rows affected 24000000
Timer 18640.000 msec 0 rows
sql>update car set sage = age ;
Rows affected 24000000
Timer 15094.000 msec 0 rows
With smallint value NULL.
sql>select count(*), gender , sum (sage), avg(sage) from car group by gender;
+--------------+-------+----------+-----------------------+
| count_gender |gender |sum_sage |avg_sage |
+==============+=======+==========+=======================+
| 12000000 |f |494872440 | null |
| 12000000 |m |494872440 | null |
+--------------+-------+----------+-----------------------+
Timer 1656.000 msec 2 rows
sql>select count(*), gender , sum (age), avg(age) from car group by gender;
+--------------+-------+----------+-----------------------+
| count_gender |gender |sum_age |avg_age |
+==============+=======+==========+=======================+
| 12000000 |f |494872440 | 41.239370000000001 |
| 12000000 |m |494872440 | 41.239370000000001 |
+--------------+-------+----------+-----------------------+
Timer 1797.000 msec 2 rows
With integer value negative :
sql>select gender, count(*),sum(iprice), avg(price), avg(iprice) from car group by gender;
+-------+--------+-------------+----------------------+-----------------------+
| gende |count_g |sum_iprice |avg_price |avg_iprice |
: r |ender | | | |
+=======+========+=============+======================+=======================+
| f |1200000 |455067160680 | 37922.26339 | -16.614391333333334 |
: |0 | | | |
| m |1200000 |455067160680 | 37922.26339 | -16.614391333333334 |
: |0 | | | |
+-------+--------+-------------+----------------------+-----------------------+
Timer 2516.000 msec 2 rows
## Comment 10310
Date: 2009-02-11 21:49:09 +0100
From: @njnes
added test to BugTracker-2009. Seems fixed. Not 100% sure as it maybe data related which isn't included in the example code.
## Comment 10311
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2132666 at http://sourceforge.net/support/tracker.php?aid=2132666
| Avg on integer and smallint : false | https://api.github.com/repos/MonetDB/MonetDB/issues/1838/comments | 0 | 2020-11-30T10:03:22Z | 2024-06-27T11:32:49Z | https://github.com/MonetDB/MonetDB/issues/1838 | 753,336,011 | 1,838 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-26 08:36:03 +0200
From: Hendrike Peetz <<hpeetz>>
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:04:06 +0100
## Comment 10302
Date: 2008-09-26 20:36:03 +0200
From: Hendrike Peetz <<hpeetz>>
Operating system: Windows XP, 32 bit on parallels (running on Leopard 64bit processor)
Using the 32 bit stable version, 20080624
The query that causes this problem:
select i.name, v1.name, v1.name
from scene s, scene b, victim v1, victim v2, inspector i where
not s.id=b.id and v1.id=s.victim_id and v2.id=b.victim_id;
The result:
System aborts, the client and the server, no error message.
## Comment 10303
Date: 2008-09-26 21:00:47 +0200
From: @drstmane
With assertions enabled, the query triggers the following assertion:
mserver5: /ufs/manegold/_/scratch0/Monet/Testing/Stable/source/sql/src/server/sql_optimize.mx:1489: set2pivot: Assertion `0' failed.
Aborted
## Comment 10304
Date: 2008-10-07 13:57:13 +0200
From: @njnes
indeed crashes with default version. But with the algebra version (mclient -lsql -G) it runs fine.
## Comment 10305
Date: 2008-11-17 21:02:23 +0100
From: @romulogoncalves
Test added at:
/sql/src/test/BugTracker-2008/Tests/aborting_process.SF-2130710.sql
The name does not describe about what is the bug. I would like to rename it, but then I decided to leave like this to simplify the identification of the bug report.
## Comment 10306
Date: 2008-12-01 15:47:31 +0100
From: @romulogoncalves
This bug is fixed in the algebra version for the stable and current branch of M5-SQL.
I can't close the bug until it is fixed in the normal version as well.
To use the algebra version just call mclient with option "-G":
mclient -G
## Comment 10307
Date: 2009-02-09 15:04:06 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10308
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2130710 at http://sourceforge.net/support/tracker.php?aid=2130710
| SQL: Aborting process | https://api.github.com/repos/MonetDB/MonetDB/issues/1837/comments | 0 | 2020-11-30T10:03:18Z | 2024-06-27T11:32:47Z | https://github.com/MonetDB/MonetDB/issues/1837 | 753,335,969 | 1,837 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-26 02:04:32 +0200
From: Wouter Alink <<alink>>
To: Wouter Alink <<alink>>
Version: -- development
Last updated: 2009-02-16 11:09:13 +0100
## Comment 10294
Date: 2008-09-26 14:04:32 +0200
From: Wouter Alink <<alink>>
Using the August-release.
The query below produces the following bug:
MAPI = monetdb@localhost:50000
QUERY = <result> {
ERROR = !fatal error: attribute `item3' referenced in projection not found
-----------------------
<result> {
let $entries := doc("aap.xml")//entry
for $i in distinct-values($entries//docs)
return
<cluster> {
element { "name" } { $i },
let $items := $entries[docs=$i]
let $exts := for $a in $items/names/name
return substring-after($a,"a")
for $j in $exts
return <hit> {
$items/names/name[ends-with(.,$j)]
} </hit>
} </cluster>
} </result>
## Comment 10295
Date: 2008-10-02 10:02:38 +0200
From: @sjoerdmullender
This is weird. When I compile this query (using pf), there is no "item3" outside of comments, so I don't understand where the message comes from.
Also, I tried this with a random document, but didn't get an error. Is the error dependent on the document you use?
Which version were you using?
## Comment 10296
Date: 2008-10-12 01:14:20 +0200
From: @drstmane
Compiling the query (using both `pf -A` & `pf -M`) works fine also for me, with the latest CVS versions of both the latest Stable release branch and the Current development head.
Wouter,
which version are you using?
## Comment 10297
Date: 2008-11-10 22:17:34 +0100
From: @peterboncz
most likely, improvements in the pathfinder compiler have made this problem disappear. In that case, this bug can be closed.
## Comment 10298
Date: 2008-11-12 12:04:06 +0100
From: Jan Rittinger <<jan.rittinger>>
Closing the bug as the error does not arise in the stable branch anymore.
Wouter if you still get an error please open again.
## Comment 10299
Date: 2009-02-16 14:01:53 +0100
From: @drstmane
re-opened to remind us that we should consider adding a test
## Comment 10300
Date: 2009-02-16 23:09:13 +0100
From: @drstmane
added test in pathfinder/tests/BugTracker/Tests/query_compilation_item3.SF-2130051.*
appears to work fine.
## Comment 10301
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2130051 at http://sourceforge.net/support/tracker.php?aid=2130051
| XQ: query compilation: item3 not found | https://api.github.com/repos/MonetDB/MonetDB/issues/1836/comments | 0 | 2020-11-30T10:03:15Z | 2024-06-28T07:37:05Z | https://github.com/MonetDB/MonetDB/issues/1836 | 753,335,907 | 1,836 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-23 12:03:08 +0200
From: Jan Rittinger <<jan.rittinger>>
To: XQuery devs <<bugs-xquery>>
Version: 11.1.1 (Mar2011) [obsolete]
Last updated: 2011-04-28 16:39:01 +0200
## Comment 10290
Date: 2008-09-23 12:03:08 +0200
From: Jan Rittinger <<jan.rittinger>>
Pathfinder cannot handle stupid queries--queries where the error function is used in incorrect/unreasonable places--correctly.
This leads to 1.) errors that are optimized away and 2.) compile time problems as some operators are not able to consume an error operator.
Example for Problem 1: The core representation does not know about side effects which leads to incorrect optimizations of the following bogus query: '(if (1 eq 1) then error () else 42)/<foo/>' (result is <foo/>).
Example for Problem 2: The algebra does not prune operators sitting on top of an error operator. For bogus queries such as 'node-name(error("FOO"))' or http://sourceforge.net/support/tracker.php?aid=2122091 the code generation fails because some assumptions were not met.
For the first problem additional side effect information in the core respresentation could be a solution. The second problem can be solved by an algebra rewrite that prunes everything above an error operator (until union operators representing choices are reached).
## Comment 10291
Date: 2009-02-16 16:12:24 +0100
From: Jan Rittinger <<jan.rittinger>>
Added test.
Problem 2 has been fixed.
## Comment 10292
Date: 2009-11-15 11:37:39 +0100
From: @drstmane
===================================================================
2009/11/15 - stmane: pathfinder/tests/BugTracker/Tests/All,1.146.2.6
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.KO.stable.err,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.KO.stable.out,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.KO.xq,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.OK.stable.err,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.OK.stable.out,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.OK.xq,1.1.2.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.stable.err,1.2.8.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.stable.out,1.2.8.1
pathfinder/tests/BugTracker/Tests/side-effects.SF-2124300.xq,1.2.8.1
split test in two to test fixed and still failing part separately;
disabled failing part; please re-enabled once the bug is fixed;
cf.,
ID: 2124300 "PF: error handling for erroneous query incorrect"
https://sourceforge.net/tracker/?func=detail&aid=2124300&group_id=56967&atid=482468
===================================================================
## Comment 10293
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2124300 at http://sourceforge.net/support/tracker.php?aid=2124300
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.
## Comment 15698
Date: 2011-03-28 17:37:07 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
## Comment 15778
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.
| PF: error handling for erroneous query incorrect | https://api.github.com/repos/MonetDB/MonetDB/issues/1835/comments | 0 | 2020-11-30T10:03:12Z | 2024-06-28T07:37:05Z | https://github.com/MonetDB/MonetDB/issues/1835 | 753,335,863 | 1,835 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-23 09:57:43 +0200
From: Jens Teubner <<teubner>>
To: Jens Teubner <<teubner>>
Version: -- development
Last updated: 2009-11-12 10:39:34 +0100
## Comment 10286
Date: 2008-09-23 09:57:43 +0200
From: Jens Teubner <<teubner>>
A silly one: Pathfinder currently allows function declarations where two parameters have the same name:
declare function foo($x, $x)
{
$x
};
foo(1,2)
This obviously is nonsense and should not be allowed.
Working on it...
## Comment 10287
Date: 2009-02-17 11:39:15 +0100
From: @drstmane
PF now(?) issues a warning:
$ cat /tmp/foo.xq
declare function foo($x, $x)
{
$x
};
foo(1,2)
$ mclient -lx /tmp/foo.xq
warning: variable reuse: at (1,27-1,28): $x
2
Would that be "enough", or should that be turned into an error?
## Comment 10288
Date: 2009-11-12 10:39:34 +0100
From: @peterboncz
not a serious issue; an error message is given
## Comment 10289
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2124130 at http://sourceforge.net/support/tracker.php?aid=2124130
| PF: Multiple function parameters with same name | https://api.github.com/repos/MonetDB/MonetDB/issues/1834/comments | 0 | 2020-11-30T10:03:09Z | 2024-06-27T11:32:45Z | https://github.com/MonetDB/MonetDB/issues/1834 | 753,335,812 | 1,834 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-21 11:23:03 +0200
From: @yzchang
To: @yzchang
Version: -- development
Last updated: 2008-09-22 10:28:22 +0200
## Comment 10282
Date: 2008-09-21 23:23:03 +0200
From: @yzchang
An ADT group has reported that, on Win XP, mclient handles Ctrl-Z differently than what Win XP does. I'm not sure if this is an expected behaviour of mclient, or a missing feature. Steps to reproduce:
I. use query Q1 from page http://monetdb.cwi.nl/projects/monetdb/XQuery/QuickTour/Books/index.html
II. Copy the text of the query and paste it to XQuery client console window. (Windows XP)
III. Put the ^Z character (by pressing Ctrl-Z or F6) on the same line as the query text ends ( i.e. } </bib> ^Z )
IV. Press ENTER. See that the cursor simply moves to new line (query is not submitted).
V. Press ENTER once again. Prompt “more>†appears.
VI. Compare with functioning of e.g. WinXP shell command “copy con 1.txtâ€. It handles ^Z on the last line correctly.
## Comment 10283
Date: 2008-09-21 23:57:29 +0200
From: @drstmane
IMHO this is a (standard) feature:
"end-of-document" (CRTL-D / CTRL-Z) needs to be the only content of a line.
(Just try what CRTL-D does on Linux in the same case ...)
(See also my reply to the respective ADT group's email / report.)
## Comment 10284
Date: 2008-09-22 10:28:22 +0200
From: @yzchang
Hi Stefan,
I overlooked your comment one this point. I printed the e-mail on paper, but the layout makes it difficult to distinguish your text from the students' text.
I also expect Ctrl-Z to behave the same as Ctrl-D. Without having read your comment, I was wondering if this standard feature is different on Windows, of Windows has just extended this feature to also handle Ctrl-Z at the end of non-empty line. Now I think the second might be true.
I'm closing this bug as invalid.
Jennie
## Comment 10285
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2122108 at http://sourceforge.net/support/tracker.php?aid=2122108
| mclient: unexpected behaviour of Ctrl-Z | https://api.github.com/repos/MonetDB/MonetDB/issues/1833/comments | 0 | 2020-11-30T10:03:06Z | 2024-06-28T07:37:05Z | https://github.com/MonetDB/MonetDB/issues/1833 | 753,335,772 | 1,833 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-21 10:58:58 +0200
From: @yzchang
To: Jan Rittinger <<jan.rittinger>>
Version: -- development
Last updated: 2008-11-15 10:31:20 +0100
## Comment 10276
Date: 2008-09-21 22:58:58 +0200
From: @yzchang
[query written by an ADT student]
The use of fn:distinct-values in the following query results in an assertion failed, only when the algebra backend is used (hence, not in MPS):
$ echo 'for $fname in distinct-values(doc("people")/people/person/leisure_activities/*)
order by $fname
return <activity> { $fname/text() } </activity>' | pf -A
pf: /ufs/zhang/monet/stable/pathfinder/compiler/mil/milgen.brg:7875: do_reduce: Assertion `!(type_of (((p)->child[0]), p->sem.ii.item) & ~0x0000F000)' failed.
Aborted
## Comment 10277
Date: 2008-09-21 23:15:19 +0200
From: @yzchang
- test added in
pathfinder/tests/BugTracker/Tests/distinct-values-triggers-assertion.SF-2122091_ALG.*
- corrected typo in summary
## Comment 10278
Date: 2008-09-23 12:14:06 +0200
From: Jan Rittinger <<jan.rittinger>>
The query should always generate an error.
Avoided the assertion for this query in the CVS Head -- back-porting is not possible due to usage of new error type.
## Comment 10279
Date: 2008-10-04 13:46:17 +0200
From: @drstmane
re-opened as the CVS head still/again/now fails with
pf: /scratch/monet.Int.64.32.d.1.18921/pathfinder/compiler/mil/milgen.brg:7895: do_reduce: Assertion `!(type_of (((p)->child[0]), p->sem.ii.item) & ~0x0000F000)' failed.
./distinct-values-triggers-assertion.SF-2122091_ALG.sh: line 7: 22629 Aborted $p $q > /dev/null
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/Int.64.32.d.1-Fedora8/tests_BugTracker/distinct-values-triggers-assertion.SF-2122091_ALG.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTestsg103/Int.64.32.d.1-Fedora8/tests_BugTracker/distinct-values-triggers-assertion.SF-2122091_ALG.err.00.html
Please check & comment whether this is indeed the desired/expected error message.
## Comment 10280
Date: 2008-11-15 22:31:20 +0100
From: Jan Rittinger <<jan.rittinger>>
Testweb is green again -- closing.
## Comment 10281
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2122091 at http://sourceforge.net/support/tracker.php?aid=2122091
| PF: distinct-values triggers assertion | https://api.github.com/repos/MonetDB/MonetDB/issues/1832/comments | 0 | 2020-11-30T10:03:03Z | 2024-06-27T11:32:43Z | https://github.com/MonetDB/MonetDB/issues/1832 | 753,335,729 | 1,832 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-17 04:36:47 +0200
From: @drstmane
To: @mlkersten
Version: -- development
Last updated: 2008-09-19 10:50:56 +0200
## Comment 10273
Date: 2008-09-17 16:36:47 +0200
From: @drstmane
The MonetDB web site fails to build based on the "Stable" released code base:
"
(./opt_evaluate.bdy.texi) (./opt_costModel.bdy.texi [69])
! I can't find file `opt_dataflow.bdy.texi'.
@temp ->@input opt_dataflow.bdy.texi
@includezzz ...mp {@input 1 }@expandafter }@temp
@popthisfilestack
l.259 @include opt_dataflow.bdy.texi
Please type another input file name:
"
Please either make is build on the stable release, or let me know, whether and when the website should be built from the least development code base.
Thank you very much in advance!
Stefan
## Comment 10274
Date: 2008-09-19 22:50:56 +0200
From: @mlkersten
Fixed the SQL manual generation
## Comment 10275
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2116269 at http://sourceforge.net/support/tracker.php?aid=2116269
| Website fails to build on "Stable" release | https://api.github.com/repos/MonetDB/MonetDB/issues/1831/comments | 0 | 2020-11-30T10:03:00Z | 2024-06-27T11:32:42Z | https://github.com/MonetDB/MonetDB/issues/1831 | 753,335,681 | 1,831 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-17 04:08:09 +0200
From: Loredana Afanasiev <<lafanasi>>
To: Stefan Manegold <<Stefan.Manegold>>
Version: -- development
Last updated: 2008-10-03 06:27:54 +0200
## Comment 10270
Date: 2008-09-17 16:08:09 +0200
From: Loredana Afanasiev <<lafanasi>>
Hi,
the bulk loading query from:
http://monetdb.cwi.nl/projects/monetdb/XQuery/Documentation/Bulk-Loading-a-Collection.htmlBulk-Loading-a-Collection
has a couple of problems:
1. $n variable undefined
2. the first argument in the call of add-doc() contains only the path to the document, missing the document name.
3. the second argument in the call of add-doc() is of type "string?" instead of required "string". This is an error output by the static type checker of the algebra version compiler, which is the default compiler.
Here is the query I used to successfully bulk load my data:
for $d in doc("/tmp/dir.xml")//doc
return
add-doc(fn:concat($d/@path,$d/@name), fn:string($d/@name), "my-coll", 0)
groetjes,
l.
## Comment 10271
Date: 2008-09-17 16:39:48 +0200
From: @drstmane
Thanks for the report!
I just fixed in the CVS repository for our web site.
(In fact, I also fixed your proposed query slightly by adding the required "pf:" namespace prefix to "add-doc()" ;-)).
Unfortunately, the fix will only be live once
[ 2116269 ] Website fails to build on "Stable" release
https://sourceforge.net/tracker/index.php?func=detail&aid=2116269&group_id=56967&atid=482468
is fixed.
Stefan
## Comment 10272
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2116209 at http://sourceforge.net/support/tracker.php?aid=2116209
| document bulk-load query | https://api.github.com/repos/MonetDB/MonetDB/issues/1830/comments | 0 | 2020-11-30T10:02:57Z | 2024-06-27T11:32:41Z | https://github.com/MonetDB/MonetDB/issues/1830 | 753,335,645 | 1,830 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-11 01:58:44 +0200
From: @skinkie
To: @sjoerdmullender
Version: -- development
Last updated: 2008-09-12 11:21:09 +0200
## Comment 10266
Date: 2008-09-11 01:58:44 +0200
From: @skinkie
I think this is an UTF8 artifact:
| 22699 |radozw |
| 22694 |Christian Karrié |
| 22692 |janrikard |
A special character is probably counter as two. Getting the pipes not to align right.
## Comment 10267
Date: 2008-09-11 08:56:06 +0200
From: @grobian
I think Sjoerd already fixed this, and I fixed the awkward border spacing. Can you try a recent snapshot of clients (stable or current shouldn't matter).
## Comment 10268
Date: 2008-09-12 11:21:09 +0200
From: @sjoerdmullender
This is indeed exactly the problem I fixed the other day. Both in stable and current.
I added a test for this in sql/src/test/mapi/Tests/utf8test.
## Comment 10269
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2104624 at http://sourceforge.net/support/tracker.php?aid=2104624
| Column output wrong with special characters | https://api.github.com/repos/MonetDB/MonetDB/issues/1829/comments | 0 | 2020-11-30T10:02:54Z | 2024-06-27T11:32:40Z | https://github.com/MonetDB/MonetDB/issues/1829 | 753,335,601 | 1,829 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-10 10:39:41 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2008-11-14 02:55:27 +0100
## Comment 10261
Date: 2008-09-10 10:39:41 +0200
From: @romulogoncalves
NULL should not be seen as a value, so UNIQUE constraint check should not fail over several NULL's in the same column.
The sql examples are:
create table crash_q (q integer,unique (q));
insert into crash_q (q) values (NULL);
insert into crash_q (q) values (NULL);
insert into crash_q (q) values (1);
QUERY = insert into crash_q (q) values (NULL);
ERROR = !SQLException:assert:INSERT INTO: UNIQUE constraint 'crash_q.crash_q_q_unique' violated
create table crash_q (q integer, x integer,unique (q)) ;
insert into crash_q(x) values(1);
insert into crash_q(x) values(2);
QUERY = insert into crash_q(x) values(2);
ERROR = !SQLException:assert:INSERT INTO: UNIQUE constraint 'crash_q.crash_q_q_unique' violated
Romulo
## Comment 10262
Date: 2008-09-10 11:17:25 +0200
From: @drstmane
See also
[ 2075241 ] When the NULL is in a column,it shouldn't add primary key
http://sourceforge.net/tracker/index.php?func=detail&aid=2075241&group_id=56967&atid=482468
[ 2075180 ] the unique column can't insert more than 1 row with null
http://sourceforge.net/tracker/index.php?func=detail&aid=2075180&group_id=56967&atid=482468
[ 1960373 ] kunion and nil
http://sourceforge.net/tracker/index.php?func=detail&aid=1960373&group_id=56967&atid=482468
## Comment 10263
Date: 2008-09-10 11:48:18 +0200
From: @romulogoncalves
Yes, all the problems are related and they will be fixed.
The NULLS were not handled properly in the SQL constraints check....
Romulo
## Comment 10264
Date: 2008-11-14 14:55:27 +0100
From: @romulogoncalves
The fix for this bug were the check ins:
[Monetdb-sql-checkins] sql/src/server sql_schema.mx, Nov2008, 1.152, 1.152.2.1
[Monetdb-sql-checkins] sql/src/server sql_updates.mx, Nov2008, 1.153, 1.153.2.1
[Monetdb-sql-checkins] sql/src/storage store.mx, Nov2008, 1.22, 1.22.2.1
No test need to be added because it is covered by the tests for the following bugs:
[ 2075241 ] When the NULL is in a column,it shouldn't add primary key
http://sourceforge.net/tracker/index.php?func=detail&aid=2075241&group_id=56967&atid=482468
[ 2075180 ] the unique column can't insert more than 1 row with null
http://sourceforge.net/tracker/index.php?func=detail&aid=2075180&group_id=56967&atid=482468
## Comment 10265
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2103348 at http://sourceforge.net/support/tracker.php?aid=2103348
| unique problem with nulls | https://api.github.com/repos/MonetDB/MonetDB/issues/1828/comments | 0 | 2020-11-30T10:02:51Z | 2024-06-27T11:32:39Z | https://github.com/MonetDB/MonetDB/issues/1828 | 753,335,555 | 1,828 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-09 04:46:17 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-11-22 10:30:47 +0100
## Comment 10254
Date: 2008-09-09 16:46:17 +0200
From: @romulogoncalves
When we have too many nested operators the mserver crashes for algebra version. However, the error message is given in the normal version.
To see the example run the sql file in attach.
## Comment 10255
Date: 2008-11-17 20:55:26 +0100
From: @romulogoncalves
Test added at:
/sql/src/test/BugTracker-2008/Tests/too_may_nested_operators.SF-2102167.ssql
It seems the problem is gone and now the proper message is returned by the mserver.
I will not close it until I get a complete result from the test-web
## Comment 10256
Date: 2009-02-16 10:44:28 +0100
From: @drstmane
test appears to fail with Intel's icc on Fedora8/x86_64 --- not with icc on RedHat4WS/ia64, though:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.32.d.1-Fedora8/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.32.d.1-Fedora8/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora8/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora8/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.err.00.html
## Comment 10257
Date: 2009-06-05 13:35:15 +0200
From: @drstmane
Updated TestWeb URLs:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.32.d.1-Fedora10/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.32.d.1-Fedora10/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora10/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.err.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/Int.64.64.d.1-Fedora10/src_test_BugTracker-2008/too_may_nested_operators.SF-2102167.out.00.html
## Comment 10258
Date: 2009-08-14 13:54:42 +0200
From: @drstmane
tagged subject
## Comment 10259
Date: 2009-11-22 22:30:46 +0100
From: @njnes
is duplicate of 921173
## Comment 10260
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2102167 at http://sourceforge.net/support/tracker.php?aid=2102167
This bug was marked DUPLICATE in the database it was moved from.
Changing resolution to "MOVED"
| SQL: too may nested operators in algebra version | https://api.github.com/repos/MonetDB/MonetDB/issues/1827/comments | 0 | 2020-11-30T10:02:48Z | 2024-06-28T07:37:04Z | https://github.com/MonetDB/MonetDB/issues/1827 | 753,335,514 | 1,827 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-09 04:06:53 +0200
From: @romulogoncalves
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:05:48 +0100
## Comment 10247
Date: 2008-09-09 16:06:53 +0200
From: @romulogoncalves
The following sql crashes M5-SQL no-algebra version....
create table t1(id int);
select id from t1 where 5 between 4 and 6;
drop table t1;
and it give the following error message in the algebra version:
mdb>EOD
mdb> _21;
[goncalve@alviss test]$ mclient current debug algebra sql < test.sql > out
MAPI = monetdb@localhost:50000
QUERY = select id from t1 where 5 between 4 and 6;
ERROR = !TypeException:user.s0_3[4]:'algebra.uselect' undefined in: _7:any := algebra.uselect(_4:bte, _5:bte, _6:bte, _8:bit, _8:bit)
!TypeException:user.s0_3[6]:'algebra.markT' undefined in: _11:any := algebra.markT(_7:any, _9:oid)
!TypeException:user.s0_3[7]:'bat.reverse' undefined in: _12:any := bat.reverse(_11:any)
!TypeException:user.s0_3[17]:'algebra.join' undefined in: _28:any := algebra.join(_12:any, _27:bat[:oid,:int])
[goncalve@alviss test]$
## Comment 10248
Date: 2008-09-14 22:46:09 +0200
From: @mlkersten
Added the test file
between_no_columns.SF2102101.sql
## Comment 10249
Date: 2008-11-17 16:07:50 +0100
From: @romulogoncalves
Martin,
I can't find the test file....
If someone had's a test for a bug, please add the complete path until the top directory of the module.
Because not all the bugs tests are added to sql/src/test/BugTracker/Tests ;)
## Comment 10250
Date: 2008-11-17 16:16:34 +0100
From: @drstmane
Neither can I:
$ find sql -type f | grep 2102101
$ find sql -type f | grep between_no_columns
$ find sql -type f | grep between
sql/src/test/bugs/innerjoin_between-bug-sf-960672.sql
sql/src/test/BugTracker/Tests/between_having_problem.SF-1959391.sql
sql/src/test/BugTracker/Tests/between_having_problem.SF-1959391.stable.err
sql/src/test/BugTracker/Tests/between_having_problem.SF-1959391.stable.err.Algebra
sql/src/test/BugTracker/Tests/between_having_problem.SF-1959391.stable.out
sql/src/test/BugTracker/Tests/between_on_strings.SF-2021508.sql
sql/src/test/BugTracker/Tests/between_on_strings.SF-2021508.stable.err
sql/src/test/BugTracker/Tests/between_on_strings.SF-2021508.stable.out
sql/src/test/BugTracker/Tests/between_with_column.SF-1959410.sql
sql/src/test/BugTracker/Tests/between_with_column.SF-1959410.stable.err
sql/src/test/BugTracker/Tests/between_with_column.SF-1959410.stable.out
sql/src/test/BugTracker-2008/Tests/select_between_wrong_result.SF-2080189.sql
sql/src/test/BugTracker-2008/Tests/select_between_wrong_result.SF-2080189.stable.err
sql/src/test/BugTracker-2008/Tests/select_between_wrong_result.SF-2080189.stable.out
sql/src/test/bugs/Tests/innerjoin_between-bug-sf-960672.sql.src
sql/src/test/bugs/Tests/innerjoin_between-bug-sf-960672.stable.err
sql/src/test/bugs/Tests/innerjoin_between-bug-sf-960672.stable.out
## Comment 10251
Date: 2008-12-01 15:46:17 +0100
From: @romulogoncalves
This bug is fixed in the algebra version for the stable and current branch of M5-SQL.
I can't close the bug until it is fixed in the normal version as well.
To use the algebra version just call mclient with option "-G":
mclient -G
## Comment 10252
Date: 2009-02-09 15:05:47 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10253
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2102101 at http://sourceforge.net/support/tracker.php?aid=2102101
| between without columns | https://api.github.com/repos/MonetDB/MonetDB/issues/1826/comments | 0 | 2020-11-30T10:02:44Z | 2024-06-27T11:32:36Z | https://github.com/MonetDB/MonetDB/issues/1826 | 753,335,461 | 1,826 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-09 03:40:21 +0200
From: @sjoerdmullender
To: SQL devs <<bugs-sql>>
Version: 2.40.1 (Oct2010) [obsolete]
Last updated: 2011-01-25 12:44:04 +0100
## Comment 10242
Date: 2008-09-09 15:40:21 +0200
From: @sjoerdmullender
There is no stable test output for the crashme test. This makes the test totally useless. Please provide the correct expected output.
## Comment 10243
Date: 2008-12-05 12:03:55 +0100
From: @drstmane
since it makes little (no) sense to run tests without stable output,
I disabled this one and
https://sourceforge.net/tracker/index.php?func=detail&aid=2102055&group_id=56967&atid=482468
## Comment 10244
Date: 2009-02-15 19:09:02 +0100
From: @drstmane
test has been disabled in the Feb2009 release branch, only.
## Comment 10245
Date: 2009-08-14 13:58:52 +0200
From: @drstmane
tagged subject
## Comment 10246
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2102056 at http://sourceforge.net/support/tracker.php?aid=2102056
## Comment 15130
Date: 2010-10-28 13:19:42 +0200
From: @grobian
the test currently successfully crashes the server, aproving it's output, however is a tedious job.
## Comment 15131
Date: 2010-10-28 13:20:35 +0200
From: @grobian
sorry, it doesn't crash, but the test can't be fully executed since the server disconnects the client on the huge expression.
## Comment 15418
Date: 2011-01-25 12:43:46 +0100
From: @grobian
Changeset [9861cf6f10df](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=9861cf6f10df) made by Fabian Groffen <fabian@cwi.nl> in the MonetDB repo, refers to this bug.
For complete details, see [http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9861cf6f10df](https://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=http//devmonetdborg/hg/MonetDB?cmd=changeset;node=9861cf6f10df)
Changeset description:
disable running crashme test, bug #1825
There is currently no way to run it, since the server disconnects the
client when it runs out of stack space.
| SQL: no test output for crashme test | https://api.github.com/repos/MonetDB/MonetDB/issues/1825/comments | 0 | 2020-11-30T10:02:41Z | 2024-06-28T07:37:04Z | https://github.com/MonetDB/MonetDB/issues/1825 | 753,335,415 | 1,825 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-09-09 03:40:11 +0200
From: @sjoerdmullender
To: Romulo Goncalves <<goncalve>>
Version: -- development
Last updated: 2009-02-15 07:08:26 +0100
## Comment 10238
Date: 2008-09-09 15:40:11 +0200
From: @sjoerdmullender
There is no stable test output for the 50ways test. This makes the test totally useless. Please provide the correct expected output.
## Comment 10239
Date: 2008-12-05 12:04:04 +0100
From: @drstmane
since it makes little (no) sense to run tests without stable output,
I disabled this one and
https://sourceforge.net/tracker/index.php?func=detail&aid=2102056&group_id=56967&atid=482468
## Comment 10240
Date: 2009-02-15 19:08:26 +0100
From: @drstmane
test appears to have been fixed:
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-Fedora10/src_test/50ways.out.00.html
http://monetdb.cwi.nl/testing/projects/monetdb/Stable/sql/.mTests103/GNU.32.32.d.1-Fedora10/src_test/50ways.err.00.html
## Comment 10241
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2102055 at http://sourceforge.net/support/tracker.php?aid=2102055
| no test output for 50ways test | https://api.github.com/repos/MonetDB/MonetDB/issues/1824/comments | 0 | 2020-11-30T10:02:38Z | 2024-06-27T11:32:34Z | https://github.com/MonetDB/MonetDB/issues/1824 | 753,335,364 | 1,824 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 10:38:11 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:35:31 +0200
## Comment 10234
Date: 2008-08-28 10:38:11 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1. setup
create schema s1;
create schema s2;
drop table s1.A;
drop table s2.A;
create table s1.A(a varchar(10) NOT NULL UNIQUE);
create table s2.A(a varchar(10) NOT NULL);
set schema s2;
insert into A values('abc');
set schema s1;
insert into A values('abc');
2. result
select * from s1.A;
select * from s2.A;
+-----+
| a |
+=====+
| abc |
| abc |
+-----+
But after I update the sequence,then:
sql> drop table s1.A;
sql> drop table s2.A;
sql> create table s1.A(a varchar(10) NOT NULL UNIQUE);
sql> create table s2.A(a varchar(10) NOT NULL);
sql>
sql> set schema s1;
sql> insert into A values('abc');
Rows affected 1
sql> set schema s2;
sql> insert into A values('abc');
!SQLException:assert:INSERT INTO: UNIQUE constraint 'a.a_a_unique' violated
## Comment 10235
Date: 2008-08-28 12:57:10 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test constraint_with_schemas.SF-2080219.sql
## Comment 10236
Date: 2008-09-09 14:35:31 +0200
From: @njnes
The query cache didn't handle the different schemas. This is fixed now.
## Comment 10237
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2080219 at http://sourceforge.net/support/tracker.php?aid=2080219
| The conflict exist when the same tablename are in different | https://api.github.com/repos/MonetDB/MonetDB/issues/1823/comments | 0 | 2020-11-30T10:02:35Z | 2024-06-27T11:32:33Z | https://github.com/MonetDB/MonetDB/issues/1823 | 753,335,334 | 1,823 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 10:23:31 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2009-02-09 03:07:00 +0100
## Comment 10228
Date: 2008-08-28 10:23:31 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1. setup
drop table A;
drop table B;
CREATE TABLE A
(a varchar(10),
b varchar(10));
CREATE TABLE B
(a varchar(10),
b varchar(10));
insert into a values('1','2');
insert into a values('2','2');
insert into b values('1','2');
insert into b values('3','2');
2. execute
update A set a='a' where A.a not in (select B.a from B where A.b=B.b);
3. result
select * from a;
+---+--+
| a |b |
+===+==+
| a |2 |
| a |2 |
+---+--+
4.question:
The result should be only "a 2".
## Comment 10229
Date: 2008-08-28 12:51:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
seems related to 2080151 The result of SELECT NOT is wrong
(added test table_update.SF-2080207.sql
## Comment 10230
Date: 2008-11-17 19:03:11 +0100
From: @romulogoncalves
Another additional information. If I do the following select (extracted from the update query) for the non_algebra version:
select * from A where A.a not in (select B.a from B where A.b=B.b);
I get:MAPI = monetdb@localhost:50000
QUERY = select * from A where A.a not in (select B.a from B where A.b=B.b);
ERROR = !MALException:batstr.CMDcompare!=:requires bats of identical size
However, in the algebra version I get the correct result:
% sys.a, sys.a table_name
% a, b name
% varchar, varchar type
% 1, 1 length
[ "2", "2" ]
## Comment 10231
Date: 2008-12-01 15:44:39 +0100
From: @romulogoncalves
This bug is fixed in the current branch of M5-SQL without using the algebra version.
It will not be closed because it is not fixed in the stable branch...
What happen to the propagation? Or was the fix only checked in on the current branch?
## Comment 10232
Date: 2009-02-09 15:07:00 +0100
From: @romulogoncalves
The algebra version became the default one in the stable branch as well.
So the bug is fixed and it can be closed.
## Comment 10233
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2080207 at http://sourceforge.net/support/tracker.php?aid=2080207
| The sub SELECT can't identify the outer table | https://api.github.com/repos/MonetDB/MonetDB/issues/1822/comments | 0 | 2020-11-30T10:02:32Z | 2024-06-27T11:32:32Z | https://github.com/MonetDB/MonetDB/issues/1822 | 753,335,288 | 1,822 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 10:06:53 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:37:14 +0200
## Comment 10222
Date: 2008-08-28 10:06:53 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A
(A DECIMAL(5));
INSERT INTO A VALUES (12);
INSERT INTO A VALUES (20);
INSERT INTO A VALUES (40);
INSERT INTO A VALUES (12);
2.execute:
SELECT COUNT(*)
FROM A
WHERE a BETWEEN 11.999 AND 12 OR
a BETWEEN 19.999 AND 2.001E1;
3.question:
The result should be 3
## Comment 10223
Date: 2008-08-28 12:46:07 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Did you mean the parser has problems with the 2.001E1 ?
## Comment 10224
Date: 2008-08-28 12:46:56 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
added test select_between_wrong_result.SF-2080189.sql
## Comment 10225
Date: 2008-08-29 09:46:04 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
forget my remark about parsing. I forgot to correctly remove the 2.execute part.
## Comment 10226
Date: 2008-09-09 14:37:14 +0200
From: @njnes
fixed by fixes in the type system.
## Comment 10227
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2080189 at http://sourceforge.net/support/tracker.php?aid=2080189
| The result of SELECT ... BETWEEN is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1821/comments | 0 | 2020-11-30T10:02:29Z | 2024-06-27T11:32:31Z | https://github.com/MonetDB/MonetDB/issues/1821 | 753,335,228 | 1,821 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 09:52:25 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:38:30 +0200
## Comment 10218
Date: 2008-08-28 09:52:25 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (
a varchar(10)
);
INSERT INTO A VALUES ('a1');
INSERT INTO A VALUES ('a2');
INSERT INTO A VALUES ('a3');
2.execute:
SELECT a FROM A
WHERE a < (SELECT a FROM A WHERE a = 'a4')
AND a IN (SELECT a FROM A);
3.result:
+----+
| a |
+====+
| a1 |
| a2 |
| a3 |
+----+
4.question:
The count should be 0;
## Comment 10219
Date: 2008-08-28 12:43:17 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added test select_in_wrong_result.SF-2080168.sql
## Comment 10220
Date: 2008-09-09 14:38:30 +0200
From: @njnes
fixed handling of zero or one returning sub queries. The a < (empty result), wasn't correctly handled.
## Comment 10221
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2080168 at http://sourceforge.net/support/tracker.php?aid=2080168
| The result of SELECT ... IN is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1820/comments | 0 | 2020-11-30T10:02:26Z | 2024-06-27T11:32:30Z | https://github.com/MonetDB/MonetDB/issues/1820 | 753,335,177 | 1,820 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 09:44:22 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:39:26 +0200
## Comment 10214
Date: 2008-08-28 09:44:22 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (
a varchar(10)
);
INSERT INTO A VALUES ('a1');
INSERT INTO A VALUES ('a2');
CREATE TABLE B (
a varchar(10)
);
INSERT INTO B VALUES ('a1');
INSERT INTO B VALUES ('a2');
INSERT INTO B VALUES ('a3');
2.execute:
SELECT COUNT(*)
FROM A
WHERE NOT (A.a =
(SELECT B.a
FROM B
WHERE a > 'a4' ));
3.result:
+--------+
| count_ |
+========+
| 2 |
+--------+
4.question:
The count should be 0;
## Comment 10215
Date: 2008-08-28 12:39:47 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
Added test select_not_wrong_result.SF-2080151.sql
It seems to work correctly on the algebra backend (mclient -G)
The handling of the NOT in the binary algebra case goes wrong.
## Comment 10216
Date: 2008-09-09 14:39:26 +0200
From: @njnes
a sub query within a not wasn't correctly handled.
## Comment 10217
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2080151 at http://sourceforge.net/support/tracker.php?aid=2080151
| The result of SELECT NOT is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1819/comments | 0 | 2020-11-30T10:02:23Z | 2024-06-27T11:32:29Z | https://github.com/MonetDB/MonetDB/issues/1819 | 753,335,139 | 1,819 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 07:35:05 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2008-08-28 05:31:04 +0200
## Comment 10210
Date: 2008-08-28 07:35:05 +0200
From: @drstmane
Since Tuesday August 26 2008, i.e., after checkins on Monday August 25
2008, 64-bit MonetDB with 64-bit OIDs segfaults when shredding documents (via fn:doc()); see. e.g.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.mTests103/GNU.64.64.d.0-Fedora8/benchmarks_MBench/load_docs.err.00.html
## Comment 10211
Date: 2008-08-28 07:36:19 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
possibly related to
[ 2079937 ] PF: module pathfinder fails to load with 32-bit OIDs
http://sourceforge.net/tracker/index.php?func=detail&aid=2079937&group_id=56967&atid=482468
## Comment 10212
Date: 2008-08-28 17:31:04 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Fixed by reverting and then properly fixing the change to make ptr(nil) be equal to NULL.
## Comment 10213
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2079946 at http://sourceforge.net/support/tracker.php?aid=2079946
| PF: MonetDB segfaults when loading documents w/ 64-bit OIDs | https://api.github.com/repos/MonetDB/MonetDB/issues/1818/comments | 0 | 2020-11-30T10:02:19Z | 2024-06-27T11:32:28Z | https://github.com/MonetDB/MonetDB/issues/1818 | 753,335,090 | 1,818 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-28 07:28:50 +0200
From: @drstmane
To: @sjoerdmullender
Version: -- development
Last updated: 2008-09-01 10:23:19 +0200
## Comment 10206
Date: 2008-08-28 07:28:50 +0200
From: @drstmane
Since Tuesday August 26 2008, i.e., after checkins on Monday August 25 2008, module pathfinder fails to load when compiled with 32-bit OIDs:
Mtest.py: ERROR: ' Mserver "--config=/scratch/monet.GNU.64.32.d.1.22647/MonetDB4/.GNU.64.32.d.1-Fedora8/etc/MonetDB.conf" --debug=10 --set gdk_nr_threads=1 --set "monet_mod_path=/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/runtime/.libs:/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/runtime:/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/modules/pftijah/.libs:/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/modules/pftijah:/scratch/monet.GNU.64.32.d.1.22647/MonetDB4/.GNU.64.32.d.1-Fedora8/lib64/MonetDB4:/scratch/monet.GNU.64.32.d.1.22647/MonetDB4/.GNU.64.32.d.1-Fedora8/lib64/MonetDB4/lib:/scratch/monet.GNU.64.32.d.1.22647/MonetDB4/.GNU.64.32.d.1-Fedora8/lib64/MonetDB4/bin" --set "gdk_dbfarm=/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/dbfarm" --set "sql_logdir=/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/sql_logs" --set "xquery_logdir=/scratch/monet.GNU.64.32.d.1.22647/pathfinder/Fedora8/xquery_logs" --set mapi_open=true --set xrpc_open=true --set mapi_port=32638 --set xrpc_port=40252 --set monet_prompt= --trace --dbname=mTests "--dbinit=module(pathfinder);"` failed:
MonetDB Server v4.25.0
based on GDK v1.25.0
Copyright (c) 1993-2008, CWI. 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.5.0 loaded. http://dbappl.cs.utwente.nl/pftijah
!ERROR: CMDslice: argument out of range
!ERROR: CMDslice_int: operation failed.
!ERROR: interpret_params: rename(param 1): evaluation error.
quit();
Mtest.py: ERROR: Stopping Pathfinder testing as module "pathfinder" fails to load!
Cf.,
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.64.32.d.1-Fedora8/test10.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.64.32.d.1-Fedora8..2008.08.28_00-09-02/test10.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d.1-Fedora9..2008.08.28_00-09-02/test10.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.GNU.32.32.d.1-SunOS5.11..2008.08.28_00-09-02/test10.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Sun.32.32.d.1-SunOS5.11..2008.08.28_00-09-02/test10.out.html
http://monetdb.cwi.nl/testing/projects/monetdb/Current/pathfinder/.Int.32.32.d.1-Windows5.1..2008.08.28_00-09-02/test10.out.html
## Comment 10207
Date: 2008-08-28 07:36:24 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: YES
possibly related to
[ 2079946 ] PF: MonetDB segfaults when loading documents w/ 64-bit OIDs
http://sourceforge.net/tracker/index.php?func=detail&aid=2079946&group_id=56967&atid=482468
## Comment 10208
Date: 2008-09-01 10:23:19 +0200
From: @sjoerdmullender
Logged In: YES
user_id=43607
Originator: NO
Fixed by noting that you can't slice to INT_MAX if sizeof(int) == sizeof(BUN). slice checks the bounds and wants the bounds to be <= BUN_MAX which in this case is INT_MAX-1.
No test needed.
## Comment 10209
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2079937 at http://sourceforge.net/support/tracker.php?aid=2079937
| PF: module pathfinder fails to load with 32-bit OIDs | https://api.github.com/repos/MonetDB/MonetDB/issues/1817/comments | 0 | 2020-11-30T10:02:16Z | 2024-06-27T11:32:27Z | https://github.com/MonetDB/MonetDB/issues/1817 | 753,335,034 | 1,817 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:59:46 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 03:00:46 +0200
## Comment 10202
Date: 2008-08-26 09:59:46 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A
(COL1 INTEGER,
COL2 INTEGER);
INSERT INTO A VALUES (111,1112);
2.execute:
SELECT SUM(2 * COL1 * COL2)
FROM A;
3.result:
!SQLException:convert:value (1112) exceeds limits of type bte
## Comment 10203
Date: 2008-08-26 15:22:40 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
related to http://sourceforge.net/support/tracker.php?aid=2075157. Test included in to the auto_coersion_bug.SF-2075157.sql
## Comment 10204
Date: 2008-09-09 15:00:46 +0200
From: @njnes
fixed the auto coersion with binary function
## Comment 10205
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075310 at http://sourceforge.net/support/tracker.php?aid=2075310
| "SELECT SUM (:var * COL1 * COL2)" is not OK | https://api.github.com/repos/MonetDB/MonetDB/issues/1816/comments | 0 | 2020-11-30T10:02:12Z | 2024-06-27T11:32:26Z | https://github.com/MonetDB/MonetDB/issues/1816 | 753,334,990 | 1,816 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:52:26 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
CC: @sjoerdmullender
Duplicates: #1814
Last updated: 2010-07-09 15:12:05 +0200
## Comment 10199
Date: 2008-08-26 09:52:26 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
./mclient -lsql -dcjtest1 -t
sql>CREATE TABLE BASE (a CHAR(4));
sql>CREATE VIEW A AS
SELECT a FROM BASE;
2.execute:
./mclient -lsql -dcjtest2 -t
sql>CREATE VIEW A AS
SELECT a FROM cjtest1.A;
3.result:
!CREATE VIEW: no such schema 'cjtest1'
4.question:
Can't access other schema.
## Comment 10200
Date: 2008-08-26 10:08:46 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
Duplicate;
already reported as
[ 2075271 ] Can't access other schema's view
http://sourceforge.net/tracker/index.php?func=detail&aid=2075271&group_id=56967&atid=482468
Please note that your bug reports are highly appreciated, in particular since they provide detailed instructions to very simply reproduce the problem!
However, reporting the same problem twice (possibly by accident via hitting the <reload> button in your browser and thus re-posting the data) is neither "required" nor "convenient"
## Comment 10201
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075290 at http://sourceforge.net/support/tracker.php?aid=2075290
Bug has invalid status, setting status to "NEW".
Previous status was "DELETED".
## Comment 14326
Date: 2010-07-09 15:12:05 +0200
From: @sjoerdmullender
*** This bug has been marked as a duplicate of bug #1814 ***
| Can't access other schema's view | https://api.github.com/repos/MonetDB/MonetDB/issues/1815/comments | 0 | 2020-11-30T10:02:09Z | 2024-06-28T07:37:04Z | https://github.com/MonetDB/MonetDB/issues/1815 | 753,334,939 | 1,815 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:39:54 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2010-07-09 15:12:05 +0200
## Comment 10196
Date: 2008-08-26 09:39:54 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
./mclient -lsql -dcjtest1 -t
sql>CREATE TABLE BASE (a CHAR(4));
sql>CREATE VIEW A AS
SELECT a FROM BASE;
2.execute:
./mclient -lsql -dcjtest2 -t
sql>CREATE VIEW A AS
SELECT a FROM cjtest1.A;
3.result:
!CREATE VIEW: no such schema 'cjtest1'
4.question:
Can't access other schema.
## Comment 10197
Date: 2008-08-26 16:02:04 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
the -d option is for different databases, not for different schemas. Schema's should very well be found in the same database. Your cjtest1 schema isn't known in your cjtest2 database.
## Comment 10198
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075271 at http://sourceforge.net/support/tracker.php?aid=2075271
## Comment 14327
Date: 2010-07-09 15:12:05 +0200
From: @sjoerdmullender
*** Bug #1815 has been marked as a duplicate of this bug. ***
| Can't access other schema's view | https://api.github.com/repos/MonetDB/MonetDB/issues/1814/comments | 0 | 2020-11-30T10:02:05Z | 2024-06-28T07:37:03Z | https://github.com/MonetDB/MonetDB/issues/1814 | 753,334,895 | 1,814 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:38:19 +0200
From: Jane Chen <<cjnn>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:59:34 +0200
## Comment 10191
Date: 2008-08-26 09:38:19 +0200
From: Jane Chen <<cjnn>>
OS: RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE TMP (T1 CHAR (10));
INSERT INTO TMP (T1)
VALUES ( 'xxxx');
2.execute:
SELECT * FROM TMP
WHERE T1 = 'xxxx ';
3.result:
0 row selected.
4.question:
The result should be 1 row selected.
## Comment 10192
Date: 2008-08-26 10:10:21 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
See also
[ 2075085 ] The char and varchar compared wrong
http://sourceforge.net/tracker/index.php?func=detail&aid=2075085&group_id=56967&atid=482468
As Fabian already commented there, (trailing) spaces do matter unless explicitly trimmed-off.
## Comment 10193
Date: 2008-09-09 14:59:34 +0200
From: @njnes
we consider this a feature ;-). The old fixed size char semantics stem from the times where fixed sizes charaters strings really were stored in a fixed length array. With current unicode encodings this can hardly be true. The filling with spaces was more a result of the old storage structure then logical semantics. We think our current approach (ie not adding spaces) is much more logical semantics. We keep wat the user inserted.
## Comment 10194
Date: 2009-02-16 16:39:34 +0100
From: @drstmane
test added in sql/src/test/BugTracker-2008/Tests/About_CHAR.SF-2075268.*
works as expected
## Comment 10195
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075268 at http://sourceforge.net/support/tracker.php?aid=2075268
| About CHAR | https://api.github.com/repos/MonetDB/MonetDB/issues/1813/comments | 0 | 2020-11-30T10:02:02Z | 2024-06-27T11:32:23Z | https://github.com/MonetDB/MonetDB/issues/1813 | 753,334,852 | 1,813 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:37:21 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2009-08-06 11:26:31 +0200
## Comment 10186
Date: 2008-08-26 09:37:21 +0200
From: Qian Qiao <<drizzlerain>>
OS : RedHat Linux AS 4
GCC: 3.4.6
1.setup:
CREATE TABLE A (FIPS2 TIMESTAMP);
2.insert:
INSERT INTO A VALUES (
TIMESTAMP '1996-08-24 16:03:00.999999');
3.execute:
SELECT EXTRACT (SECOND FROM FIPS2)
* 1000000 - 999990 FROM A;
4.result:
+----------------------+
| sql_mul_second_fips2 |
+======================+
| -999990 |
+----------------------+
5.question:
The result is wrong.
## Comment 10187
Date: 2008-08-26 15:58:41 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
script added. extract_bug.SF-2075266.sql
The second(s) extract doesn't follow the specs here.
## Comment 10188
Date: 2009-02-15 21:43:56 +0100
From: @drstmane
test sql/src/test/BugTracker-2008/Tests/extract_bug.SF-2075266.* has been disabled in the Feb2009 release branch as it won't be fixed, there.
## Comment 10189
Date: 2009-08-06 23:26:31 +0200
From: @njnes
will be close in next feature release
## Comment 10190
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075266 at http://sourceforge.net/support/tracker.php?aid=2075266
| SELECT EXTRACT is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1812/comments | 0 | 2020-11-30T10:01:59Z | 2024-06-27T11:32:22Z | https://github.com/MonetDB/MonetDB/issues/1812 | 753,334,809 | 1,812 |
[
"MonetDB",
"MonetDB"
] | Date: 2008-08-26 09:23:20 +0200
From: Qian Qiao <<drizzlerain>>
To: @njnes
Version: -- development
Last updated: 2008-09-09 02:55:38 +0200
## Comment 10181
Date: 2008-08-26 09:23:20 +0200
From: Qian Qiao <<drizzlerain>>
OS: RedHat Linux AS 4
GCC:3.4.6
1.setup:
CREATE TABLE A (
COL1 INTEGER,
COL2 INTEGER,
COL3 INTEGER
);
2.insert:
INSERT INTO A VALUES(1000,-2000,NULL);
3.execute:
SELECT (-COL2+COL1)
FROM A
WHERE COL3 IS NULL;
4.result:
+----------------------+
| sql_add_sql_neg_col2 |
+======================+
| 6866 |
+----------------------+
5.question:
The result is wrong.
## Comment 10182
Date: 2008-08-26 09:44:25 +0200
From: @drstmane
Logged In: YES
user_id=572415
Originator: NO
This might help debugging:
sql>CREATE TABLE A (
more>COL1 INTEGER,
more>COL2 INTEGER,
more>COL3 INTEGER
more>);
sql>INSERT INTO A VALUES(1000,-2000,NULL);
Rows affected 1
sql>select * from A;
+------+------+-----+
| col1 |col2 |col3 |
+======+======+=====+
| 1000 |-2000 |null |
+------+------+-----+
sql>SELECT (-COL2+COL1)
more>FROM A;
+----------------------+
| sql_add_sql_neg_col2 |
+======================+
| 3000 |
+----------------------+
sql>SELECT (-COL2+COL1)
more>FROM A
more>WHERE COL3 IS NULL;
+----------------------+
| sql_add_sql_neg_col2 |
+======================+
| 6000 |
+----------------------+
sql>SELECT (-COL2+COL1)
more>FROM A
more>WHERE COL3 IS NULL;
+----------------------+
| sql_add_sql_neg_col2 |
+======================+
| 9000 |
+----------------------+
sql>SELECT (-COL2+COL1)
more>FROM A
more>WHERE COL3 IS NULL;
+----------------------+
| sql_add_sql_neg_col2 |
+======================+
| 12000 |
+----------------------+
## Comment 10183
Date: 2008-08-26 15:53:58 +0200
From: @njnes
Logged In: YES
user_id=43556
Originator: NO
related to http://sourceforge.net/support/tracker.php?aid=2075157. Test included in to the
auto_coersion_bug.SF-2075157.sql
## Comment 10184
Date: 2008-09-09 14:55:38 +0200
From: @njnes
handling of is NULL was wrong
## Comment 10185
Date: 2010-05-04 09:32:09 +0200
From: Pseudo user for Sourceforge import <<sfimport>>
This bug was previously known as tracker item 2075243 at http://sourceforge.net/support/tracker.php?aid=2075243
| the result of the account columns selected is wrong | https://api.github.com/repos/MonetDB/MonetDB/issues/1811/comments | 0 | 2020-11-30T10:01:55Z | 2024-06-27T11:32:21Z | https://github.com/MonetDB/MonetDB/issues/1811 | 753,334,758 | 1,811 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.