Bug #3081 if an INSERT DELAYED is killed, it is binlogged as killed but it's not needed
Submitted: 6 Mar 2004 6:48 Modified: 8 Mar 2004 5:51
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[6 Mar 2004 6:48] Guilhem Bichot
Killing an INSERT DELAYED thread happens when FLUSH TABLES, OPTIMIZE TABLE...
In this case the thread writes all its pending rows (to the table and to the binlog) and terminates.
So the slave has nothing to worry about: just need to execute the INSERTs written into the binary log.
For that reason, the INSERT DELAYED should not be logged with a 1053 error code (the "killed" error code) but zero instead.

How to repeat:
Not obvious; see description.
[8 Mar 2004 5:51] Guilhem Bichot
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 bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Fixed in ChangeSet@1.1727.2.1, 2004-03-08 14:47:13+01:00, guilhem@mysql.com