Timestamp-based concurrency control

Short description: Concurrency control algorithm

This article relies largely or entirely on a single source. Please help improve this article by introducing citations to additional sources.
Find sources: "Timestamp-based concurrency control" – news · newspapers · books · scholar · JSTOR (March 2026)

|

In computer science, a timestamp-based concurrency control algorithm is a optimistic concurrency control method. It is used in some databases to safely handle transactions using timestamps for synchronization instead of locks.[1]

## Contents

* 1 Operation
* 1.1 Assumptions
* 1.2 Generating a timestamp
* 1.3 Formal definition
* 1.4 Informal definition
* 2 Physically unrealizable
* 3 Recoverability
* 4 Implementation issues
* 4.1 Timestamp resolution
* 4.2 Timestamp locking
* 5 See also
* 6 References

## Operation

### Assumptions

* Every timestamp value is unique and accurately represents an instant in time.
* A higher-valued timestamp occurs later in time than a lower-valued timestamp.

### Generating a timestamp

A number of different approaches can generate timestamps

* Using the value of the system's clock at the start of a transaction as the timestamp.
* Using a thread-safe shared counter that is incremented at the start of a transaction as the timestamp.
* A combination of the above two methods.

### Formal definition

Each transaction (Ti) is an ordered list of actions (Aix). Before the transaction performs its first action (Ai1), it is marked with the current timestamp, or any other strictly totally ordered sequence: TS(Ti)=NOW(). Every transaction is also given an initially empty set of transactions upon which it depends, DEP(Ti)=[], and an initially empty set of old objects which it updated, OLD(Ti)=[].

Each object (Oj) in the database is given two timestamp fields which are not used other than for concurrency control:

* RT(Oj) is the timestamp of the last transaction that read the value of the object ( TS(Tr), where Tr is the last transaction that read the value of the object).
* WT(Oj) is the timestamp of the last transaction that updated the value of the object ( TS(Tw), where Tw is the last transaction that updated the value of the object).

For all Ti:

For each action Aix:

If Aix wishes to read the value of Oj:

If WT(Oj)>TS(Ti) then abort (a more recent thread has overwritten the value),
Otherwise update the set of dependencies DEP(Ti).add(WT(Oj)) and set RT(Oj)=max⁡(RT(Oj),TS(Ti));
If Aix wishes to update the value of Oj:

If RT(Oj)>TS(Ti) then abort (a more recent thread is already relying on the old value),
If WT(Oj)>TS(Ti) then skip (the Thomas Write Rule),
Otherwise store the previous values, OLD(Ti).add(Oj,WT(Oj)), set WT(Oj)=TS(Ti), and update the value of Oj.
While there is a transaction in DEP(Ti) that has not ended: wait
If there is a transaction in DEP(Ti) that aborted then abort
Otherwise: commit.

To abort:

For each (oldOj,oldWT(Oj)) in OLD(Ti)

If WT(Oj) equals TS(Ti) then restore Oj=oldOj and WT(Oj)=oldWT(Oj)

### Informal definition

Whenever a transaction initiated, it receives a timestamp. The transaction's timestamp indicates when the transaction was initiated. These timestamps ensure that transactions affect each object in the same sequence of their respective timestamps. Thus, given two operations that affect the same object from different transactions, the operation of the transaction with the earlier timestamp must execute before the operation of the transaction with the later timestamp. However, if the operation of the wrong transaction is actually presented first, then it is aborted and the transaction must be restarted.

Every object in the database has a read timestamp, which is updated whenever the object's data is read, and a write timestamp, which is updated whenever the object's data is changed.

If a transaction wants to read an object,

* but the transaction started before the object's write timestamp it means that something changed the object's data after the transaction started. In this case, the transaction is canceled and must be restarted.
* and the transaction started after the object's write timestamp, it means that it is safe to read the object. In this case, if the transaction's timestamp is after the object's read timestamp, the read timestamp is set to the transaction's timestamp.

If a transaction wants to write to an object,

* but the transaction started before the object's read timestamp it means that something has had a look at the object, and we assume it took a copy of the object's data. So we can't write to the object as that would make any copied data invalid, so the transaction is aborted and must be restarted.
* and the transaction started before the object's write timestamp it means that something has changed the object since we started our transaction. In this case we use the Thomas write rule and simply skip our write operation and continue as normal; the transaction does not have to be aborted or restarted
* otherwise, the transaction writes to the object, and the object's write timestamp is set to the transaction's timestamp.

## Physically unrealizable

The behavior is physically unrealizable if the results of transactions could not have occurred if transactions were instantaneous. The following are the only two situations that result in physically unrealizable behavior:

1. Transaction T tries to read X but TS(T) < WT(X). Reason: It means that X has been written to by another transaction after T began.
2. Transaction T tries to write X but TS(T) < RT(X). Reason: It means that a later transaction read X before it was written by T.

## Recoverability

For an explanation of the terms recoverable (RC), avoids cascading aborts (ACA) and strict (ST), see Database transaction schedule.

Note that timestamp ordering in its basic form does not produce recoverable histories. Consider for example the following history with transactions T1 and T2:

W1(x)R2(x)W2(y)C2R1(z)C1

This could be produced by a TO scheduler, but is not recoverable, as T2 commits even though having read from an uncommitted transaction. To make sure that it produces recoverable histories, a scheduler can keep a list of other transactions each transaction has read from, and not let a transaction commit before this list consisted of only committed transactions. To avoid cascading aborts, the scheduler could tag data written by uncommitted transactions as dirty, and never let a read operation commence on such a data item before it was untagged. To get a strict history, the scheduler should not allow any operations on dirty items.

## Implementation issues

### Timestamp resolution

This is the minimum time elapsed between two adjacent timestamps. If the resolution of the timestamp is too large (coarse), the possibility of two or more timestamps being equal is increased and thus enabling some transactions to commit out of correct order. For example, for a system that creates one hundred unique timestamps per second, two events that occur 2 milliseconds apart may be given the same timestamp even though they occurred at different times.

### Timestamp locking

Even though this technique is a non-locking one, in as much as the object is not locked from concurrent access for the duration of a transaction, the act of recording each timestamp against the Object requires an extremely short duration lock on the Object or its proxy.

## See also

* Multiversion concurrency control
* Timestamping (computing)

## References

1. ↑ Wolf, Stephan; Mühe, Henrik; Kemper, Alfons; Neumann, Thomas (2013). "An evaluation of strict timestamp ordering concurrency control for main-memory database systems". Springer Publishing. pp. 82–93. doi:10.1007/978-3-319-13960-9_7.

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Timestamp-based concurrency control. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Timestamp-based_concurrency_control&oldid=4296188"