| 1 |
# |
| 2 |
# This test validates the behavior of SQL_BEFORE_GTIDS and SQL_AFTER_GTIDS |
| 3 |
# of a slave's START SLAVE UNTIL command. Notably, it tests the following |
| 4 |
# scenarios: |
| 5 |
# 1. Single domain id in binary log with a single domain id in the UNTIL |
| 6 |
# condition |
| 7 |
# 2. Multiple domain ids in binary log with a single domain id in the UNTIL |
| 8 |
# condition |
| 9 |
# 3. Multiple domain ids in binary log with multiple domain ids in the UNTIL |
| 10 |
# condition |
| 11 |
# 4. A gap in the binary log with the UNTIL condition GTID pointed to the |
| 12 |
# missing transaction |
| 13 |
# 5. Syntax errors using the new options |
| 14 |
# |
| 15 |
# |
| 16 |
# References: |
| 17 |
# MDEV-27247: Add keywords "exclusive" and "inclusive" for START SLAVE UNTIL |
| 18 |
# |
| 19 |
|
| 20 |
--source include/have_innodb.inc |
| 21 |
--source include/have_log_bin.inc |
| 22 |
--source include/master-slave.inc |
| 23 |
|
| 24 |
--let $ssu_before_gtids=1 |
| 25 |
--source include/rpl_gtid_until_before_after_gtids.test |
| 26 |
|
| 27 |
--let $ssu_before_gtids=0 |
| 28 |
--source include/rpl_gtid_until_before_after_gtids.test |
| 29 |
|
| 30 |
--echo # |
| 31 |
--echo # Error Case 2: Providing both SQL_BEFORE_GTIDS and SQL_AFTER_GTIDS |
| 32 |
--echo # should result in a syntax error |
| 33 |
--connection slave |
| 34 |
--error ER_PARSE_ERROR |
| 35 |
START SLAVE UNTIL SQL_AFTER_GTIDS="0-1-1" SQL_BEFORE_GTIDS="0-1-1"; |
| 36 |
|
| 37 |
--echo # |
| 38 |
--echo # Cleanup |
| 39 |
--source include/save_master_gtid.inc |
| 40 |
|
| 41 |
--connection slave |
| 42 |
--source include/sync_with_master_gtid.inc |
| 43 |
|
| 44 |
--source include/rpl_end.inc |
| 45 |
--echo # End of rpl_gtid_until_before_gtids.test |