Bug #11722 | InnoDB crash with prepared statement and committed transaction | ||
---|---|---|---|
Submitted: | 4 Jul 2005 13:03 | Modified: | 4 Jul 2005 14:27 |
Reporter: | Georg Richter | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server | Severity: | S1 (Critical) |
Version: | 5.0.9-beta | OS: | Linux (Linux) |
Assigned to: | CPU Architecture: | Any |
[4 Jul 2005 13:03]
Georg Richter
[4 Jul 2005 13:14]
Marko Mäkelä
This can't be repeated from the mysql client. I'm trying to link the program against the client library (never done that before).
[4 Jul 2005 13:32]
Marko Mäkelä
I couldn't repeat this with a few days old version (ChangeSet@1.1973.1.35, 2005-06-29 16:41:49+02:00, msvensson@neptunus).
[4 Jul 2005 14:19]
Georg Richter
Bug was fixed on Friday already by Heikki (fix for #3300.)
[4 Jul 2005 14:27]
Heikki Tuuri
Georg, the bug fix of bug #3300 concerned optimization of locking if innodb_locks_unsafe_for_binlog is set. I do not see how it could fix this crash. There are several crash bugs with prepared statements: http://bugs.mysql.com/search.php?search_for=prepared&limit=90&order_by=id&direction=DESC&c... and it may be some of the fixes has been pushed in the past few days. I am closing this bug report now. Regards, Heikki