mirror of
https://github.com/MariaDB/server.git
synced 2025-02-01 03:21:53 +01:00
127 lines
2.8 KiB
Text
127 lines
2.8 KiB
Text
set global innodb_table_locks=1;
|
|
select @@innodb_table_locks;
|
|
@@innodb_table_locks
|
|
1
|
|
connect con1,localhost,root,,;
|
|
connect con2,localhost,root,,;
|
|
drop table if exists t1;
|
|
set @@innodb_table_locks=1;
|
|
connection con1;
|
|
create table t1 (id integer, x integer) engine=INNODB;
|
|
insert into t1 values(0, 0);
|
|
set autocommit=0;
|
|
SELECT * from t1 where id = 0 FOR UPDATE;
|
|
id x
|
|
0 0
|
|
connection con2;
|
|
set autocommit=0;
|
|
lock table t1 write;
|
|
connection con1;
|
|
update t1 set x=1 where id = 0;
|
|
select * from t1;
|
|
id x
|
|
0 1
|
|
commit;
|
|
connection con2;
|
|
update t1 set x=2 where id = 0;
|
|
commit;
|
|
unlock tables;
|
|
connection con1;
|
|
select * from t1;
|
|
id x
|
|
0 2
|
|
commit;
|
|
drop table t1;
|
|
#
|
|
# Old lock method (where LOCK TABLE was ignored by InnoDB) no longer
|
|
# works when LOCK TABLE ... WRITE is used due to fix for bugs #46272
|
|
# "MySQL 5.4.4, new MDL: unnecessary and bug #37346 "innodb does not
|
|
# detect deadlock between update and alter table". But it still works
|
|
# for LOCK TABLE ... READ.
|
|
#
|
|
set @@innodb_table_locks=0;
|
|
create table t1 (id integer primary key, x integer) engine=INNODB;
|
|
insert into t1 values(0, 0),(1,1),(2,2);
|
|
commit;
|
|
SELECT * from t1 where id = 0 FOR UPDATE;
|
|
id x
|
|
0 0
|
|
connection con2;
|
|
set autocommit=0;
|
|
set @@innodb_table_locks=0;
|
|
# The following statement should block because SQL-level lock
|
|
# is taken on t1 which will wait until concurrent transaction
|
|
# is commited.
|
|
# Sending:
|
|
lock table t1 write;;
|
|
connection con1;
|
|
# Wait until LOCK TABLE is blocked on SQL-level lock.
|
|
# We should be able to do UPDATEs and SELECTs within transaction.
|
|
update t1 set x=1 where id = 0;
|
|
select * from t1;
|
|
id x
|
|
0 1
|
|
1 1
|
|
2 2
|
|
# Unblock LOCK TABLE.
|
|
commit;
|
|
connection con2;
|
|
# Reap LOCK TABLE.
|
|
unlock tables;
|
|
connection con1;
|
|
select * from t1 where id = 0 for update;
|
|
id x
|
|
0 1
|
|
connection con2;
|
|
# The below statement should not be blocked as LOCK TABLES ... READ
|
|
# does not take strong SQL-level lock on t1. SELECTs which do not
|
|
# conflict with transaction in the first connections should not be
|
|
# blocked.
|
|
lock table t1 read;
|
|
select * from t1;
|
|
id x
|
|
0 1
|
|
1 1
|
|
2 2
|
|
select * from t1 where id = 1 lock in share mode;
|
|
id x
|
|
1 1
|
|
unlock tables;
|
|
select * from t1;
|
|
id x
|
|
0 1
|
|
1 1
|
|
2 2
|
|
commit;
|
|
connection con1;
|
|
commit;
|
|
drop table t1;
|
|
#
|
|
#Bug#12842206 INNODB LOCKING REGRESSION FOR INSERT IGNORE
|
|
#fixed by re-fixing Bug#7975
|
|
#aka Bug#11759688 52020: InnoDB can still deadlock on just INSERT...
|
|
#
|
|
connection default;
|
|
CREATE TABLE t1 (a INT PRIMARY KEY, b INT NOT NULL) ENGINE=InnoDB;
|
|
INSERT INTO t1 VALUES(3,1);
|
|
BEGIN;
|
|
INSERT IGNORE INTO t1 VALUES(3,14);
|
|
Warnings:
|
|
Warning 1062 Duplicate entry '3' for key 'PRIMARY'
|
|
connection con1;
|
|
BEGIN;
|
|
INSERT IGNORE INTO t1 VALUES(3,23);
|
|
Warnings:
|
|
Warning 1062 Duplicate entry '3' for key 'PRIMARY'
|
|
SELECT * FROM t1 FOR UPDATE;
|
|
connection con2;
|
|
connection default;
|
|
COMMIT;
|
|
connection con1;
|
|
a b
|
|
3 1
|
|
COMMIT;
|
|
disconnect con1;
|
|
disconnect con2;
|
|
connection default;
|
|
DROP TABLE t1;
|