- 14.2 The InnoDB Storage Engine
- 14.2.1 Getting Started with InnoDB Tables
- 14.2.2 Administering InnoDB
- 14.2.3 InnoDB Concepts and Architecture
- 14.2.3.1 The InnoDB Transaction Model and Locking
- 14.2.3.2 InnoDB Lock Modes
- 14.2.3.3 Consistent Nonlocking Reads
- 14.2.3.4 Locking Reads (SELECT ... FOR UPDATE and SELECT ... LOCK IN SHARE MODE)
- 14.2.3.5 InnoDB Record, Gap, and Next-Key Locks
- 14.2.3.6 Avoiding the Phantom Problem Using Next-Key Locking
- 14.2.3.7 Locks Set by Different SQL Statements in InnoDB
- 14.2.3.8 Implicit Transaction Commit and Rollback
- 14.2.3.9 Deadlock Detection and Rollback
- 14.2.3.10 How to Cope with Deadlocks
- 14.2.3.11 InnoDB Multi-Versioning
- 14.2.3.12 InnoDB Table and Index Structures
- 14.2.3.13 The InnoDB Recovery Process
- 14.2.3.14 InnoDB Error Handling
- 14.2.4 InnoDB Performance Tuning and Troubleshooting
- 14.2.5 InnoDB Features for Flexibility, Ease of Use and Reliability
- 14.2.6 InnoDB Startup Options and System Variables
- 14.2.7 Limits on InnoDB Tables
- 14.2.8 MySQL and the ACID Model
- 14.2.9 InnoDB Integration with memcached
[+/-]
- 14.2.3.1. The
InnoDBTransaction Model and Locking - 14.2.3.2.
InnoDBLock Modes - 14.2.3.3. Consistent Nonlocking Reads
- 14.2.3.4. Locking Reads (
SELECT ... FOR UPDATEandSELECT ... LOCK IN SHARE MODE) - 14.2.3.5.
InnoDBRecord, Gap, and Next-Key Locks - 14.2.3.6. Avoiding the Phantom Problem Using Next-Key Locking
- 14.2.3.7. Locks Set by Different SQL Statements in
InnoDB - 14.2.3.8. Implicit Transaction Commit and Rollback
- 14.2.3.9. Deadlock Detection and Rollback
- 14.2.3.10. How to Cope with Deadlocks
- 14.2.3.11.
InnoDBMulti-Versioning - 14.2.3.12.
InnoDBTable and Index Structures - 14.2.3.13. The
InnoDBRecovery Process - 14.2.3.14.
InnoDBError Handling
The information in this section provides background to help you
get the most performance and functionality from using
InnoDB tables. It is intended for:
Anyone switching to MySQL from another database system, to explain what things might seem familiar and which might be all-new.
Anyone moving from
MyISAMtables toInnoDB, now thatInnoDBis the default MySQL storage engine.Anyone considering their application architecture or software stack, to understand the design considerations, performance characteristics, and scalability of
InnoDBtables at a detailed level.
In this section, you will learn:
How
InnoDBimplements transactions, and how the inner workings of transactions compare compare with other database systems you might be familiar with.How
InnoDBimplements row-level locking to allow queries and DML statements to read and write the same table simultaneously.How multi-version concurrency control (MVCC) keeps transactions from viewing or modifying each others' data before the appropriate time.
The physical layout of
InnoDB-related objects on disk, such as tables, indexes, tablespaces, undo logs, and the redo log.
User Comments
Add your own comment.