mariadb/mysql-test/suite/innodb/r/gap_locks.result
Marko Mäkelä 33d41167c5 MDEV-24224 Gap lock on delete in 10.5 using READ COMMITTED
When MDEV-19544 (commit 1a6f470464)
simplified the initialization of the local variable
set_also_gap_locks, an inadvertent change was included.
Essentially, all code branches that are executed when
set_also_gap_locks hold must also ensure that
trx->isolation_level > TRX_ISO_READ_COMMITTED holds.
This was being violated in a few code paths.

It turns out that there is an even simpler fix: Remove the test
of thd_is_select() completely. In that way, the first part of
UPDATE or DELETE should work exactly like SELECT...FOR UPDATE.

thd_is_select(): Remove.
2020-11-18 10:27:18 +02:00

35 lines
1 KiB
Text

CREATE TABLE t1(a INT PRIMARY KEY, b VARCHAR(40), c INT, INDEX(b,c))
ENGINE=InnoDB;
INSERT INTO t1 VALUES (1,'1',1),(2,'2',1);
SET @save_locks= @@GLOBAL.innodb_status_output_locks;
SET GLOBAL INNODB_STATUS_OUTPUT_LOCKS = 'ON';
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE;
BEGIN;
DELETE FROM t1 WHERE b='2' AND c=2;
SHOW ENGINE INNODB STATUS;
Type Name Status
InnoDB 2 lock struct(s), 1 row lock(s)
ROLLBACK;
SET TRANSACTION ISOLATION LEVEL REPEATABLE READ;
BEGIN;
DELETE FROM t1 WHERE b='2' AND c=2;
SHOW ENGINE INNODB STATUS;
Type Name Status
InnoDB 2 lock struct(s), 1 row lock(s)
ROLLBACK;
SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
BEGIN;
DELETE FROM t1 WHERE b='2' AND c=2;
SHOW ENGINE INNODB STATUS;
Type Name Status
InnoDB 1 lock struct(s), 0 row lock(s)
ROLLBACK;
SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED;
BEGIN;
DELETE FROM t1 WHERE b='2' AND c=2;
SHOW ENGINE INNODB STATUS;
Type Name Status
InnoDB 1 lock struct(s), 0 row lock(s)
ROLLBACK;
SET GLOBAL INNODB_STATUS_OUTPUT_LOCKS = @save_locks;
DROP TABLE t1;