File: rpl_stm_auto_increment_bug33029.test

package info (click to toggle)
mariadb-10.0 10.0.32-0%2Bdeb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 476,064 kB
  • sloc: cpp: 1,400,131; ansic: 832,140; perl: 54,391; sh: 41,304; pascal: 32,365; yacc: 14,921; xml: 5,257; sql: 4,667; cs: 4,647; makefile: 4,555; ruby: 4,465; python: 2,292; lex: 1,427; java: 941; asm: 295; awk: 54; php: 22; sed: 16
file content (108 lines) | stat: -rw-r--r-- 2,812 bytes parent folder | download | duplicates (9)
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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
# BUG#33029 5.0 to 5.1 replication fails on dup key when inserting
# using a trig in SP

# For all 5.0 up to 5.0.58 exclusive, and 5.1 up to 5.1.12 exclusive,
# if one statement in a SP generated AUTO_INCREMENT value by the top
# statement, all statements after it would be considered generated
# AUTO_INCREMENT value by the top statement, and a erroneous INSERT_ID
# value might be associated with these statement, which could cause
# duplicate entry error and stop the slave.

source include/have_binlog_format_statement.inc;
source include/master-slave.inc;

CALL mtr.add_suppression("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT");
--connection slave
CALL mtr.add_suppression("Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT");
--connection master

CREATE TABLE t1 (id INT AUTO_INCREMENT PRIMARY KEY);
CREATE TABLE t2 (id INT AUTO_INCREMENT PRIMARY KEY);

delimiter //;

CREATE PROCEDURE p1()
BEGIN
   DECLARE ins_count INT DEFAULT 10; 

   WHILE ins_count > 0 DO
       INSERT INTO t1 VALUES (NULL);
       SET ins_count = ins_count - 1;
   END WHILE;

   DELETE FROM t1 WHERE id = 1;
   DELETE FROM t1 WHERE id = 2;
   DELETE FROM t2 WHERE id = 1;
   DELETE FROM t2 WHERE id = 2;
END//

CREATE PROCEDURE p2()
BEGIN
   INSERT INTO t1 VALUES (NULL);
   DELETE FROM t1 WHERE id = f1(3);
   DELETE FROM t1 WHERE id = f1(4);
   DELETE FROM t2 WHERE id = 3;
   DELETE FROM t2 WHERE id = 4;
END//

CREATE TRIGGER tr1 BEFORE DELETE
    ON t1 FOR EACH ROW 
    BEGIN
        INSERT INTO t2  VALUES (NULL);
    END//

CREATE FUNCTION f1 (i int) RETURNS int
    BEGIN
        INSERT INTO t2 VALUES (NULL);
        RETURN i;
    END//

delimiter ;//

# the $binlog_start will be used by the show_binlog_events.inc, so
# that we can skip binlog events we don't care
let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1);
CALL p1();
source include/show_binlog_events.inc;

echo # Result on master;
SELECT * FROM t1;
SELECT * FROM t2;

sync_slave_with_master;

echo # Result on slave;
SELECT * FROM t1;
SELECT * FROM t2;

connection master;

DROP TRIGGER tr1;

# the $binlog_start will be used by the show_binlog_events.inc, so
# that we can skip binlog events we don't care
let $binlog_start= query_get_value(SHOW MASTER STATUS, Position, 1);
CALL p2();
source include/show_binlog_events.inc;

echo # Result on master;
SELECT * FROM t1;
SELECT * FROM t2;

sync_slave_with_master;

echo # Result on slave;
SELECT * FROM t1;
SELECT * FROM t2;

# clean up
connection master;
disable_warnings;
DROP TABLE IF EXISTS t1, t2;
DROP PROCEDURE IF EXISTS p1;
DROP PROCEDURE IF EXISTS p2;
DROP FUNCTION IF EXISTS f1;
DROP TRIGGER IF EXISTS tr1;
enable_warnings;
sync_slave_with_master;
--source include/rpl_end.inc