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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
|
--echo #
--echo # Bug #28799261 IODKU UNNECESSARILY GAP-LOCKS SECONDARY INDEXES
--echo # AFTER DUPLICATE IS ALREADY FOUND
--echo #
--source include/count_sessions.inc
#Test 1
CREATE TABLE t1 (a INT UNIQUE KEY, b INT UNIQUE KEY, c INT) ENGINE = InnoDB;
SHOW CREATE TABLE t1;
--echo # Scenario 1: Serialized transactions (trx1, trx2)
INSERT INTO t1 VALUES (1, 1, 1);
SELECT * FROM t1;
--echo # Transaction trx1
START TRANSACTION;
INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Transaction trx2
START TRANSACTION;
INSERT INTO t1 VALUES (2, 1, 2) ON DUPLICATE KEY UPDATE c=VALUES(c);
INSERT INTO t1 VALUES (2, 3, 4) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Result:
SELECT * FROM t1;
--echo # Cleanup
DROP TABLE t1;
#Test 2
CREATE TABLE t1 (a INT UNIQUE KEY, b INT UNIQUE KEY, c INT) ENGINE = InnoDB;
SHOW CREATE TABLE t1;
--echo # Scenario 2: Serialized transactions (trx2, trx1)
INSERT INTO t1 VALUES (1, 1, 1);
SELECT * FROM t1;
--echo # Transaction trx2
START TRANSACTION;
INSERT INTO t1 VALUES (2, 1, 2) ON DUPLICATE KEY UPDATE c=VALUES(c);
INSERT INTO t1 VALUES (2, 3, 4) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Transaction trx1
START TRANSACTION;
INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Result:
SELECT * FROM t1;
--echo # Cleanup
DROP TABLE t1;
--echo #
--echo # Bug #11758237 INSERT ON DUPLICATE KEY UPDATE SOMETIMES
--echo # WRITES BINLOG POSITION INCORRECT
--echo #
CREATE TABLE t1 (a INT UNIQUE KEY, b INT UNIQUE KEY, c INT) ENGINE = InnoDB;
SHOW CREATE TABLE t1;
# Following two lines are added because of Bug#28523025
# We don't really care about tt's content, nor about the exact body
# of the TRIGGER. What we care is that the mere fact of processing the
# TRIGGER before each inserted row, can impact the state of flags set
# for the transaction and table t1.
CREATE TABLE tt (i INT) ENGINE = InnoDB;
CREATE TRIGGER t1_bi BEFORE INSERT ON t1
FOR EACH ROW
INSERT INTO tt SELECT a as i FROM t1 WHERE a=0;
--echo # Scenario 3: Interleaved transactions (trx1 conflicts on index b)
INSERT INTO t1 VALUES (0,0,0), (1, 1, 1);
SELECT * FROM t1;
--echo # Connection default:
--echo # Transaction trx1:
START TRANSACTION;
INSERT INTO t1 VALUES (2, 1, 2) ON DUPLICATE KEY UPDATE c=VALUES(c);
SELECT * FROM t1;
--echo # Connection other:
--connect (other,localhost,root,,test,,)
--send
INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c);
--echo # Connection default:
--connection default
let $wait_condition=
SELECT COUNT(*) = 1 FROM information_schema.innodb_trx
WHERE trx_query =
'INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c)' AND
trx_operation_state = 'inserting' AND
trx_state = 'LOCK WAIT';
--source include/wait_condition.inc
INSERT INTO t1 VALUES (2, 3, 4) ON DUPLICATE KEY UPDATE c=VALUES(c);
SELECT * FROM t1;
COMMIT;
--echo # Connection other:
--connection other
reap;
--echo # Connection default:
connection default;
--echo # Result:
SELECT * FROM t1;
--echo # Cleanup
DROP TABLE t1;
DROP TABLE tt;
#Test 4
CREATE TABLE t1 (a INT UNIQUE KEY, b INT UNIQUE KEY, c INT) ENGINE = InnoDB;
SHOW CREATE TABLE t1;
--echo # Scenario 4: Serialized transactions (trx1, trx2)
INSERT INTO t1 VALUES (1, 1, 1);
SELECT * FROM t1;
--echo # Transaction trx1
START TRANSACTION;
INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Transaction trx2
START TRANSACTION;
INSERT INTO t1 VALUES (1, 2, 2) ON DUPLICATE KEY UPDATE c=VALUES(c);
INSERT INTO t1 VALUES (3, 2, 4) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Result:
SELECT * FROM t1;
--echo # Cleanup
DROP TABLE t1;
#Test 5
CREATE TABLE t1 (a INT UNIQUE KEY, b INT UNIQUE KEY, c INT) ENGINE = InnoDB;
SHOW CREATE TABLE t1;
--echo # Scenario 5: Serialized transactions (trx2, trx1)
INSERT INTO t1 VALUES (1, 1, 1);
SELECT * FROM t1;
--echo # Transaction trx2
START TRANSACTION;
INSERT INTO t1 VALUES (1, 2, 2) ON DUPLICATE KEY UPDATE c=VALUES(c);
INSERT INTO t1 VALUES (3, 2, 4) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Transaction trx1
START TRANSACTION;
INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Result:
SELECT * FROM t1;
--echo # Cleanup
DROP TABLE t1;
#Test 6
CREATE TABLE t1 (a INT UNIQUE KEY, b INT UNIQUE KEY, c INT) ENGINE = InnoDB;
SHOW CREATE TABLE t1;
--echo # Scenario 6: Interleaved transactions (trx1 conflicts on index a)
INSERT INTO t1 VALUES (1, 1, 1);
SELECT * FROM t1;
--echo # Connection default:
--echo # Transaction trx1:
START TRANSACTION;
INSERT INTO t1 VALUES (1, 2, 2) ON DUPLICATE KEY UPDATE c=VALUES(c);
SELECT * FROM t1;
--echo # Connection other:
connection other;
START TRANSACTION;
SET innodb_lock_wait_timeout = 1;
--error ER_LOCK_WAIT_TIMEOUT
INSERT INTO t1 VALUES (2, 2, 3) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Connection default:
--connection default
INSERT INTO t1 VALUES (3, 2, 4) ON DUPLICATE KEY UPDATE c=VALUES(c);
COMMIT;
--echo # Result:
SELECT * FROM t1;
--echo # Cleanup
DROP TABLE t1;
#test 7
CREATE TABLE t1(f1 INT PRIMARY KEY,
f2 INT, f3 INT, UNIQUE KEY(f2))ENGINE=INNODB;
SHOW CREATE TABLE t1;
INSERT INTO t1(f1, f2, f3) VALUES(1, 10, 100);
SELECT * FROM t1;
--echo # Connection other:
connection other;
START TRANSACTION;
INSERT INTO t1 VALUES(2, 10, 200) ON DUPLICATE KEY UPDATE f3 = 120;
--echo # Connection default
connection default;
START TRANSACTION;
SET innodb_lock_wait_timeout = 1;
--error ER_LOCK_WAIT_TIMEOUT
INSERT INTO t1 VALUES(2, 20, 300) ON DUPLICATE KEY UPDATE f3 = 500;
COMMIT;
--echo # Connection other:
--connection other
COMMIT;
--echo # Connection default
connection default;
--echo # Verify Results:
SELECT * FROM t1;
DROP TABLE t1;
disconnect other;
#Test 8
#Test added to cover the undo update path
CREATE TABLE t1(f1 INT AUTO_INCREMENT PRIMARY KEY, f2 INT, f3 INT,
UNIQUE KEY(f2),UNIQUE KEY(f3))ENGINE=INNODB;
INSERT INTO t1(f2,f3) VALUES(10, 100);
INSERT INTO t1(f2,f3) VALUES(20, 200);
--error ER_DUP_ENTRY
UPDATE t1 SET f2=30,f3=100 WHERE f2 = 20;
SELECT * FROM t1;
COMMIT;
DROP TABLE t1;
--source include/wait_until_count_sessions.inc
|
