14.5.1 InnoDB Locking
14.5.2 InnoDB Transaction Model
14.5.3 Locks Set by Different SQL Statements in InnoDB
14.5.4 Phantom Rows
14.5.5 Deadlocks in InnoDB
To implement a large-scale, busy, or highly reliable database application, to port substantial code from a different database system, or to tune MySQL performance, it is important to understand InnoDB locking and the InnoDB transaction model.
要实现大规模、繁忙或高度可靠的数据库应用程序, 要从不同的数据库系统中移植大量代码, 或者要优化 MySQL 性能, 了解 InnoDB 锁和 InnoDB 事务模型很重要。
This section discusses several topics related to InnoDB locking and the InnoDB transaction model with which you should be familiar.
本节讨论的几个关于InnoDB锁定和InnoDB事务模型的话题，你应该有所了解。
- Section 14.5.1, “InnoDB Locking” describes lock types used by InnoDB.
- Section 14.5.1, “InnoDB Locking” 描述了innob的锁类型
- Section 14.5.2, “InnoDB Transaction Model” describes transaction isolation levels and the locking strategies used by each. It also discusses the use of autocommit, consistent non-locking reads, and locking reads.
- Section 14.5.2, “InnoDB Transaction Model” 描述了事务的隔离级别使用对应的的锁定策略，它还讨论了autocommit，一致的非锁定读和锁定读的使用。
- Section 14.5.3, “Locks Set by Different SQL Statements in InnoDB” discusses specific types of locks set in InnoDB for various statements.
- Section 14.5.3, “Locks Set by Different SQL Statements in InnoDB”描述了innodb在各种语句会使用什么类型的锁
- Section 14.5.4, “Phantom Rows” describes how InnoDB uses next-key locking to avoid phantom rows
- .Section 14.5.4, “Phantom Rows” 描述了innodb如何使用next-key locking来避免幻读行
- Section 14.5.5, “Deadlocks in InnoDB” provides a deadlock example, discusses deadlock detection and rollback, and provides tips for minimizing and handling deadlocks in InnoDB.
- Section 14.5.5, “Deadlocks in InnoDB” 提供了一个死锁案例，讨论了死锁的检测和回滚，并提供了在InnoDB中最小化和处理死锁的技巧。