Multi-Version Concurrency Control

Multi-Version Concurrency Control

(database)
(MVCC) An advanced technique for improving multi-user database performance.

The main difference between multiversion and lock models is that in MVCC locks acquired for querying (reading) data don't conflict with locks acquired for writing data and so reading never blocks writing and writing never blocks reading.

This technique is used in the free software database PostgreSQL.
Mentioned in ?
References in periodicals archive ?
5 now supports multi-version concurrency control, non-stop upgrades for replicated environments and a pre-built replication framework to simplify development of highly available applications.
Some of the topics covered are: Cache Friendly Web, The Apache Toolbox, MySQL Best Practices, Internationalization and Localization with PHP, Choosing a Templating System, PostgreSQL's Multi-Version Concurrency Control, Embedded and Linux.
solidDB for MySQL is designed for transactional applications and supports full ACID compliance with configurable transaction isolation levels, both optimistic and pessimistic concurrency control, Multi-Version Concurrency Control (MVCC) with non-blocking reads and writes, row-level locking, and support for foreign keys and referential integrity.
Key features of the solidDB Storage Engine include multi-version concurrency control, full transactional integrity with robust ACID support, online backup capabilities, fast performance for mixed workloads and robust security with database roles.
Key features of solidDB Storage Engine include multi-version concurrency control, full transactional integrity with robust ACID support, online backup capabilities, fast performance for mixed workloads and robust security with database roles.

Full browser ?