Bugs item #1411926, was opened at 2006-01-22 09:36
Message generated for change (Comment added) made by stmane
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1411926&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: MonetDB4 CVS Head
Status: Pending
Resolution: Fixed
Priority: 7
Private: No
Submitted By: Martin Kersten (mlkersten)
Assigned to: Niels Nes (nielsnes)
Summary: SQL: crash on concurrent use
Initial Comment:
A simple script has been added to the monet4/ backend.
It supports simple testing of concurrent access to the
server.
The call
script.sh 2 0 20 example.sql
is sufficient to crash the server.
----------------------------------------------------------------------
>Comment By: Stefan Manegold (stmane)
Date: 2007-06-21 12:58
Message:
Logged In: YES
user_id=572415
Originator: NO
Romulo,
no need to be "shy", just go ahead, re-open the bug and make it a SQL bug,
if you think that's what should be done!
Stefan
----------------------------------------------------------------------
Comment By: Romulo Goncalves (romulog)
Date: 2007-06-21 12:47
Message:
Logged In: YES
user_id=1498628
Originator: NO
The bug needs to be open.
In M5 and M4-SQL stable crash with the script call.
I would like to move this script to the BugTracker in SQL because is not
specific bug of M4,
am I allowed to do that?
Regards,
Romulo
----------------------------------------------------------------------
Comment By: Stefan Manegold (stmane)
Date: 2006-11-06 00:25
Message:
Logged In: YES
user_id=572415
Status set to "pending", as we should check whether we could
add this script to the test collection.
----------------------------------------------------------------------
Comment By: Niels Nes (nielsnes)
Date: 2006-01-24 08:11
Message:
Logged In: YES
user_id=43556
concurrent access to the cache of catalog information wasn't
save. A second problem was that the query cache wasn't
cleared after each schema update, this is now fix by
checking a global
schema number at the start of each transaction.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1411926&group_id=56967
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
