(mysql.info) innodb-transaction-model

 
 14.2.10 `InnoDB' Transaction Model and Locking
 ----------------------------------------------

 
* innodb-lock-modes            `InnoDB' Lock Modes
* innodb-and-autocommit        `InnoDB' and `AUTOCOMMIT'
* innodb-transaction-isolation  `InnoDB' and `TRANSACTION ISOLATION LEVEL'
* innodb-consistent-read       Consistent Non-Locking Read
* innodb-locking-reads         `SELECT ... FOR UPDATE' and `SELECT ... LOCK IN SHARE MODE' Locking Reads
* innodb-next-key-locking      Next-Key Locking: Avoiding the Phantom Problem
* innodb-consistent-read-example  An Example of Consistent Read in `InnoDB'
* innodb-locks-set             Locks Set by Different SQL Statements in `InnoDB'
* innodb-implicit-command-or-rollback  Implicit Transaction Commit and Rollback
* innodb-deadlock-detection    Deadlock Detection and Rollback
* innodb-deadlocks             How to Cope with Deadlocks
 
 In the `InnoDB' transaction model, the goal is to combine the best
 properties of a multi-versioning database with traditional two-phase
 locking. `InnoDB' does locking on the row level and runs queries as
 non-locking consistent reads by default, in the style of Oracle. The
 lock table in `InnoDB' is stored so space-efficiently that lock
 escalation is not needed: Typically several users are allowed to lock
 every row in the database, or any random subset of the rows, without
 `InnoDB' running out of memory.

Info Catalog

(mysql.info) moving

(mysql.info) innodb

(mysql.info) innodb-tuning

automatically generated byinfo2html

(mysql.info) innodb-transaction-model

Menu