mirror of
https://github.com/MariaDB/server.git
synced 2025-01-28 01:34:17 +01:00
643738eec8
The INCIDENT_EVENT always caused slave error and abort, without checking --slave-skip-errors. Now, if error 1590, ER_SLAVE_INCIDENT is included in the --slave-skip-errors list, incident events will be ignored. This is a merge of this MySQL 5.6 patch: revision-id: frazer@mysql.com-20110314170916-ypgin17otj3ucx95 committer: Frazer Clement <frazer@mysql.com> timestamp: Mon 2011-03-14 17:09:16 +0000 message: Bug#11799671 NOT POSSIBLE TO SKIP INCIDENT ERRORS
28 lines
703 B
Text
28 lines
703 B
Text
--source include/master-slave.inc
|
|
--source include/have_debug.inc
|
|
|
|
--echo **** On Master ****
|
|
CREATE TABLE t1 (a INT);
|
|
|
|
INSERT INTO t1 VALUES (1),(2),(3);
|
|
SELECT * FROM t1;
|
|
|
|
# This will generate an incident log event and store it in the binary
|
|
# log before the replace statement.
|
|
REPLACE INTO t1 VALUES (4);
|
|
|
|
--sync_slave_with_master
|
|
|
|
# Now, we should have inserted the row into the table and the slave
|
|
# should be running. We should also have rotated to a new binary log.
|
|
|
|
SELECT * FROM t1;
|
|
source include/check_slave_is_running.inc;
|
|
|
|
connection master;
|
|
|
|
--echo Should have two binary logs here
|
|
--source include/show_binary_logs.inc
|
|
DROP TABLE t1;
|
|
--sync_slave_with_master
|
|
--source include/rpl_end.inc
|