B-trees have been ubiquitous in database management systems for several decades, and they serve in many other storage systems as well. Their basic structure and their basic operations are well understood including search, insertion, and deletion. However, implementation of transactional guarantees such as all-or-nothing failure atomicity and durability in spite of media and system failures seems to be difficult. High-performance techniques such as pseudo-deleted records, allocation-only logging, and transaction processing during crash recovery are widely used in commercial B-tree implementations but not widely understood. This survey collects many of these techniques as a reference for students, researchers, system architects, and software developers. Central in this discussion are physical data independence, separation of logical database contents and physical representation, and the concepts of user transactions and system transactions. Many of the techniques discussed are applicable beyond B-trees.
Beschreibung
A survey of B-tree logging and recovery techniques
%0 Journal Article
%1 Graefe:2012:SBL:2109196.2109197
%A Graefe, Goetz
%C New York, NY, USA
%D 2012
%I ACM
%J ACM Trans. Database Syst.
%K btree data_structures logging paper survey transaction
%N 1
%P 1:1--1:35
%R 10.1145/2109196.2109197
%T A survey of B-tree logging and recovery techniques
%U http://doi.acm.org/10.1145/2109196.2109197
%V 37
%X B-trees have been ubiquitous in database management systems for several decades, and they serve in many other storage systems as well. Their basic structure and their basic operations are well understood including search, insertion, and deletion. However, implementation of transactional guarantees such as all-or-nothing failure atomicity and durability in spite of media and system failures seems to be difficult. High-performance techniques such as pseudo-deleted records, allocation-only logging, and transaction processing during crash recovery are widely used in commercial B-tree implementations but not widely understood. This survey collects many of these techniques as a reference for students, researchers, system architects, and software developers. Central in this discussion are physical data independence, separation of logical database contents and physical representation, and the concepts of user transactions and system transactions. Many of the techniques discussed are applicable beyond B-trees.
@article{Graefe:2012:SBL:2109196.2109197,
abstract = {B-trees have been ubiquitous in database management systems for several decades, and they serve in many other storage systems as well. Their basic structure and their basic operations are well understood including search, insertion, and deletion. However, implementation of transactional guarantees such as all-or-nothing failure atomicity and durability in spite of media and system failures seems to be difficult. High-performance techniques such as pseudo-deleted records, allocation-only logging, and transaction processing during crash recovery are widely used in commercial B-tree implementations but not widely understood. This survey collects many of these techniques as a reference for students, researchers, system architects, and software developers. Central in this discussion are physical data independence, separation of logical database contents and physical representation, and the concepts of user transactions and system transactions. Many of the techniques discussed are applicable beyond B-trees.},
acmid = {2109197},
added-at = {2012-04-11T16:26:35.000+0200},
address = {New York, NY, USA},
articleno = {1},
author = {Graefe, Goetz},
biburl = {https://www.bibsonomy.org/bibtex/28f78b7114fd99deabebb257793c7fa38/sac},
description = {A survey of B-tree logging and recovery techniques},
doi = {10.1145/2109196.2109197},
interhash = {bb1a2c75876b953cc038adc53fccc575},
intrahash = {8f78b7114fd99deabebb257793c7fa38},
issn = {0362-5915},
issue_date = {February 2012},
journal = {ACM Trans. Database Syst.},
keywords = {btree data_structures logging paper survey transaction},
month = mar,
number = 1,
numpages = {35},
pages = {1:1--1:35},
publisher = {ACM},
timestamp = {2012-04-11T16:26:35.000+0200},
title = {A survey of B-tree logging and recovery techniques},
url = {http://doi.acm.org/10.1145/2109196.2109197},
volume = 37,
year = 2012
}