Bugs item #2130710, was opened at 2008-09-26 20:36
Message generated for change (Comment added) made by stmane
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2130710&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: SQL/Core
>Group: SQL 2.24
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Hendrike Peetz (hpeetz)
Assigned to: Niels Nes (nielsnes)
>Summary: SQL: Aborting process

Initial Comment:
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 By: Stefan Manegold (stmane)
Date: 2008-09-26 21:00

Message:
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


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2130710&group_id=56967

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to