What problems may result when the Mysqlbinlog version is inconsistent with Mysql _mysql

First of all to determine whether the current version is not mysqlbinlog version, when not the Mysqlbinlog version may cause problems, the following through the simulation of the scene to introduce the method, I hope to help you.

See the current Mysqlbinlog version of the method:

Mysqlbinlog--version
    mysqlbinlog Ver 3.3 for Linux at x86_64

Scene 1:mysql server for MySQL 5.6, the requirements of the Mysqlbinlog version of 3.4 and above, otherwise mysqlbinlog will be directly to the analysis of the error, has encountered many times before, but did not record the specific error information, seemingly and position location does not exist error information, and later converted to Mysqlbinlog 3.4 version with the rear can be resolved;

Scenario 2: Today to help customers do a DB recovery, backup files is a whole-library backup, recovery can only restore a certain db to a specific point in time. The method is as follows: MySQL plus the-o database_name parameter performs a full backup of the SQL file, and then parses the Binlog file of the specified library with the Mysqlbinlog-d database_name parameter, during which Mysqlbinlog is used, MySQL server is the 5.6,mysqlbinlog version is 3.3, the results of Mysqlbinlog parsing and no error, the implementation of the error, to see the resolution of the binlog have a lot of garbled, at first thought it was a character set, but did not find a half-day problem. Later tried to use the 3.4 version of the Mysqlbinlog to solve the problem, similar to the following figure garbled

Summary: When the MySQL server version is 5.6, be sure to remember to use the version >=3.4 Mysqlbinlog

Hope the above content is helpful to everybody.