The Delay/Re-Read Protocol for concurrency control in databases

M. Dennis Mickunas, Pankaj Jalote, Roy H. Campbell

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

We present a new protocol, called the Delay/Re-Read Protocol, for controlling concurrent access to a database. The protocol uses a combination of preventive and corrective measures for maintaining consistency. On recognizing that a transaction has read inconsistent data, the Protocol applies a corrective measure which requires the transaction to re-read some data. Alternatively, on recognizing that a transaction is about to write data which will result in inconsistency, the Protocol applies a preventive measure which delays the Write. A Read request is always granted without delay. The Protocol is deadlock-free, requires no backup data, and supports a greater degree of concurrency than Two Phase Locking. A transaction is never aborted or delayed indefinitely by the Protocol.

Original languageEnglish (US)
Title of host publicationIEEE International Conference on Data Engineering, COMPDEC 1986
PublisherIEEE Computer Society
Pages307-314
Number of pages8
ISBN (Electronic)0818605332, 081860655X, 9780818605338, 9780818606557
DOIs
StatePublished - Sep 14 2015
Event1st IEEE International Conference on Data Engineering, COMPDEC 1984 - Los Angeles, United States
Duration: Apr 24 1984Apr 27 1984

Publication series

NameProceedings - International Conference on Data Engineering
Volume2015-September
ISSN (Print)1084-4627

Other

Other1st IEEE International Conference on Data Engineering, COMPDEC 1984
CountryUnited States
CityLos Angeles
Period4/24/844/27/84

Fingerprint

Concurrency control
Network protocols

Keywords

  • Concurrency control
  • Databases
  • Delays
  • History
  • Protocols
  • Schedules
  • System recovery

ASJC Scopus subject areas

  • Software
  • Signal Processing
  • Information Systems

Cite this

Dennis Mickunas, M., Jalote, P., & Campbell, R. H. (2015). The Delay/Re-Read Protocol for concurrency control in databases. In IEEE International Conference on Data Engineering, COMPDEC 1986 (pp. 307-314). [7271287] (Proceedings - International Conference on Data Engineering; Vol. 2015-September). IEEE Computer Society. https://doi.org/10.1109/ICDE.1984.7271287

The Delay/Re-Read Protocol for concurrency control in databases. / Dennis Mickunas, M.; Jalote, Pankaj; Campbell, Roy H.

IEEE International Conference on Data Engineering, COMPDEC 1986. IEEE Computer Society, 2015. p. 307-314 7271287 (Proceedings - International Conference on Data Engineering; Vol. 2015-September).

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Dennis Mickunas, M, Jalote, P & Campbell, RH 2015, The Delay/Re-Read Protocol for concurrency control in databases. in IEEE International Conference on Data Engineering, COMPDEC 1986., 7271287, Proceedings - International Conference on Data Engineering, vol. 2015-September, IEEE Computer Society, pp. 307-314, 1st IEEE International Conference on Data Engineering, COMPDEC 1984, Los Angeles, United States, 4/24/84. https://doi.org/10.1109/ICDE.1984.7271287
Dennis Mickunas M, Jalote P, Campbell RH. The Delay/Re-Read Protocol for concurrency control in databases. In IEEE International Conference on Data Engineering, COMPDEC 1986. IEEE Computer Society. 2015. p. 307-314. 7271287. (Proceedings - International Conference on Data Engineering). https://doi.org/10.1109/ICDE.1984.7271287
Dennis Mickunas, M. ; Jalote, Pankaj ; Campbell, Roy H. / The Delay/Re-Read Protocol for concurrency control in databases. IEEE International Conference on Data Engineering, COMPDEC 1986. IEEE Computer Society, 2015. pp. 307-314 (Proceedings - International Conference on Data Engineering).
@inproceedings{79e1ea8c7d3a44eab652dc0bb53b7ec0,
title = "The Delay/Re-Read Protocol for concurrency control in databases",
abstract = "We present a new protocol, called the Delay/Re-Read Protocol, for controlling concurrent access to a database. The protocol uses a combination of preventive and corrective measures for maintaining consistency. On recognizing that a transaction has read inconsistent data, the Protocol applies a corrective measure which requires the transaction to re-read some data. Alternatively, on recognizing that a transaction is about to write data which will result in inconsistency, the Protocol applies a preventive measure which delays the Write. A Read request is always granted without delay. The Protocol is deadlock-free, requires no backup data, and supports a greater degree of concurrency than Two Phase Locking. A transaction is never aborted or delayed indefinitely by the Protocol.",
keywords = "Concurrency control, Databases, Delays, History, Protocols, Schedules, System recovery",
author = "{Dennis Mickunas}, M. and Pankaj Jalote and Campbell, {Roy H.}",
year = "2015",
month = "9",
day = "14",
doi = "10.1109/ICDE.1984.7271287",
language = "English (US)",
series = "Proceedings - International Conference on Data Engineering",
publisher = "IEEE Computer Society",
pages = "307--314",
booktitle = "IEEE International Conference on Data Engineering, COMPDEC 1986",

}

TY - GEN

T1 - The Delay/Re-Read Protocol for concurrency control in databases

AU - Dennis Mickunas, M.

AU - Jalote, Pankaj

AU - Campbell, Roy H.

PY - 2015/9/14

Y1 - 2015/9/14

N2 - We present a new protocol, called the Delay/Re-Read Protocol, for controlling concurrent access to a database. The protocol uses a combination of preventive and corrective measures for maintaining consistency. On recognizing that a transaction has read inconsistent data, the Protocol applies a corrective measure which requires the transaction to re-read some data. Alternatively, on recognizing that a transaction is about to write data which will result in inconsistency, the Protocol applies a preventive measure which delays the Write. A Read request is always granted without delay. The Protocol is deadlock-free, requires no backup data, and supports a greater degree of concurrency than Two Phase Locking. A transaction is never aborted or delayed indefinitely by the Protocol.

AB - We present a new protocol, called the Delay/Re-Read Protocol, for controlling concurrent access to a database. The protocol uses a combination of preventive and corrective measures for maintaining consistency. On recognizing that a transaction has read inconsistent data, the Protocol applies a corrective measure which requires the transaction to re-read some data. Alternatively, on recognizing that a transaction is about to write data which will result in inconsistency, the Protocol applies a preventive measure which delays the Write. A Read request is always granted without delay. The Protocol is deadlock-free, requires no backup data, and supports a greater degree of concurrency than Two Phase Locking. A transaction is never aborted or delayed indefinitely by the Protocol.

KW - Concurrency control

KW - Databases

KW - Delays

KW - History

KW - Protocols

KW - Schedules

KW - System recovery

UR - http://www.scopus.com/inward/record.url?scp=84958695700&partnerID=8YFLogxK

UR - http://www.scopus.com/inward/citedby.url?scp=84958695700&partnerID=8YFLogxK

U2 - 10.1109/ICDE.1984.7271287

DO - 10.1109/ICDE.1984.7271287

M3 - Conference contribution

AN - SCOPUS:84958695700

T3 - Proceedings - International Conference on Data Engineering

SP - 307

EP - 314

BT - IEEE International Conference on Data Engineering, COMPDEC 1986

PB - IEEE Computer Society

ER -