×

On-the-fly, incremental, consistent reading of entire databases. (English) Zbl 0639.68112

We describe an algorithm to read entire databases with locking concurrency control allowing multiple readers or an exclusive writer. The algorithm runs concurrently with the normal transaction processing (on- the-fly), and locks the entities in the database one by one (incremental). We prove that the algorithm produces consistent pictures of the database. We also show that conflicts between the algorithm and some updates, although necessary, can be resolved.
Reading entire databases consistently, on-the-fly, incremental algorithms can avoid the database downtime trade-off between frequent checkpoints and crash recovery delay, thus improving system availability and reliability. Our algorithm reads the database once and writes only to sequential output, lowering its implementation and execution costs. A simple extension runs in parallel on several processors and produces consistent pictures of entire distributed databases.

MSC:

68P20 Information storage and retrieval of data
Full Text: DOI

References:

[1] Attar, R.; Bernstein, P. A.; Goodman, N., Site initialization, recovery, and back-up in a distributed database system, IEEE Trans. Software Engrg, 10, 645-650 (1984) · doi:10.1109/TSE.1984.5010293
[2] Bayer, R.; Heller, H.; Reiser, A., Parallelism and recovery in database systems, ACM Trans. Database Systems, 5, 139-156 (1980) · Zbl 0433.68072 · doi:10.1145/320141.320146
[3] Eswaran, K. P.; Gray, J. N.; Lorie, R. A.; Traiger, I. L., The notions of consistency and predicate locks in a database system, Comm. ACM, 19, 624-633 (1976) · Zbl 0341.68023 · doi:10.1145/360363.360369
[4] M. J. Fischer, N. D. Griffeth, and N. A. Lynch, Global states of a distributed system,Proceedings of a Symposium on Reliability in Distributed Software and Database Systems, 1981.
[5] Garcia-Molina, H.; Wiederhold, G., Read-only transactions in a distributed database, ACM Trans. Database Systems, 7, 209-234 (1982) · Zbl 0477.68103 · doi:10.1145/319702.319704
[6] Gray, J.; McJones, P.; Blasgen, M.; Lindsay, B.; Lorie, R.; Price, T.; Putzolu, F.; Traiger, I., The recovery manager of the System R database manager, ACM Comput. Surveys, 13, 223-242 (1981) · doi:10.1145/356842.356847
[7] Gray, J. N., Notes on data base operating systems, Operating Systems—An Advanced Course (1978), New York: Springer-Verlag, New York
[8] Kim, Won, Highly available systems for database applications, ACM Comput. Surveys, 16, 71-98 (1984) · doi:10.1145/861.866
[9] Krishna, C. M.; Shin, K. G.; Lee, Y. H., Optimization criteria for checkpoint placement, Comm. ACM, 27, 1008-1012 (1984) · doi:10.1145/358274.358282
[10] Lohman, G. M.; Muckstadt, J. A., Optimal policy for batch operations: backup, checkpointing, reorganization and updating, ACM Trans. Database Systems, 2, 209-222 (1977) · doi:10.1145/320557.320558
[11] Lorie, R. A., Physical integrity in a large segmented database, ACM Trans. Database Systems, 2, 91-104 (1977) · doi:10.1145/320521.320540
[12] D. J. Rosenkrantz, Dynamic database dumping,Proceedings of the ACMSIGMOD Conference on Management of Data, 1978, pp. 3-8.
[13] Tantawi, A. N.; Ruschitzka, M., Performance analysis of checkpointing strategies, ACM Trans. Comput. Systems, 2, 123-144 (1984) · doi:10.1145/190.357398
This reference list is based on information provided by the publisher or from digital mathematics libraries. Its items are heuristically matched to zbMATH identifiers and may contain data conversion errors. In some cases that data have been complemented/enhanced by data from zbMATH Open. This attempts to reflect the references listed in the original paper as accurately as possible without claiming completeness or a perfect matching.