Bug #5705 SET CHARATER_SET_SERVERetc will be lost if STOP SLAVE before following query
Submitted: 22 Sep 2004 17:05 Modified: 23 Sep 2004 11:08
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.1 OS:Any (all)
Assigned to: Guilhem Bichot CPU Architecture:Any

[22 Sep 2004 17:05] Guilhem Bichot
To propagate charset information between master and slave, starting from 4.1 master writes
to binlog before every query which needs it. As this makes two independent binlog query events, if STOP SLAVE interrupts the slave SQL thread between the two, then at restart the query will be executed without the SET.

How to repeat:
depends on timing (or you can use START SLAVE UNTIL to test).

Suggested fix:
modify one line in Query_log_event::exec_event().
[23 Sep 2004 11:08] Guilhem Bichot
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 bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

ChangeSet@1.2027, 2004-09-23 12:16:56+02:00, guilhem@mysql.com