File: gr_serializable_isolation.test

package info (click to toggle)
mysql-8.0 8.0.43-3
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 1,273,924 kB
  • sloc: cpp: 4,684,605; ansic: 412,450; pascal: 108,398; java: 83,641; perl: 30,221; cs: 27,067; sql: 26,594; sh: 24,181; python: 21,816; yacc: 17,169; php: 11,522; xml: 7,388; javascript: 7,076; makefile: 2,194; lex: 1,075; awk: 670; asm: 520; objc: 183; ruby: 97; lisp: 86
file content (123 lines) | stat: -rw-r--r-- 3,985 bytes parent folder | download
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
################################################################################
# Aim of the testcase is to check that GR successfully blocks the DMLs run with
# 'SERIALIZABLE' isolation mode.
# Test:
# 0. Start a server with GR.
# 1. Create table t1, temporary table temp1
# 2. Set isolation level to 'SERIALIZABLE'
# 3. Verify that DDLs are not blocked irrespective of trasaction isolation.
# 4. Verify that DMLs are blocked if isolation level is 'SERIALIZABLE'
# 5. Set isolation level to 'REPEATABLE-READ' and check that DMLs are allowed.
# 6. Clean-up
################################################################################

--source include/set_privilege_checks_user_as_system_user.inc
--source include/have_group_replication_plugin.inc
--source include/group_replication.inc
--echo #
--echo # Bug#21225075 GROUP REPLICATION MAY CAUSE INCONSISTENCIES IF SERIALIZABLE IS ENABLED
--echo #
# Check that Group Replication does not allow any DML transactions if they are run with
# serializable isolation mode.

--let $rpl_connection_name= server1
--source include/rpl_connection.inc

SET SESSION sql_log_bin= 0;
CALL mtr.add_suppression("Transaction isolation level \\(tx_isolation\\) is set to SERIALIZABLE, which is not compatible with Group Replication");
SET SESSION sql_log_bin= 1;

--echo
--echo ## 1. Create table and insert some sample data to do some DML operations
CREATE TABLE t1 (c1 INT NOT NULL PRIMARY KEY) ENGINE=InnoDB;
INSERT INTO t1 VALUE (1);
CREATE TEMPORARY TABLE temp1 (c1 INT NOT NULL PRIMARY KEY) ENGINE=InnoDB;
INSERT INTO temp1 VALUE (1);

--echo
--echo ## 2. Change Isolation level to SERIALIZABLE.
SET @transaction_isolation_orig = @@session.transaction_isolation;
SET SESSION transaction_isolation='SERIALIZABLE';

--echo
--echo ## 3. DDLs are allowed irrespective of transaction isolation value
CREATE TABLE t2 (c1 INT NOT NULL PRIMARY KEY) ENGINE=InnoDB;

--echo
--echo ## 4. DMLs should be blocked if isolation level is SERIALIZABLE.
--error ER_BEFORE_DML_VALIDATION_ERROR
INSERT INTO t1 VALUES (2);

--error ER_BEFORE_DML_VALIDATION_ERROR
UPDATE t1 SET c1=c1+1;

--error ER_BEFORE_DML_VALIDATION_ERROR
DELETE FROM t1;

# Check that even DML operations on temporary tables are disallowed
# when isolation level is SERIALIZABLE
--error ER_BEFORE_DML_VALIDATION_ERROR
INSERT INTO temp1 VALUES (2);

--error ER_BEFORE_DML_VALIDATION_ERROR
UPDATE temp1 SET c1=c1+1;

--error ER_BEFORE_DML_VALIDATION_ERROR
DELETE FROM temp1;

DELIMITER |;

# Verify that if a procedure/function contains restricted DML operation, it
# will also throw error
CREATE PROCEDURE dml_procedure()
  BEGIN
  INSERT INTO t1 VALUES (2);
END |

CREATE FUNCTION dml_function() RETURNS INTEGER MODIFIES SQL DATA
  BEGIN
  INSERT INTO t1 VALUES (2);
  RETURN 1;
END|

DELIMITER ;|

--error ER_BEFORE_DML_VALIDATION_ERROR
CALL dml_procedure();

--error ER_BEFORE_DML_VALIDATION_ERROR
SELECT dml_function();


START TRANSACTION;
SET SESSION transaction_isolation='REPEATABLE-READ';
# Isolation value change is effective only from the next transaction.
# So this insert should be disallowed as the current transaction's
# isolation level is 'SERIALIZABLE';
--error ER_BEFORE_DML_VALIDATION_ERROR
INSERT INTO t1 VALUES (2);
COMMIT;

--let $assert_text= 'transaction_isolation should be REPEATABLE-READ'
--let $assert_cond= "[SELECT @@SESSION.transaction_isolation]" = "REPEATABLE-READ";
--source include/assert.inc

START TRANSACTION;
SET SESSION transaction_isolation='SERIALIZABLE';
--echo
--echo ## 5. Isolation value change is effective only from the next transaction.
--echo ##    So this insert should be allowed as the current transaction's
--echo ##    isolation level is 'REPEATABLE-READ';
INSERT INTO t1 VALUES (2);
COMMIT;

--echo
--echo ## 6. Cleaning up
DROP TABLE t1;
DROP TABLE t2;
DROP TABLE temp1;
DROP PROCEDURE dml_procedure;
DROP FUNCTION dml_function;
SET SESSION transaction_isolation=@transaction_isolation_orig;

--source include/group_replication_end.inc