MySQL Bugs: #31126: Dump for replication is not usable if tere are open TEMPORARY tables

Bug #31126	Dump for replication is not usable if tere are open TEMPORARY tables
Submitted:	21 Sep 2007 9:15	Modified:	25 Oct 2007 13:01
Reporter:	Martin Brennfleck	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	5.0.32-Debian_7etch1-log	OS:	Linux (Debian Etch)
Assigned to:		CPU Architecture:	Any
Tags:	dump, replication, temporary tables

Description:
Setting up a replication fails, when there is an open TEMPORARY table on the master during dumping the master with
 
# mysqldump --opt --master-data db_with_open_temorary_table > dump

after loading the dump in the slave server with 

# mysql db_with_open_temorary_table < dump

and starting the slave, the replication crashes, when there is an update on that temporary table. I know that in RBR in MySQL 5.1 that problem should be fixed.
Are you fixing that in SBR too?

How to repeat:
open temporary table
dump the database with --master-data
update the temporary table
use the dump for setting up a replication

Suggested fix:
Dump temporary tables too.

Thank you for the report.

But version 5.0.32 is quit old. Additionally I can not repeat described behaviour with current development sources. Please upgrade to current version 5.0.45, try with it and say us result.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".