Mysql Lock with different isolation level

0. Preparation

CREATE TABLE `test` (
  `id` int(11) DEFAULT NULL,
  `name` varchar(100) DEFAULT NULL,
  UNIQUE KEY `test_id_IDX` (`id`) USING BTREE
) ENGINE=InnoDB DEFAULT CHARSET=utf8;

 

1. Read Committed with Unique Key

set session transaction isolation level read committed;
select * from test where id = 20 for update ;

 

select ENGINE, ENGINE_TRANSACTION_ID, THREAD_ID, OBJECT_SCHEMA, OBJECT_NAME, INDEX_NAME, LOCK_TYPE, LOCK_MODE, LOCK_STATUS, LOCK_DATA from performance_schema.data_locks;

We can see, in READ COMMITTED level, only the record with id = 20 is locked by RECORD LOCK. Others are free. (BTW, actually, in this case, there is an lock degradation happened, when retrived column exists Unique Key.)

2. Repeatable Read with Unique Key

set session transaction isolation level repeatable read;
select * from test where id = 20 for update ;

 In REPEATABLE READ level, a NEXT-KEY LOCK locked indexes between id (20, 30]. Any insertion statement like "INSERT INTO test.test(id, name) VALUES(21, 'bbb')" will be blocked, but insert (30, 'bbb') will be success.

 

评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

yexianyi

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值