Fifth International Conference on Very Large Data Bases, 1979.
DOI: 10.1109/vldb.1979.718150
|View full text |Cite
|
Sign up to set email alerts
|

On Optimistic Methods For Concurrency Control

Abstract: Most current approaches to concurrency control in database systems rely on locking of data objects as a control mechanism. In this paper, two families of nonlocking concurrency controls are presented. The methods used are "optimistic" in the sense that they rely mainly on transaction backup as a control mechanism, "hoping" that conflicts between transactions will not occur. Applications for which these methods should be more efficient than locking are discussed.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
142
0
1

Publication Types

Select...
6
4

Relationship

0
10

Authors

Journals

citations
Cited by 121 publications
(143 citation statements)
references
References 12 publications
0
142
0
1
Order By: Relevance
“…The ability to revert to a prior point within a concurrent execution is essential to transaction systems (Kung & Robinson 1981;Gray & Reuter 1993;Adya et al 1995); outside their role for database concurrency control, such approaches can improve parallel program performance by profitably exploiting speculative execution (Rinard 1999;Welc et al 2005). Harris et al (2005) proposes a transactional memory system for Haskell that introduces a retry primitive to allow a transactional execution to safely abort and be reexecuted, if desired resources are unavailable.…”
Section: Related Workmentioning
confidence: 99%
“…The ability to revert to a prior point within a concurrent execution is essential to transaction systems (Kung & Robinson 1981;Gray & Reuter 1993;Adya et al 1995); outside their role for database concurrency control, such approaches can improve parallel program performance by profitably exploiting speculative execution (Rinard 1999;Welc et al 2005). Harris et al (2005) proposes a transactional memory system for Haskell that introduces a retry primitive to allow a transactional execution to safely abort and be reexecuted, if desired resources are unavailable.…”
Section: Related Workmentioning
confidence: 99%
“…Optimistic write: Our transactional memory writes optimistically [23]. The transaction boundaries are controlled by working on copies of the objects.…”
Section: Transactions At Runtimementioning
confidence: 99%
“…In fact, we only hope that failures will rarely occur, whereas purely backup methods, making no use of locks, work hoping that conflicting accesses will rarely occur, and this is a more improbable condition. Kung and Robinson (1981), for example, suggest applying their approach to "query-dominant systems and very large tree-structured indexes" Among the locking methods, an approach towards efficiency improvement which we have already mentioned in the introduction is the semantic approach, such as, for example, that of Schwarz and Spector (1982). Locking is performed by making use of type-specific semantic knowledge about shared abstract types and operations in order to allow higher concurrency.…”
Section: Related Workmentioning
confidence: 99%