Bug #3063 Don't mark an auto DROP TEMP TABLE as 'killed' in the binlog
Submitted: 4 Mar 2004 6:17 Modified: 4 Mar 2004 6:48
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S4 (Feature request)
Version: OS:4.0
Assigned to: Guilhem Bichot CPU Architecture:Any

[4 Mar 2004 6:17] Guilhem Bichot
Imagine you create a temp table, then issue a big SELECT, then kill the session during the SELECT.
In the binlog you get an automatic
with error code 1053 (="killed").
It would be better to always give an error code 0 (no error) to this DROP TEMPORARY TABLE, because it causes superfluous errors on the slave.

How to repeat:
see description.
[4 Mar 2004 6:48] 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:

Done in ChangeSet@1.1723.1.1, 2004-03-04 15:44:24+01:00, guilhem@mysql.com