mariadb/mysql-test/suite/binlog/r
Mats Kindahl 8f95c5e183 Bug #44442: Incident events are silent in mysqlbinlog output
In the output from mysqlbinlog, incident log events were
represented as just a comment. Since the incident log event
represents an incident that could cause the contents of the
database to change without being logged to the binary log,
it means that if the SQL is applied to a server, it could
potentially lead to that the databases are out of sync.

In order to handle that, this patch adds the statement "RELOAD
DATABASE" to the SQL output for the incident log event. This will
require a DBA to edit the file and handle the case as apropriate
before applying the output to a server.

mysql-test/suite/binlog/t/binlog_incident-master.opt:
  Options file to cause server to generate an incident log
  event when executing a REPLACE.
mysql-test/suite/binlog/t/binlog_incident.test:
  Test to check that the incident log event is represented
  correctly in the output from mysqlbinlog.
sql/log_event.cc:
  The incident log event now ouput a "RELOAD DATABASE" instead
  of just a comment. RELOAD DATABASE is not an existing command
  and will generate a syntax error.
2009-05-11 13:32:38 +02:00
..
binlog_auto_increment_bug33029.result Bug #40559 assertion failed in check_binlog_magic 2009-03-06 20:19:29 +02:00
binlog_base64_flag.result
binlog_database.result merge: 5.1 -> 5.1-rpl 2009-01-23 13:22:05 +01:00
binlog_grant.result
binlog_incident.result Bug #44442: Incident events are silent in mysqlbinlog output 2009-05-11 13:32:38 +02:00
binlog_index.result merge: 5.1 -> 5.1-rpl 2009-01-23 13:22:05 +01:00
binlog_innodb.result Fix a few problems after latest bunch of InnoDB snapshot changes: 2009-01-08 03:06:54 +01:00
binlog_innodb_row.result Bug #40221 Replication failure on RBR + UPDATE the primary key 2008-12-08 17:07:08 +02:00
binlog_killed.result
binlog_killed_simulate.result
binlog_mix_innodb_stat.result
binlog_multi_engine.result Manual merge of 5.1 into 5.1-rpl 2008-10-24 14:51:06 +02:00
binlog_old_versions.result
binlog_row_binlog.result Manual merge. 2009-03-25 23:41:16 +04:00
binlog_row_ctype_cp932.result
binlog_row_ctype_ucs.result
binlog_row_drop_tmp_tbl.result
binlog_row_innodb_stat.result
binlog_row_insert_select.result
binlog_row_mix_innodb_myisam.result BUG#36763: TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. 2009-02-10 15:44:58 +01:00
binlog_sql_mode.result BUG#39526 sql_mode not retained in binary log for CREATE PROCEDURE 2009-02-28 09:35:18 +08:00
binlog_start_comment.result
binlog_statement_insert_delayed.result
binlog_stm_binlog.result Manual merge. 2009-03-25 23:41:16 +04:00
binlog_stm_blackhole.result Merging 5.1 main into 5.1-rpl 2008-10-23 21:27:09 +02:00
binlog_stm_ctype_cp932.result
binlog_stm_ctype_ucs.result
binlog_stm_drop_tmp_tbl.result
binlog_stm_innodb_stat.result
binlog_stm_insert_select.result
binlog_stm_mix_innodb_myisam.result BUG#36763: TRUNCATE TABLE fails to replicate when stmt-based binlogging is not supported. 2009-02-10 15:44:58 +01:00
binlog_stm_ps.result BUG#42640 mysqld crashes when unsafe statements are executed (STRICT_TRANS_TABLESmode) 2009-04-03 18:21:57 +00:00
binlog_stm_row.result merged 5.1-main -> 5.1-bugteam 2009-01-30 15:44:49 +02:00
binlog_tmp_table.result BUG#35583 mysqlbinlog replay fails with ERROR 1146 when temp tables are used 2009-01-28 14:35:12 +00:00
binlog_truncate_innodb.result Bug #36763 2009-02-06 17:06:41 +01:00
binlog_truncate_myisam.result Bug #36763 2009-02-10 22:26:37 +01:00
binlog_unsafe.result BUG#42640 mysqld crashes when unsafe statements are executed (STRICT_TRANS_TABLESmode) 2009-04-03 18:21:57 +00:00