The Concurrency control reference article from the English Wikipedia on 24-Apr-2004 (provided by Fixed Reference: snapshots of Wikipedia from wikipedia.org)

Concurrency control

In computer science -- more specifically, in the field of databases -- concurrency control is a method used to ensure that database transactions are executed in a safe manner (i.e., without data loss). Concurrency control is especially applicable to relational databases and database management systems, which must ensure that transactions are executed safely and that they follow the ACID rules. The DBMS must be able to ensure that only serializable, recoverable schedules are allowed, and that no actions of committed transactions are lost while undoing aborted transactions.

Table of contents

1 Transaction ACID Rules 2 Concurrency Control mechanism 3 See also

Transaction ACID Rules

• Atomicity - Either all or no operations are completed. (Undo)
• Consistency - All transactions must leave the database in consistent state.
• Isolation - Transactions cannot interfere with each other.
• Durability - Successful transactions must persist through crashes. (Redo)

Concurrency Control mechanism

The main categories of concurrency control mechanisms are:

• Pessimist - The concurrent executions of transactions are synchronized early in their execution life cycle.

• Optimistic - Delay the synchronization for transactions until their termination.

There are several methods for concurrency control, the majority of which uses Strict 2PL locking:

• Strict two-phase locking
• Non-strict two-phase locking
• Conservative two-phase locking
• Index locking
• Multiple granularity locking

Locks are bookkeeping objects associated with a database object.

There are also Non-lock concurrency control methods.

See also

• Concurrent programming
• Race condition
• Synchronization

This is the "Concurrency control" reference article from the English Wikipedia. All text is available under the terms of the GNU Free Documentation License. See also our Disclaimer.