Re: How does Innodb cleverly avoid read-write conflicts when implementing mvcc?

[Y M]

I think I can add a more detailed point: the current transaction level is read committed, but transaction 1 reads the data of transaction 2 before transaction 2 is committed (because I did not have a read-write lock to protect this shared area in the steps above. , I want to know whether InnoDB uses read-write locks to handle it in this scenario. As far as I know, mvcc will not lock before the serializable level)