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 non-locking 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 where these methods should be more efficient than locking are discussed.
No takes yet. Share an insight, caveat, or question.
King et al. (1979) studied this question.
Synapse has enriched 3 closely related papers on similar clinical questions. Consider them for comparative context: