0ece5891a2 Bug#46640: output from mysqlbinlog command in 5.1 breaks replication ... The BINLOG statement was sharing too much code with the slave SQL thread, introduced with the patch for Bug#32407. This caused statements to be logged with the wrong server_id, the id stored inside the events of the BINLOG statement rather than the id of the running server. Fix by rearranging code a bit so that only relevant parts of the code are executed by the BINLOG statement, and the server_id of the server executing the statements will not be overrided by the server_id stored in the 'format description BINLOG statement'.		2009-10-14 09:39:05 +08:00
..
binlog_tests	Bug#46640: output from mysqlbinlog command in 5.1 breaks replication	2009-10-14 09:39:05 +08:00
rpl_tests	BUG#44661: automerge local 5.1-bt bug branch --> local 5.1-bt up to date	2009-10-07 22:26:36 +01:00