A large number of Binlog dump records are found in the slow log of the Mysql problem _mysql

There is a database on the line, and in slow log there are a number of records similar to the following:

 code as follows:

# time:130823 13:56:08
# User@host:repl[repl] @ slave [10.x.x.x]
# query_time:9.000833 lock_time:0.000000 rows_sent:1 rows_examined:1
SET timestamp=1377237368;
# Administrator Command:binlog Dump;

Every time I finish Binlog dump will be recorded, very uncomfortable looking (I have OCD, O (∩_∩) o ha), I have to think of ways to get rid of.
After the investigation, finally confirmed that there is a specific version of this phenomenon, currently found that the official 5.1.49 exists, estimated that the entire official 5.1.x will have this phenomenon.

Workaround:

Modify the MY.CNF configuration file to add or modify the following option:

Copy Code code as follows:

log-slow-admin-statements = 0

More deceptive, this option cannot be modified online in 5.1 and requires a reboot of the mysqld.
The manual explains this option as follows:

Copy Code code as follows:

Include Slow Administrative Statements The statements written to the slow query log. Administrative statements include ALTER table, ANALYZE table, CHECK table, CREATE INDEX, DROP index, OPTIMIZE table, and R Epair TABLE.

The manual also has the time which is not reliable, or the practice is genuine.