mariadb/mysql-test/extra/binlog_tests
unknown f9c6730258 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'.

mysql-test/extra/binlog_tests/binlog.test:
  Added test to verify if the server_id stored in the 'format 
  description BINLOG statement' will override the server_id
  of the server executing the statements.
mysql-test/suite/binlog/r/binlog_row_binlog.result:
  Test result for bug#46640
mysql-test/suite/binlog/r/binlog_stm_binlog.result:
  Test result for bug#46640
sql/log_event.cc:
  Moved rows_event_stmt_clean() call from update_pos() to apply_event(). This in any case
  makes more sense, and is needed as update_pos() is no longer called when executing
  BINLOG statements.
  
  Moved setting of rli->relay_log.description_event_for_exec from 
  Format_description_log_event::do_update_pos() to 
  Format_description_log_event::do_apply_event()
sql/log_event_old.cc:
  Moved rows_event_stmt_clean() call from update_pos() to apply_event(). This in any case
  makes more sense, and is needed as update_pos() is no longer called when executing
  BINLOG statements.
sql/slave.cc:
  The skip flag is no longer needed, as the code path for BINLOG statement has been 
  cleaned up.
sql/sql_binlog.cc:
  Don't invoke the update_pos() code path for the BINLOG statement, as it contains code 
  that is redundant and/or harmful (especially setting thd->server_id).
2009-10-14 09:39:05 +08:00
..
binlog.test Bug#46640: output from mysqlbinlog command in 5.1 breaks replication 2009-10-14 09:39:05 +08:00
binlog_failure_mixing_engines.test BUG#47678 Changes to n-tables that happen early in a trans. are only flushed upon commit 2009-10-06 01:54:00 +01:00
binlog_insert_delayed.test BUG#38068: binlog_stm_binlog fails sporadically in pushbuild 2008-07-23 18:56:39 +02:00
binlog_truncate.test Bug #36763 2009-02-06 17:06:41 +01:00
blackhole.test Merging 5.1 main into 5.1-rpl 2008-10-23 21:27:09 +02:00
ctype_cp932.test Merge dl145h.mysql.com:/data0/mkindahl/mysql-5.0-rpl 2008-02-20 19:49:26 +01:00
ctype_cp932_binlog.test
ctype_ucs_binlog.test WL#4189 2007-12-12 18:19:24 +01:00
database.test Bug#41888: Test binlog.binlog_database causing binlog_innodb to fail on Pushbuild. 2009-01-12 18:45:35 -05:00
drop_temp_table.test BUG #46572 DROP TEMPORARY table IF EXISTS does not have a consistent behavior in ROW mode 2009-09-28 10:23:06 +08:00
innodb_stat.test Bug#37312 Make tests binlog_row_innodb_stat and binlog_stm_innodb_stat more robust 2008-09-22 15:15:52 -04:00
insert_select-binlog.test Merge bk-internal:/home/bk/mysql-5.1-new-maint 2007-06-07 15:21:52 -07:00
mix_innodb_myisam_binlog.test Update paths 2008-03-03 10:17:32 +01:00
mix_innodb_myisam_side_effects.test Merge pilot.mysql.com:/data/msvensson/mysql/mysql-5.1-rpl 2008-02-28 12:21:44 +01:00