InnoDBTransaction Model and Locking
SELECT ... FOR UPDATEand
SELECT ... LOCK IN SHARE MODE)
InnoDBRecord, Gap, and Next-Key Locks
InnoDBTable and Index Structures
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
MyISAM tables to
InnoDB, now that
is the default MySQL storage engine.
Anyone considering their application architecture or software
stack, to understand the design considerations, performance
characteristics, and scalability of
tables at a detailed level.
In this section, you will learn:
InnoDB implements transactions, and how
the inner workings of transactions compare compare with other
database systems you might be familiar with.
InnoDB implements row-level locking to
allow queries and DML statements to read and write the same
How multi-version concurrency control (MVCC) keeps transactions from viewing or modifying each others' data before the appropriate time.
The physical layout of
objects on disk, such as tables, indexes, tablespaces, undo
logs, and the redo log.