File: start_alter_mysqlbinlog_replay.result

package info (click to toggle)
mariadb 1%3A11.8.3-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 772,520 kB
  • sloc: ansic: 2,414,714; cpp: 1,791,394; asm: 381,336; perl: 62,905; sh: 49,647; pascal: 40,897; java: 39,363; python: 20,791; yacc: 20,432; sql: 17,907; xml: 12,344; ruby: 8,544; cs: 6,542; makefile: 6,145; ada: 1,879; lex: 1,193; javascript: 996; objc: 80; tcl: 73; awk: 46; php: 22
file content (42 lines) | stat: -rw-r--r-- 1,282 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
#
# Test verifies replay of binary logs which contain
# SA/RA/CA works fine.
# Generate a binary log with alter events and use mysqlbinlog tool to
# generate a sql file for replay. Source it on an clean master and
# verify the correctness. Use the latest binlog and repeat the same
# process mentioned above and observe replay works fine.
#
set global binlog_alter_two_phase = ON;
set binlog_alter_two_phase = ON;
create table t1 (f1 int primary key) engine=InnoDB;
create table t2 (f1 int primary key, constraint c1 foreign key (f1) references t1(f1)) engine=innodb;
alter table t2 add constraint c1 foreign key (f1) references t1(f1);
ERROR HY000: Can't create table `test`.`t2` (errno: 121 "Duplicate key on write or update")
drop table t2, t1;
select @@gtid_binlog_state;
@@gtid_binlog_state
0-1-5
FLUSH LOGS;
# reset the binlog
RESET MASTER;
# execute the binlog
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
0-1-5
FLUSH LOGS;
# Replay 1: One more time to simulate S->S case
RESET MASTER;
# execute the binlog
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
0-1-5
FLUSH LOGS;
# Replay 2: One more time to simulate S->S case
RESET MASTER;
# execute the binlog
SELECT @@gtid_binlog_state;
@@gtid_binlog_state
0-1-5
# clean up
RESET MASTER;
set global binlog_alter_two_phase=0;