• 's avatar
    Bug#46640: output from mysqlbinlog command in 5.1 breaks replication · 0ece5891
    authored
          
    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'.
    0ece5891
binlog.test 8.78 KB