Bug #28953 | Using events in a replication let the slave crash. | ||
---|---|---|---|
Submitted: | 7 Jun 2007 17:49 | Modified: | 19 Jun 2007 13:29 |
Reporter: | Horst Hunger | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S1 (Critical) |
Version: | 5.1.19 | OS: | Linux (suse 10.1) |
Assigned to: | Damien Katz | CPU Architecture: | Any |
[7 Jun 2007 17:49]
Horst Hunger
[8 Jun 2007 7:10]
Sveta Smirnova
Thank you for the report. Verified as described using last BK sources.
[13 Jun 2007 20:26]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/28700 ChangeSet@1.2545, 2007-06-13 16:24:21-04:00, dkatz@damien-katzs-computer.local +3 -0 Bug #28953 Using events in a replication let the slave crash. Fixed where the slave code would try to update the Lex->sphead which is NULL on an "alter table" commands.
[16 Jun 2007 4:50]
Bugs System
Pushed into 5.1.20-beta
[19 Jun 2007 13:29]
Jon Stephens
Thank you for your bug report. This issue has been committed to our source repository of that product and will be incorporated into the next release. If necessary, you can access the source repository and build the latest available version, including the bug fix. More information about accessing the source trees is available at http://dev.mysql.com/doc/en/installing-source.html Documented bugfix in 5.1.20 changelog.