Skip to content

Update MySQL_InnoDB_engine.md #72

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/studynotes/database/MySQL/MySQL_InnoDB_engine.md
Original file line number Diff line number Diff line change
Expand Up @@ -285,7 +285,7 @@ show engine innodb status;

![image](https://cdn.jsdelivr.net/gh/xustudyxu/image-hosting1@master/20221002/image.sgj8ivm9ilc.webp)

而对于这四大特性,实际上分为两个部分。 其中的原子性、一致性、持久化,实际上是由InnoDB中的两份日志来保证的,一份是redo log日志,一份是undo log日志。 而持久性是通过数据库的锁,加上MVCC来保证的。
而对于这四大特性,实际上分为两个部分。 其中的原子性、一致性、持久化,实际上是由InnoDB中的两份日志来保证的,一份是redo log日志,一份是undo log日志。 而隔离性是通过数据库的锁,加上MVCC来保证的。

![image](https://cdn.jsdelivr.net/gh/xustudyxu/image-hosting1@master/20221002/image.1oe3nog6lskg.webp)

Expand Down Expand Up @@ -743,4 +743,4 @@ RR隔离级别下,仅在事务中第一次执行快照读时生成ReadView,

所以呢,MVCC的实现原理就是通过 InnoDB表的隐藏字段、UndoLog 版本链、ReadView来实现的。而MVCC + 锁,则实现了事务的隔离性。 而一致性则是由redolog 与 undolog保证。

![image](https://cdn.jsdelivr.net/gh/xustudyxu/image-hosting1@master/20221003/image.28l27i8tw340.webp)
![image](https://cdn.jsdelivr.net/gh/xustudyxu/image-hosting1@master/20221003/image.28l27i8tw340.webp)