Bug #70287 mysqlbinlog does nog recognize incompatible binlog format

Submitted:	10 Sep 2013 18:20	Modified:	11 Sep 2013 11:13
Reporter:	Daniël van Eeden	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Server: Command-line Clients	Severity:	S3 (Non-critical)
Version:	5.5	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
The mysqlbinlog tool does not check if the binlog format is compatible.

How to repeat:
1. Enable binlogs and CRC32 binlog checksums on MySQL 5.6.12
2. Create some data
3. Use mysqlbinlog from MySQL 5.5.30 to view the created binlog file.

Actual result:
Binlog contents with giberish

Expected result:
"The binlog format is newer than the format supported by this tool. Please upgrade mysqlbinlog"

MySQL 5.6 generates binlogs with format v4. If checksums were added it should increase the binlog version, but it doesn't. This makes it hard for a client to detect if it should be able to read the file, however it can use the mysql version in the binlog file instead of the format version with the risk that it isn't forward compatible.

Suggested fix:
Check if the binlog file has a higher version number than the mysqlbinlog tool.

Hello Daniel,

Thank you for the bug report.
Verified as described.

Thanks,
Umesh

Page generated in 0.048 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.