InnoDB鎖

1. Shared and Exclusive Locks

  1. Shared Lock(簡稱S Lock,共享鎖): 允許持有鎖的事務(wù)讀取行的操作
  2. Exclusive Lock(簡稱 X Lock,排他鎖): 允許持有鎖的事務(wù)進(jìn)行更新和刪除行的操作

事務(wù)T1如果持有記錄a的S Lock,此時事務(wù)t2也對記錄a進(jìn)行操作時伺帘,有兩種情況:

  • t2請求的是S Lock: t1,t2同時持有記錄a的S Lock
  • t2請求的是X Lock: t2會等待t1釋放鎖后代嗤,才能獲取X Lock

事務(wù)t1如果持有是記錄a的X Lock新锈,那么t2不管請求S 還是X Lock,都要等t1釋放鎖后才能去請求字管。

2. Intention Locks

Intention Locks是表級鎖黄橘,它表示之后的事務(wù)需要獲取哪種類型的行鎖(S亥至、X)悼沈。

  • Intention Shared Lock(IS Lock): 表示事務(wù)意圖在表中各個行上加一個共享鎖
  • Intention Exclusive Lock (IX Lock): 表示事務(wù)意圖在表中各個行上加一個排他鎖

我們可以通過SELECT ... FOR SHARESELECT ... FOR UPDATE 來獲取IS、IX Lock姐扮。

意圖鎖有以下限制:

  • 在事務(wù)可以獲取表中某行的共享鎖之前絮供,它必須首先獲取表上的IS鎖或更強(qiáng)的鎖(IX、S茶敏、X)壤靶。
  • 在事務(wù)可以獲取表中某行的獨(dú)占鎖之前,它必須首先獲取表上的IX鎖惊搏。

表級鎖的兼容性如下表:

\ X IX S IS
X Conflict Conflict Conflict Conflict
IX Conflict Compatible Conflict Compatible
S Conflict Conflict Compatible Compatible
IS Conflict Compatible Compatible Compatible

如果事務(wù)請求的鎖和先有鎖兼容贮乳,則獲取到鎖。否則恬惯,事務(wù)會等待向拆,直到現(xiàn)有的鎖被釋放。

2.1 SELECT ... FOR UPDATE

T1:

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test  for update;
+----+------+-------+
| id | name | name2 |
+----+------+-------+
|  1 | aa   | aa    |
|  2 | aA   | aA    |
+----+------+-------+
2 rows in set (0.03 sec)
 
 mysql>show engine innodb status;
 
------------
TRANSACTIONS
------------
Trx id counter 13049
Purge done for trx's n:o < 12996 undo n:o < 0 state: running but idle
History list length 113
LIST OF TRANSACTIONS FOR EACH SESSION:
...
---TRANSACTION 13048, ACTIVE 122 sec
2 lock struct(s), heap size 1136, 3 row lock(s)
MySQL thread id 19, OS thread handle 12056, query id 367 localhost ::1 root

表里就兩條記錄酪耳,但有三把行鎖 浓恳?
此時事務(wù)T2

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test for update;
Lock wait timeout exceeded; try restarting transaction


------------
TRANSACTIONS
------------
Trx id counter 13050
Purge done for trx's n:o < 12996 undo n:o < 0 state: running but idle
History list length 113
LIST OF TRANSACTIONS FOR EACH SESSION:
...
---TRANSACTION 13049, ACTIVE 11 sec starting index read
mysql tables in use 1, locked 1
LOCK WAIT 2 lock struct(s), heap size 1136, 1 row lock(s)
MySQL thread id 20, OS thread handle 2708, query id 370 localhost ::1 root Sending data
select * from test for update
------- TRX HAS BEEN WAITING 11 SEC FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 153 page no 4 n bits 72 index PRIMARY of table `localtest`.`test` trx id 13049 lock_mode X waiting
Record lock, heap no 4 PHYSICAL RECORD: n_fields 5; compact format; info bits 128
 0: len 4; hex 80000001; asc     ;;
 1: len 6; hex 000000002e5a; asc     .Z;;
 2: len 7; hex 010000011a096e; asc       n;;
 3: len 2; hex 6161; asc aa;;
 4: len 2; hex 6161; asc aa;;

------------------
---TRANSACTION 13048, ACTIVE 458 sec
2 lock struct(s), heap size 1136, 3 row lock(s)
MySQL thread id 19, OS thread handle 12056, query id 367 localhost ::1 root

3. Record Locks

Record Lock鎖的是索引。如果表沒有,InnoDB會建一個隱藏的聚簇索引颈将,并用該隱藏索引來鎖定記錄梢夯。

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test  where id=3 for update;
+----+------+-------+
| id | name | name2 |
+----+------+-------+
|  1 | aa   | aa    |
+----+------+-------+
1 row in set (0.03 sec)

------------
TRANSACTIONS
------------
mysql tables in use 1, locked 1
LOCK WAIT 3 lock struct(s), heap size 1136, 6 row lock(s), undo log entries 1
MySQL thread id 13, OS thread handle 14940, query id 586 localhost ::1 root updating
update test set name='test' where id =3
------- TRX HAS BEEN WAITING 2 SEC FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 312 page no 4 n bits 96 index PRIMARY of table `localtest`.`test` trx id 18709
lock_mode X locks rec but not gap waiting
Record lock, heap no 19 PHYSICAL RECORD: n_fields 7; compact format; info bits 128

4. Gap Locks

T1開啟一個事務(wù) 并執(zhí)行下面語句

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test;
+----+-----+
| id | num |
+----+-----+
|  1 |   1 |
|  3 |   3 |
|  5 |   5 |
|  9 |   9 |
| 10 |  10 |
| 15 |  15 |
| 20 |  20 |
+----+-----+
7 rows in set (0.03 sec)

mysql> select * from test where id between 5 and 10 for update;
+----+-----+
| id | num |
+----+-----+
|  5 |   5 |
|  9 |   9 |
| 10 |  10 |
+----+-----+
3 rows in set (0.03 sec)

T2

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> insert into test (id,num) values (100,100);
Query OK, 1 row affected (0.00 sec)

mysql> insert into test (id,num) values (4,4);
Query OK, 1 row affected (0.00 sec)

mysql> insert into test (id,num) values (6,6);
1205 - Lock wait timeout exceeded; try restarting transaction

····


MySQL thread id 20, OS thread handle 13996, query id 856 localhost ::1 root update
insert into test (id,num) values (6,6)
------- TRX HAS BEEN WAITING 42 SEC FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 313 page no 4 n bits 96 index PRIMARY 
of table `localtest`.`test` trx id 20874 lock_mode X locks gap before rec 
insert intention waiting

當(dāng)where xxx=? 條件的xxx不是索引或者非唯一索引,會鎖住前一個間隙

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test;
+----+-----+
| id | num |
+----+-----+
|  1 |   1 |
|  3 |   3 |
|  5 |   5 |
|  9 |   9 |
| 10 |  10 |
| 11 |  11 |
| 12 |  12 |
| 15 |  15 |
| 20 |  20 |
+----+-----+
9 rows in set (0.03 sec)

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test where num=15 for update;
+----+-----+
| id | num |
+----+-----+
| 15 |  15 |
+----+-----+
1 row in set (0.03 sec)

T2開啟一個事務(wù)吆鹤,并執(zhí)行下面insert語句厨疙,

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> insert into test (id,num) values (17,17);
Query OK, 1 row affected (0.00 sec)

mysql> insert into test (id,num) values (16,16);
Query OK, 1 row affected (0.00 sec)

mysql> insert into test (id,num) values (14,14);
1205 - Lock wait timeout exceeded; try restarting transaction
mysql> insert into test (id,num) values (22,15);
1205 - Lock wait timeout exceeded; try restarting transaction
mysql> insert into test (id,num) values (23,12);
1205 - Lock wait timeout exceeded; try restarting transaction
····

MySQL thread id 20, OS thread handle 13996, query id 765 localhost ::1 root update
insert into test (id,num) values (14,14)
------- TRX HAS BEEN WAITING 41 SEC FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 313 page no 6 n bits 88 index num of table `localtest`.`test` trx id 20832 
lock_mode X locks gap before rec insert intention waiting
Record lock, heap no 12 PHYSICAL RECORD: n_fields 2;
compact format; info bits 0
 0: len 4; hex 8000000f; asc     ;;
 1: len 4; hex 8000000f; asc     ;;

上面的情況鎖住的區(qū)間是[12,15]

檢索條件必須有索引,沒有索引的話,會鎖定整張表所有的記錄
T1

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> select * from test;
+----+-----+
| id | num |
+----+-----+
|  1 |   1 |
|  3 |   3 |
|  5 |   5 |
|  9 |   9 |
| 10 |  10 |
| 15 |  15 |
| 20 |  20 |
+----+-----+
7 rows in set (0.03 sec)

mysql> select * from test where num=15 for update;
+----+-----+
| id | num |
+----+-----+
| 15 |  15 |
+----+-----+
1 row in set (0.04 sec)

T2

mysql> start transaction;
Query OK, 0 rows affected (0.00 sec)

mysql> insert into test (id,num) values (4,4);
1205 - Lock wait timeout exceeded; try restarting transaction
mysql> insert into test (id,num) values (100,100);
1205 - Lock wait timeout exceeded; try restarting transaction

MySQL thread id 20, OS thread handle 13996, query id 834 localhost ::1 root update
insert into test (id,num) values (4,4)
------- TRX HAS BEEN WAITING 24 SEC FOR THIS LOCK TO BE GRANTED:
RECORD LOCKS space id 313 page no 4 n bits 96 index PRIMARY of table `localtest`.`test` trx id 20872 
lock_mode X locks gap before rec insert intention waiting
Record lock, heap no 5 PHYSICAL RECORD: n_fields 4; compact format; info bits 0
 0: len 4; hex 80000005; asc     ;;
 1: len 6; hex 000000005114; asc     Q ;;
 2: len 7; hex 01000001242299; asc     $" ;;
 3: len 4; hex 80000005; asc     ;;

PS: 如果指定區(qū)間[5,10],沒有值為5和10的記錄疑务。insert 數(shù)據(jù)的時候沾凄,gap locks 會擴(kuò)大到就近的存在記錄的范圍。如擴(kuò)大到[3,15]

5. Insert Intention Locks

不同數(shù)據(jù)插入到相同索引間隙不需要等待知允,互不影響撒蟀。

6. Next-Key Locks

InnoDB在REPEATABLE READ事務(wù)隔離級別下,默認(rèn)開啟温鸽。其實(shí)就是record lock 和gap lock 組合使用保屯。
官方文檔寫的范圍

假設(shè)索引包含值10,11,13和20,

(negative infinity, 10]
(10, 11]
(11, 13]
(13, 20]
(20, positive infinity)
?著作權(quán)歸作者所有,轉(zhuǎn)載或內(nèi)容合作請聯(lián)系作者
  • 序言:七十年代末,一起剝皮案震驚了整個濱河市涤垫,隨后出現(xiàn)的幾起案子姑尺,更是在濱河造成了極大的恐慌,老刑警劉巖蝠猬,帶你破解...
    沈念sama閱讀 218,284評論 6 506
  • 序言:濱河連續(xù)發(fā)生了三起死亡事件切蟋,死亡現(xiàn)場離奇詭異,居然都是意外死亡榆芦,警方通過查閱死者的電腦和手機(jī)柄粹,發(fā)現(xiàn)死者居然都...
    沈念sama閱讀 93,115評論 3 395
  • 文/潘曉璐 我一進(jìn)店門,熙熙樓的掌柜王于貴愁眉苦臉地迎上來匆绣,“玉大人驻右,你說我怎么就攤上這事∑榇荆” “怎么了堪夭?”我有些...
    開封第一講書人閱讀 164,614評論 0 354
  • 文/不壞的土叔 我叫張陵,是天一觀的道長拣凹。 經(jīng)常有香客問我茵瘾,道長,這世上最難降的妖魔是什么咐鹤? 我笑而不...
    開封第一講書人閱讀 58,671評論 1 293
  • 正文 為了忘掉前任拗秘,我火速辦了婚禮,結(jié)果婚禮上祈惶,老公的妹妹穿的比我還像新娘雕旨。我一直安慰自己扮匠,他們只是感情好,可當(dāng)我...
    茶點(diǎn)故事閱讀 67,699評論 6 392
  • 文/花漫 我一把揭開白布凡涩。 她就那樣靜靜地躺著棒搜,像睡著了一般。 火紅的嫁衣襯著肌膚如雪活箕。 梳的紋絲不亂的頭發(fā)上力麸,一...
    開封第一講書人閱讀 51,562評論 1 305
  • 那天,我揣著相機(jī)與錄音育韩,去河邊找鬼克蚂。 笑死,一個胖子當(dāng)著我的面吹牛筋讨,可吹牛的內(nèi)容都是我干的埃叭。 我是一名探鬼主播,決...
    沈念sama閱讀 40,309評論 3 418
  • 文/蒼蘭香墨 我猛地睜開眼悉罕,長吁一口氣:“原來是場噩夢啊……” “哼赤屋!你這毒婦竟也來了?” 一聲冷哼從身側(cè)響起壁袄,我...
    開封第一講書人閱讀 39,223評論 0 276
  • 序言:老撾萬榮一對情侶失蹤类早,失蹤者是張志新(化名)和其女友劉穎,沒想到半個月后嗜逻,有當(dāng)?shù)厝嗽跇淞掷锇l(fā)現(xiàn)了一具尸體涩僻,經(jīng)...
    沈念sama閱讀 45,668評論 1 314
  • 正文 獨(dú)居荒郊野嶺守林人離奇死亡,尸身上長有42處帶血的膿包…… 初始之章·張勛 以下內(nèi)容為張勛視角 年9月15日...
    茶點(diǎn)故事閱讀 37,859評論 3 336
  • 正文 我和宋清朗相戀三年变泄,在試婚紗的時候發(fā)現(xiàn)自己被綠了令哟。 大學(xué)時的朋友給我發(fā)了我未婚夫和他白月光在一起吃飯的照片恼琼。...
    茶點(diǎn)故事閱讀 39,981評論 1 348
  • 序言:一個原本活蹦亂跳的男人離奇死亡妨蛹,死狀恐怖,靈堂內(nèi)的尸體忽然破棺而出晴竞,到底是詐尸還是另有隱情蛙卤,我是刑警寧澤,帶...
    沈念sama閱讀 35,705評論 5 347
  • 正文 年R本政府宣布噩死,位于F島的核電站颤难,受9級特大地震影響,放射性物質(zhì)發(fā)生泄漏已维。R本人自食惡果不足惜行嗤,卻給世界環(huán)境...
    茶點(diǎn)故事閱讀 41,310評論 3 330
  • 文/蒙蒙 一、第九天 我趴在偏房一處隱蔽的房頂上張望垛耳。 院中可真熱鬧栅屏,春花似錦飘千、人聲如沸。這莊子的主人今日做“春日...
    開封第一講書人閱讀 31,904評論 0 22
  • 文/蒼蘭香墨 我抬頭看了看天上的太陽。三九已至哥纫,卻和暖如春霉旗,著一層夾襖步出監(jiān)牢的瞬間,已是汗流浹背蛀骇。 一陣腳步聲響...
    開封第一講書人閱讀 33,023評論 1 270
  • 我被黑心中介騙來泰國打工厌秒, 沒想到剛下飛機(jī)就差點(diǎn)兒被人妖公主榨干…… 1. 我叫王不留,地道東北人松靡。 一個月前我還...
    沈念sama閱讀 48,146評論 3 370
  • 正文 我出身青樓简僧,卻偏偏與公主長得像,于是被迫代替她去往敵國和親雕欺。 傳聞我的和親對象是個殘疾皇子岛马,可洞房花燭夜當(dāng)晚...
    茶點(diǎn)故事閱讀 44,933評論 2 355

推薦閱讀更多精彩內(nèi)容

  • 原文地址:https://docs.oracle.com/cd/E17952_01/mysql-5.5-en/in...
    翼徳閱讀 2,511評論 0 4
  • 1. 鎖類型 鎖是數(shù)據(jù)庫區(qū)別與文件系統(tǒng)的一個關(guān)鍵特性,鎖機(jī)制用于管理對共享資源的并發(fā)訪問屠列。InnoDB使用的鎖類型...
    butterfly100閱讀 1,153評論 0 2
  • 1)自增鎖(AUTO-INC Locks)啦逆,表級鎖用于AUTO_INCREMENT的自增主鍵,MySQL 8.0....
    哈密朵閱讀 2,819評論 5 4
  • InnoDB Locking This section describes lock types used by ...
    誓言的夢閱讀 466評論 0 0
  • 所謂“修身”笛洛,便是求學(xué)問夏志。只有學(xué)到了知識才能明白自己志向,知識就是力量苛让;知識可以改變自己的命運(yùn)沟蔑,自己變得強(qiáng)大了才有...
    裴佳霞閱讀 588評論 2 0