File: lock_end_of_range.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 (645 lines) | stat: -rw-r--r-- 14,986 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
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
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
--echo #
--echo # Bug #29508068  UNNECESSARY NEXT-KEY LOCK TAKEN
--echo #

--source include/have_debug_sync.inc
--source include/not_hypergraph.inc  # Locks taken depend on the query plan chosen.

CREATE TABLE t1 (
  id INT NOT NULL,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

CREATE TABLE t2 (
  id INT NOT NULL,
  PRIMARY KEY (id DESC)
) ENGINE=InnoDB;

--let $TWO=2

SET @conditions =  CONCAT(
  '<=0 <1 <=1 <7 <=7 <=8 <9 <=9 <=10 ',
  '>=10 >9 >=9 >3 >=3 >=2 >1 >=1 >0'
);
let $conditions_cnt = `
  SELECT 1 + LENGTH(@conditions) - LENGTH(REPLACE(@conditions, ' ',''))
`;

--let $t=1
while($t <= 2)
{

  --eval INSERT INTO t$t VALUES (1),  (3), (4), (5), (6), (7),  (9)

  --eval ANALYZE TABLE t$t

  --let $c=1
  while($c <= $conditions_cnt)
  {
    let condition = `
      SELECT SUBSTRING_INDEX(SUBSTRING_INDEX(@conditions,' ',$c),' ',-1)
    `;

    --let $desc=0
    while($desc <= 1)
    {
      if($desc == 0)
      {
        --let $ord=ASC
      }
      if($desc == 1)
      {
        --let $ord=DESC
      }
      BEGIN;

      eval
        SELECT *
          FROM t$t FORCE INDEX (PRIMARY)
          WHERE id $condition
          ORDER BY id $ord
          FOR UPDATE;

      --sorted_result
      eval
        SELECT index_name,lock_type,lock_mode,lock_status,lock_data
          FROM performance_schema.data_locks
          WHERE object_name = 't$t';

      ROLLBACK;

      --inc $desc
    }

    --inc $c
  }

  --eval DROP TABLE t$t
  --inc $t
}

CREATE TABLE t1 (
  id1 INT NOT NULL,
  id2 INT NOT NULL,
  PRIMARY KEY (id1 ASC, id2 ASC)
) ENGINE=InnoDB;

CREATE TABLE t2 (
  id1 INT NOT NULL,
  id2 INT NOT NULL,
  PRIMARY KEY (id1 ASC, id2 DESC)
) ENGINE=InnoDB;

CREATE TABLE t3 (
  id1 INT NOT NULL,
  id2 INT NOT NULL,
  PRIMARY KEY (id1 DESC, id2 ASC)
) ENGINE=InnoDB;

CREATE TABLE t4 (
  id1 INT NOT NULL,
  id2 INT NOT NULL,
  PRIMARY KEY (id1 DESC, id2 DESC)
) ENGINE=InnoDB;

SET @conditions =  CONCAT(
  '<0 <1 <3 <=3 <=4 <5 <=5 ',
  '>6 >5 >3 >=3 >=2 >1 >=1'
);
let $conditions_cnt = `
  SELECT 1 + LENGTH(@conditions) - LENGTH(REPLACE(@conditions, ' ',''))
`;

--let $t = 1
while($t <= 4)
{
  eval
    INSERT INTO t$t (id1,id2) VALUES
    (1,1),(1,3),(1,5),(3,1),(3,3),(3,5),(5,1),(5,3),(5,5);

  --eval ANALYZE TABLE t$t

  --let $c = 1
  while($c <= $conditions_cnt)
  {
    let condition = `
      SELECT SUBSTRING_INDEX(SUBSTRING_INDEX(@conditions,' ',$c),' ',-1)
    `;
    --let $desc=0
    while($desc <= 1)
    {
      if($desc == 0)
      {
        --let $ord=ASC
      }
      if($desc == 1)
      {
        --let $ord=DESC
      }

      --let $field = 1
      while($field <= 2)
      {
        if($field == 1){
          --let $predicate=id1 $condition
          --let $order_column=id1
        }
        if($field == 2){
          --let $predicate=id1=3 AND id2 $condition
          --let $order_column=id2
        }
        BEGIN;

        eval
          SELECT *
            FROM t$t FORCE INDEX (PRIMARY)
            WHERE $predicate
            ORDER BY $order_column $ord
            FOR UPDATE;

        --sorted_result
        eval
          SELECT index_name,lock_type,lock_mode,lock_status,lock_data
            FROM performance_schema.data_locks
            WHERE object_name = 't$t';

        ROLLBACK;

        --inc $field
      }
      --inc $desc
    }

    --inc $c
  }

  --eval DROP TABLE t$t
  --inc $t
}

CREATE TABLE t1 (
  id VARCHAR(100) NOT NULL,
  PRIMARY KEY (id(1) ASC)
) ENGINE=InnoDB;

CREATE TABLE t2 (
  id VARCHAR(100) NOT NULL,
  PRIMARY KEY (id(1) DESC)
) ENGINE=InnoDB;

SET @conditions = CONCAT(
  '<="c" <="d" <"e" <"ee" <="ee" <="ec" <="ef" ',
  '>="g" >="f" >"e" >"ee" >="ee" >="ef" >="ec"'
);
let $conditions_cnt = `
  SELECT 1 + LENGTH(@conditions) - LENGTH(REPLACE(@conditions, ' ',''))
`;

--let $t = 1
while($t <= 2)
{

  eval
    INSERT INTO t$t
      VALUES ("aa"), ("bb"), ("cc"),   ("ee"),   ("gg"), ("hh"), ("ii");

  --eval ANALYZE TABLE t$t

  --let $c = 1
  while($c <= $conditions_cnt)
  {
    let condition = `
      SELECT SUBSTRING_INDEX(SUBSTRING_INDEX(@conditions,' ',$c),' ',-1)
    `;

    --let $desc=0
    while($desc <= 1)
    {
      if($desc == 0)
      {
        --let $ord=ASC
      }
      if($desc == 1)
      {
        --let $ord=DESC
      }
      BEGIN;

      eval
        SELECT *
          FROM t$t FORCE INDEX (PRIMARY)
          WHERE id $condition
          ORDER BY id $ord
          FOR UPDATE;

      --sorted_result
      eval
        SELECT index_name,lock_type,lock_mode,lock_status,lock_data
          FROM performance_schema.data_locks
          WHERE object_name = 't$t';

      ROLLBACK;

      --inc $desc
    }

    --inc $c
  }

  --eval DROP TABLE t$t
  --inc $t
}

CREATE TABLE t1 (
  id VARCHAR(100) NOT NULL,
  PRIMARY KEY (id(2) ASC)
) ENGINE=InnoDB;

CREATE TABLE t2 (
  id VARCHAR(100) NOT NULL,
  PRIMARY KEY (id(2) DESC)
) ENGINE=InnoDB;

SET @conditions = CONCAT(
  '<="c" <="d" <"e" <"ee" <="ee" <="ec" <="ef" ',
  '>="g" >="f" >"e" >"ee" >="ee" >="ef" >="ec"'
);
let $conditions_cnt = `
  SELECT 1 + LENGTH(@conditions) - LENGTH(REPLACE(@conditions, ' ',''))
`;

--let $t = 1
while($t <= 2)
{

  eval
    INSERT INTO t$t
      VALUES ("aaa"), ("bbb"), ("ccc"),   ("eee"),   ("ggg"), ("hhh"), ("iii");

  --eval ANALYZE TABLE t$t

  --let $c = 1
  while($c <= $conditions_cnt)
  {
    let condition = `
      SELECT SUBSTRING_INDEX(SUBSTRING_INDEX(@conditions,' ',$c),' ',-1)
    `;

    --let $desc=0
    while($desc <= 1)
    {
      if($desc == 0)
      {
        --let $ord=ASC
      }
      if($desc == 1)
      {
        --let $ord=DESC
      }
      BEGIN;

      eval
        SELECT *
          FROM t$t FORCE INDEX (PRIMARY)
          WHERE id $condition
          ORDER BY id $ord
          FOR UPDATE;

      --sorted_result
      eval
        SELECT index_name,lock_type,lock_mode,lock_status,lock_data
          FROM performance_schema.data_locks
          WHERE object_name = 't$t';

      ROLLBACK;

      --inc $desc
    }

    --inc $c
  }

  --eval DROP TABLE t$t
  --inc $t
}

# In this scenario, we test what happens if the last row in the range is locked
# by another transaction. In particular con1 locks row with id=7, and con2 tries
# to lock rows with id<=7. This scenario is interesting, because when con2 goes
# to waiting state AFTER it has already "seen" the end of the range, and when it
# "wakes up" (after con1 releases the lock) it tries to read the row again.
# A faulty implementation might fail on assert, not read the row, or fail to
# lock it properly on the second attempt.

CREATE TABLE t1 (
  id INT NOT NULL,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

INSERT INTO t1 VALUES (1),  (3), (4), (5), (6), (7),  (9);
ANALYZE TABLE t1;
--connect (con1,localhost,root,,)
--connect (con2,localhost,root,,)

--connection con1
  BEGIN;
  SELECT * FROM t1 WHERE id=7 FOR UPDATE;

--connection con2
  BEGIN;
  SET DEBUG_SYNC='lock_wait_will_wait SIGNAL con2_will_wait';
  --send SELECT * FROM t1 FORCE INDEX (PRIMARY) WHERE id<=7 FOR UPDATE;

--connection con1
  SET DEBUG_SYNC='now WAIT_FOR con2_will_wait';
  ROLLBACK;

--connection con2
  --reap

--connection default
--disconnect con1
--disconnect con2

DROP TABLE t1;

# In this scenario, we test what happens if the last row in the range is delete-
# -marked

CREATE TABLE t1 (
  id INT NOT NULL,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

INSERT INTO t1 VALUES (1),  (3), (4), (5), (6), (7),  (9);
ANALYZE TABLE t1;
SET GLOBAL innodb_purge_stop_now = ON;
DELETE FROM t1 WHERE id=7;


BEGIN;
SELECT * FROM t1 FORCE INDEX (PRIMARY) WHERE id<=7 FOR UPDATE;

--sorted_result
SELECT index_name, lock_type, lock_mode, lock_status, lock_data
  FROM performance_schema.data_locks
  WHERE object_name='t1';

ROLLBACK;
SET GLOBAL innodb_purge_run_now = ON;

DROP TABLE t1;

# In this scenario, we test what happens if the last row in the range is locked
# by another transaction and is delete-marked.
# In particular con1 locks row with id=7, and con2 tries
# to lock rows with id<=7. This scenario is interesting, because when con2 goes
# to waiting state AFTER it has already "seen" the end of the range, and when it
# "wakes up" (after con1 releases the lock) it tries to read the row again.
# A faulty implementation might fail on assert, not read the row, or fail to
# lock it properly on the second attempt.

CREATE TABLE t1 (
  id INT NOT NULL,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

INSERT INTO t1 VALUES (1),  (3), (4), (5), (6), (7),  (9);
ANALYZE TABLE t1;
SET GLOBAL innodb_purge_stop_now = ON;
DELETE FROM t1 WHERE id=7;

--connect (con1,localhost,root,,)
--connect (con2,localhost,root,,)

--connection con1
  BEGIN;
  SELECT * FROM t1 WHERE id=7 FOR UPDATE;

--connection con2
  BEGIN;
  SET DEBUG_SYNC='lock_wait_will_wait SIGNAL con2_will_wait';
  --send SELECT * FROM t1 FORCE INDEX (PRIMARY) WHERE id<=7 FOR UPDATE;

--connection con1
  SET DEBUG_SYNC='now WAIT_FOR con2_will_wait';
  ROLLBACK;

--connection con2
  --reap

--connection default
--disconnect con1
--disconnect con2

SET GLOBAL innodb_purge_run_now = ON;
DROP TABLE t1;

# In this scenario, we test what happens if the last row in the range is locked
# by another transaction and is delete-marked, and the other transaction
# undeletes this row, and then rolls back.
# In particular con1 locks row with id=7, and con2 tries
# to lock rows with id<=7. This scenario is interesting, because when con2 goes
# to waiting state AFTER it has already "seen" the end of the range, and when it
# "wakes up" (after con1 releases the lock) it tries to read the row again.
# A faulty implementation might fail on assert, not read the row, or fail to
# lock it properly on the second attempt.

CREATE TABLE t1 (
  id INT NOT NULL,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

INSERT INTO t1 VALUES (1),  (3), (4), (5), (6), (7),  (9);
ANALYZE TABLE t1;
SET GLOBAL innodb_purge_stop_now = ON;
DELETE FROM t1 WHERE id=7;

--connect (con1,localhost,root,,)
--connect (con2,localhost,root,,)

--connection con1
  BEGIN;
  INSERT INTO t1 VALUES (7);

--connection con2
  BEGIN;
  SET DEBUG_SYNC='lock_wait_will_wait SIGNAL con2_will_wait';
  --send SELECT * FROM t1 FORCE INDEX (PRIMARY) WHERE id<=7 FOR UPDATE;

--connection con1
  SET DEBUG_SYNC='now WAIT_FOR con2_will_wait';
  ROLLBACK;

--connection con2
  --reap

--connection default
--disconnect con1
--disconnect con2

SET GLOBAL innodb_purge_run_now = ON;
DROP TABLE t1;

# In this scenario, we test what happens if the last row in the range is locked
# by another transaction and is delete-marked, and the other transaction
# undeletes this row.
# In particular con1 locks row with id=7, and con2 tries
# to lock rows with id<=7. This scenario is interesting, because when con2 goes
# to waiting state AFTER it has already "seen" the end of the range, and when it
# "wakes up" (after con1 releases the lock) it tries to read the row again.
# A faulty implementation might fail on assert, not read the row, or fail to
# lock it properly on the second attempt.

CREATE TABLE t1 (
  id INT NOT NULL,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

INSERT INTO t1 VALUES (1),  (3), (4), (5), (6), (7),  (9);
ANALYZE TABLE t1;
SET GLOBAL innodb_purge_stop_now = ON;
DELETE FROM t1 WHERE id=7;

--connect (con1,localhost,root,,)
--connect (con2,localhost,root,,)

--connection con1
  BEGIN;
  INSERT INTO t1 VALUES (7);

--connection con2
  BEGIN;
  SET DEBUG_SYNC='lock_wait_will_wait SIGNAL con2_will_wait';
  --send SELECT * FROM t1 FORCE INDEX (PRIMARY) WHERE id<=7 FOR UPDATE;

--connection con1
  SET DEBUG_SYNC='now WAIT_FOR con2_will_wait';
  COMMIT;

--connection con2
  --reap

--connection default
--disconnect con1
--disconnect con2

SET GLOBAL innodb_purge_run_now = ON;
DROP TABLE t1;

# In this scenario, we test what happens when semi-consistent read is involved.
# In particular con1 locks row with id=6 while deleting it, and con2 tries
# to lock rows with id<=6 while updating them using semi-consistent read.
# This scenario is interesting, because when con2 notices it would have to
# wait, it avoids creating a waiting lock, and reports the old (non-deleted)
# version of the row to the higher layer, which then retries the read, this time
# with proper locking enabled - so it is interesting what would happen if con1
# have had commited the delete meanwhile.

CREATE TABLE t1 (
  id INT NOT NULL,
  val INT,
  PRIMARY KEY (id ASC)
) ENGINE=InnoDB;

INSERT INTO t1 (id,val) VALUES (1,1),(2,2) ,(3,3), (4,4), (5,5), (6,6),   (9,9);

--connect (con1,localhost,root,,)
--connect (con2,localhost,root,,)

--connection con1
  BEGIN;
  DELETE FROM t1 WHERE id=6;

--connection con2
  SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
  BEGIN;
  SET DEBUG_SYNC='
    semi_consistent_read_would_wait
    SIGNAL con2_would_wait
    WAIT_FOR con2_can_peek';
  SET DEBUG_SYNC='
    row_search_for_mysql_before_return
    SIGNAL con2_returns_row
    WAIT_FOR con2_can_return_row
    EXECUTE 6';
  --send UPDATE t1 SET val=13 WHERE id<=6

--connection con1

  --let i=1
  while($i < 6)
  {
    --echo Expecting row number $i
    SET DEBUG_SYNC='now WAIT_FOR con2_returns_row';
    SET DEBUG_SYNC='now SIGNAL con2_can_return_row';
    --inc $i
  }

  SET DEBUG_SYNC='now WAIT_FOR con2_would_wait';
  --sorted_result
  SELECT index_name, lock_type, lock_mode, lock_status, lock_data
    FROM performance_schema.data_locks
    WHERE object_name='t1';
  SET DEBUG_SYNC='now SIGNAL con2_can_peek';
  SET DEBUG_SYNC='now WAIT_FOR con2_returns_row';
  --sorted_result
  SELECT index_name, lock_type, lock_mode, lock_status, lock_data
    FROM performance_schema.data_locks
    WHERE object_name='t1';
  COMMIT;

  # Wait for purge to delete the delete-marked record
  --source include/wait_innodb_all_purged.inc

  --sorted_result
  SELECT index_name, lock_type, lock_mode, lock_status, lock_data
    FROM performance_schema.data_locks
    WHERE object_name='t1';
  SET DEBUG_SYNC='now SIGNAL con2_can_return_row';


--connection con2
  --reap
  --sorted_result
  SELECT index_name, lock_type, lock_mode, lock_status, lock_data
    FROM performance_schema.data_locks
    WHERE object_name='t1';
  ROLLBACK;

--connection default
--disconnect con1
--disconnect con2

DROP TABLE t1;
--echo #
--echo # Bug #30112238 - [INNODB] ASSERTION FAILURE: ROW0SEL.CC.*DIRECTION != 0
--echo #

CREATE TABLE t1 (
        id INT PRIMARY KEY
);

INSERT INTO t1 (id) VALUES (1), (2), (3), (4), (5), (6), (7), (8), (9);
ANALYZE TABLE t1;


--connect (view_keeper,localhost,root,,)
        BEGIN;
        SELECT * FROM t1;

--connection default

DELETE FROM t1 WHERE id<=5;

BEGIN;
--sorted_result
SELECT index_name, lock_type, lock_mode, lock_status, lock_data FROM performance_schema.data_locks WHERE object_name='t1';
SELECT id FROM t1 FORCE INDEX (PRIMARY) WHERE id<=5 FOR UPDATE;
--sorted_result
SELECT index_name, lock_type, lock_mode, lock_status, lock_data FROM performance_schema.data_locks WHERE object_name='t1';
COMMIT;

--disconnect view_keeper

DROP TABLE t1;