[go: nahoru, domu]

Jump to content

Non-lock concurrency control: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
rv inline talk
MVCC is optimistic
 
(12 intermediate revisions by 11 users not shown)
Line 1: Line 1:
{{Unreferenced|date=December 2009}}
In [[Computer Science]], in the field of [[database]]s, '''non-lock concurrency control''' is [[concurrency control]] method used in [[relational database]]s without using [[lock (computer science)|locking]].
In [[Computer Science]], in the field of [[database]]s, '''non-lock concurrency control''' is a [[concurrency control]] method used in [[relational database]]s without using [[lock (computer science)|locking]].


There are several non-lock concurrency control methods:
There are several non-lock concurrency control methods, which involve the use of timestamps on transaction to determine transaction priority:


* [[Optimistic concurrency control]]
* [[Optimistic concurrency control]]
* [[Timestamp-based concurrency control]]
** [[Timestamp-based concurrency control]]
* [[Multiversion concurrency control]]
** Validation-based concurrency control
** [[Multiversion concurrency control]]
*** [[Snapshot isolation]]


==See also==
They involve the use of timestamps on transaction to determine transaction priority.

See also
* [[Concurrency pattern]]
* [[Concurrency pattern]]
* [[Optimistic concurrency control]]
* [[InterBase]]
* [[InterBase]]
* [[Lock-free and wait-free algorithms]]
* [[Lock-free and wait-free algorithms]]


{{DEFAULTSORT:Non-Lock Concurrency Control}}
[[Category:concurrency control]]
[[Category:Concurrency control]]
[[Category:Transaction processing]]
[[Category:Transaction processing]]



{{database-stub}}
{{Database-stub}}

Latest revision as of 21:27, 27 December 2023

In Computer Science, in the field of databases, non-lock concurrency control is a concurrency control method used in relational databases without using locking.

There are several non-lock concurrency control methods, which involve the use of timestamps on transaction to determine transaction priority:

See also[edit]