官方文档:
![](https://img.haomeiwen.com/i3515770/b578e073cc8d627c.png)
表结构和数据
![](https://img.haomeiwen.com/i3515770/0e394c8666cdabc9.png)
验证1:
A会话:
![](https://img.haomeiwen.com/i3515770/3ba28f2bac458389.png)
B会话:
![](https://img.haomeiwen.com/i3515770/db94aa9e3b13f7d0.png)
![](https://img.haomeiwen.com/i3515770/039630d718f5fa2c.png)
查下锁持有情况:SHOW ENGINE INNODB STATUS;
![](https://img.haomeiwen.com/i3515770/4c5ef306e147d93e.png)
验证2:
A会话:
![](https://img.haomeiwen.com/i3515770/06588144094b1ccf.png)
B会话:
![](https://img.haomeiwen.com/i3515770/23b4f9f3dc7be20a.png)
查下锁持有情况:SHOW ENGINE INNODB STATUS;
![](https://img.haomeiwen.com/i3515770/4784fee65f56c56b.png)
结论:
当我们查询条件是a unique search condition时,只锁一行;不然就锁全表;
A会话:
B会话:
查下锁持有情况:SHOW ENGINE INNODB STATUS;
A会话:
B会话:
当我们查询条件是a unique search condition时,只锁一行;不然就锁全表;
本文标题:repeatable read下的 locking reads
本文链接:https://www.haomeiwen.com/subject/vxbluhtx.html
网友评论