Bugs item #2757104, was opened at 2009-04-13 02:01 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2757104&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: PF/compiler Group: Pathfinder CVS Head Status: Open Resolution: Postponed Priority: 5 Private: No Submitted By: Peter Boncz (boncz) Assigned to: Jan Rittinger (tsheyar) Summary: xiraf and other test queries fail (Y option) Initial Comment: XIRAF test queries 5 and 8 fail now http://wiki.pathfinder-xquery.org/wiki/index.php/XIRAF_testdata this can be circumvented by disabling a compile option (Y) in compile.c and recompiling, but should be fixed. bug report just as a reminder (can't we at least switch off Y by default though??) ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2009-04-13 11:35 Message: FYI: 7 of the Xiraf test fail wit the CVS development trunk due to a BAT propcheck error: ID: 2668437 "PF runtime: parent step produces not/wrongly sorted result" (https://sourceforge.net/tracker/?func=detail&aid=2668437&group_id=56967&atid=482468) (cf., http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/index_short.html http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/Int.64.32.d.1-Fedora8/large-testset/q525.out.00.html ... http://monetdb.cwi.nl/testing/intern/monetdb/Current/_intern_/Xiraf/.mTests103/GNU.64.64.d.1-Fedora8/large-testset/q538.out.00.html ) With the Feb2009 release branch, the Xiraf queries work fine, since I avoided the above mentioned BATprocheck error there (only); (Cf., http://monetdb.cwi.nl/testing/intern/monetdb/Stable/_intern_/Xiraf/.mTests103/index_short.html ) (ps: Xiraf testing result can only be accessed from within CWI, or with CWI intraweb access) ---------------------------------------------------------------------- Comment By: Jan Rittinger (tsheyar) Date: 2009-04-13 10:56 Message: In both example queries I can see no mistake. Option Y only provides plans that the physical planner has problems with---the staircase join algorithms are (unnecessarily) called with unique iter values. The solution (hopefully) will come soon: a MonetDB specific optimization that hides part of the job of optimization Y. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2757104&group_id=56967 ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
