Bug #21479 Binary log rotation cause "orphan" table map event
Submitted: 7 Aug 2006 12:29 Modified: 2 Jun 2007 17:22
Reporter: Mats Kindahl Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server: Row Based Replication ( RBR ) Severity:S2 (Serious)
Version:5.1 OS:Any (ALL)
Assigned to: Mats Kindahl CPU Architecture:Any

[7 Aug 2006 12:29] Mats Kindahl 
Description:
If statements that insert into a table is executed, it might be that the binary log is rotated between the table map event and the corresponding rows events.

How to repeat:
Execute several inserts in a row and set max_binlog_size to something small.

Suggested fix:
Only rotate the log at the end of a transaction or statement.
[7 Aug 2006 13:28] Mats Kindahl 
Duplicate of BUG#21474.
[10 Oct 2006 8:58] Lars Thalmann 
Not a duplicate of the other report.

The fix of this is mainly to make it easier for the user to know which
log file contains which transactions.  The bug is not causing any
illegal results.
[2 Jun 2007 17:22] Mats Kindahl 
It is possible to get an table map event last in a relay log but this is not a bug. A problem with a rotate in the middle of a group (e.g., just after a table map event) causing the group log position to be updated was fixed in BUG#23171.