This Article 
 Bibliographic References 
 Add to: 
Modular Synchronization in Distributed, Multiversion Databases: Version Control and Concurrency Control
February 1993 (vol. 5 no. 1)
pp. 126-137

A version control mechanism is proposed that enhances the modularity and extensibility of multiversion concurrency control algorithms. The multiversion algorithms are decoupled into two components: version control and concurrency control. This permits modular development of multiversion protocols and simplifies the task of proving the correctness of these protocols. A set of procedures for version control is described that defines the interface with the version control component. It is shown that the same interface can be used by the database actions of both two-phase locking and time-stamp concurrency control protocols to access multiversion data. An interesting feature of the framework is that the execution of read-only transactions becomes completely independent of the underlying concurrency control implementation. Unlike other multiversion algorithms, read-only transactions in this scheme do not modify any version-related information, and therefore do not interfere with the execution of read-write transactions. The extension of the multiversion algorithms to a distributed environment becomes very simple.

[1] D. Agrawal, A. J. Bernstein, P. Gupta, and S. Sengupta, "Distributed multiversion optimistic concurrency control for relational databases," inProc. 31st IEEE Computer Society International Conf., COMPCON, Mar. 1986, pp. 416-421.
[2] D. Agrawal, "Distributed optimistic concurrency control with reduced rollback,"Distributed Comput., vol. 2, no. 1, pp. 45-59, Jan. 1987.
[3] P. Bernstein and N. Goodman, "Concurrency Control in Distributed Database Systems,"ACM Computing Surveys, Vol. 13, No. 2, June 1981, pp. 185-221.
[4] P. A. Bernstein and N. Goodman, "Multiversion concurrency control,"ACM Trans. Database Syst., vol. 8, no. 4, pp. 465-483, Dec. 1983.
[5] P. A. Bernstein and N. Goodman, "The failure and recovery problem for replicated databases," inProc. 2nd Ann. Symp. Principles of Distributed Computing, 1983, pp. 114-122.
[6] P.A. Bernstein, V. Hadzilacos, and N. Goodman,Concurrency Control and Recovery in Database Systems, Addison-Wesley, Reading, Mass., 1987.
[7] A. Chanet al., "The implementation of an integrated concurrency control and recovery scheme," inProc. SIGMOD Conf. Management Data, June 1982, pp. 184-191.
[8] A. Chan and R. Gray, "Implementing distributed read-only transactions,"IEEE Trans. Software Eng., vol. 11, pp. 205-212, Feb. 1985.
[9] K. P. Eswaran, J. N. Gray, R. A. Lorie, and I. L. Traiger, "The notions of consistency and predicate locks in a database system,"Commun. ACM, vol. 19, no. 11, pp. 624-633, Nov. 1976.
[10] H. Garcia-Molina and G. Weiderhold, "Read-only transactions in a distributed database,"ACM Trans. Database Syst., vol. 7, no. 2, pp. 209-234, June 1982.
[11] D. Gifford, "Weighted voting for replicated data," inProc. 7th ACM Symp. Oper. Syst. Principles, Dec. 1979, pp. 150-162.
[12] J. Gray, "Notes on database operation systems," inOperating Systems: An Advanced Course(Lecture Notes in Computer Science, vol. 60) Berlin: Springer-Verlag, 1978.
[13] A. Heddaya, M. Hsu, and W. Weihl, "Two phase gossip: Managing distributed event histories," Tech. Rep. TR-04-87, Aiken Computation Lab., Harvard Univ., 1987.Information Sciences: An International Journal, to be published.
[14] M. P. Herlihy, "A quorum-consensus replication method for abstract data types,"ACM Trans. Comput. Syst., vol. 4, no. 1, Feb. 1986.
[15] H. T. Kung and J. T. Robinson, "On optimistic methods for concurrency control,"ACM Trans. Database Syst., vol. 6, pp. 213-226, June 1981.
[16] C.H. Papadimitriou, "The serializability of concurrent database updates,"J. ACM, vol. 26, pp. 631-653, Oct. 1979.
[17] D. P. Reed, "Naming and synchronization in a decentralized computer system," Ph.D. dissertation, Massachusetts Instit. Technol., 1978. Available as Tech. Rep. MIT/LCS/TR-205.
[18] O. T. Satyanarayanan and D. Agrawal, "Increasing availability and efficiency of read-only transactions," Tech. Rep. TRCS 89-28, Dep. of Comput. Sci., Univ. of California at Santa Barbara, Oct. 1989.
[19] R. E. Stearns and D. J. Rosenkrantz, "Distributed database concurrency control using before-values," inProc. ACM SIGMOD Conf. on Management of Data, June 1981, pp. 74-83.
[20] R. Thomas, "A majority consensus approach to concurrency control,"ACM Trans. Database Syst., vol. 4, pp. 180-209, June 1979.
[21] W.E. Weihl, "Distributed version management for read-only actions,"IEEE Trans. Software Eng., vol. SE-13, pp. 55-64, Jan. 1987.
[22] G. T. Wuu and A. J. Bernstein, "Efficient solutions to the replicated log and dictionary problems," inProc. Third ACM Symp. Priniciples Distributed Comput., Aug. 1984, pp. 233-242.

Index Terms:
distributed databases; modular synchronisation; multiversion databases; version control; concurrency control; modularity; extensibility; multiversion protocols; proving the correctness; two-phase locking; time-stamp; read-only transactions; concurrency control; configuration management; distributed databases; protocols; synchronisation
D. Agrawal, S. Sengupta, "Modular Synchronization in Distributed, Multiversion Databases: Version Control and Concurrency Control," IEEE Transactions on Knowledge and Data Engineering, vol. 5, no. 1, pp. 126-137, Feb. 1993, doi:10.1109/69.204097
Usage of this product signifies your acceptance of the Terms of Use.