Speeple News Search

Sign Up! | Tags | Domains | Statistics | Options | Advanced Search

InnoDB Transactional Characteristics

pythian.com » 2008 » July » 1st » InnoDB Transactional Characteristics

Tagged: mysql, innodb, innodb data file path, innodb file per table, innodb data home dir, innodb buffer pool size, mvcc, row level locking, innodb log file size, page level locking, innodb flush log at trx commit, table level locking

InnoDB is a storage engine that uses MVCC (described shortly) to provide ACID-compliant transactional data storage using row-level locking. MVCC stands for Multi-Version Concurrency Control. It is how InnoDB allows multiple transactions to look at a data set of one or more tables and have a consistent view of the data. MVCC keeps a virtual snapshot of the dataset for each transaction. An example Continue Reading »


Latest news from Pythian Group Blog:

  1. SQL Server: Understanding and Controlling Connection-Pooling Fragmentation
  2. DBD::mysql on OS X Quirks: Architectures, MySQL Binaries and the Filesystem
  3. MySQL Reference Manual Search
  4. AUSOUG Conference 2008 in Perth — Getting Ready
  5. SQL Server Virtualization, Part One: Introduction

Latest news from pythian.com:

  1. Log Buffer #117: a Carnival of the Vanities for DBAs
  2. Breaking News: How Fast Can Your Query be With Exadata?
  3. MySQL Replication Failures
  4. InnoDB logfiles
  5. Blank VIEW_DEFINITION?