看一些文章提到,mysql中INNODB引擎的表采用mvcc机制来解决幻读问题。但next key lock也是用于解决幻读,弄不清这两个到底区别在哪?
高洛峰2017-04-17 12:00:39
The ideal MVCC can solve phantom reading, but what innodb actually implements is not the ideal MVCC.
Innodb really relies on next key lock to solve phantom reads. Because innodb's write operation is actually an exclusive lock operation, the actual implementation of MVCC is used to solve the read concurrency problem.
I finally understood it after reading this link, so I attached it directly
http://blog.csdn.net/chen77716/article/details/6742128