Bug #11373 mysqlbinlog on 5.0.6 on windows produces weird meta-output
Submitted: 16 Jun 2005 9:43 Modified: 10 Oct 2005 19:49
Reporter: Tobias Asplund Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: Command-line Clients Severity:S2 (Serious)
Version:5.0.6 OS:Windows (Windows)
Assigned to: Assigned Account CPU Architecture:Any

[16 Jun 2005 9:43] Tobias Asplund
Description:
Seems to be a problem with the binary format of the binlog where mysqlbinlog gets bogus numbers when trying to read binlogs.

How to repeat:
Start a server up on mysql 5.0.6 on Windows

C:\mysql\binlogs>mysqlbinlog binlog.000002
/*!40019 SET @@session.max_insert_delayed_threads=0*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
# at 4
#050616  9:33:50 server id 1  end_log_pos 98    Start: binlog v 4, server v5.0.6-beta-nt-log created 050616  9:33:50 at startup
# Warning: this binlog was not closed properly. Most probably mysqld crashed writing it.

ROLLBACK;
# at 98
#050616 10:20:52 server id 1  end_log_pos 185   Query   thread_id=15    exec_time=0
error_code=0
SET TIMESTAMP=1118913652;

######## LOOK HERE!!! #########
SET @@session.foreign_key_checks=67108864,  @@session.sql_auto_is_null=16384, @@session.u
nique_checks=134217728;
###########################

SET @@session.sql_mode=0;
SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collat
ion_server=8;
CREATE DATABASE `world`;
ROLLBACK;
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;

This of course will give errors if you try to do point-in-time recovery from a binlog since this isn't valid values for those options.
[10 Oct 2005 19:37] Tobias Asplund
This seems to be fixed by some other fix,
can't reproducec anymore in 5.0.13
[10 Oct 2005 19:49] Guilhem Bichot
duplicate of BUG#11567 I think.