Bug #67643 Increase mysqlbinlog version (3.4 or something higher than 3.3) in MySQL 5.6

• Submitted: 20 Nov 2012 1:22
• Modified: 3 Apr 2013 9:58
• Reporter: Yoshinori Matsunobu (OCA)
• Status: Closed
• Category: MySQL Server: Command-line Clients
• Severity: S4 (Feature request)
• Version: 5.6
• OS: Any
• Assigned to: MySQL Verification Team
• CPU Architecture: Any

[20 Nov 2012 1:22] Yoshinori Matsunobu

Description:
mysqlbinlog version is 3.2 in MySQL 5.0, 3.3 in MySQL 5.1 and 5.5, and 3.3 in MySQL 5.6. This is problematic since MySQL 5.6 adds new binlog format such as checksums. For example, mysqlbinlog in 5.5 or older MySQL can't parse binlog events generated in MySQL 5.6.

So when parsing binlog events generated in MySQL 5.6, we need to make sure to use mysqlbinlog in 5.6, not in 5.5 or older version. Increasing mysqlbinlog version in 5.6 will make it easy.

How to repeat:
mysqlbinlog --version

Suggested fix:
Increase mysqlbinlog version to 3.4 or something higher than 3.3 in 5.6

[20 Nov 2012 4:10] MySQL Verification Team

Verified as described.

Thank you for the feature request.

[3 Apr 2013 9:58] Jon Stephens

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 bug fix. More information about accessing the source trees is available at

    http://dev.mysql.com/doc/en/installing-source.html

[3 Apr 2013 10:01] Jon Stephens

Documented fix in the 5.6.11 changelog:

        The version number reported by mysqlbinlog has been increased to 3.4.
      

Closed.