DMCA
ARIES/IM: An Efficient and High Concurrency Index Management Method Using Write-ahead Logging (1992)
| Venue: | PROCEEDINGS OF THE 1992 ACM SIGMOD INTERNATIONAL CONFERENCE ON MANAGEMENT OF DATA |
| Citations: | 97 - 6 self |
BibTeX
@MISC{Mohan92aries/im:an,
author = {C. Mohan and Frank Levine},
title = {ARIES/IM: An Efficient and High Concurrency Index Management Method Using Write-ahead Logging},
year = {1992}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
This paper provides a comprehensive treatment of index management in transaction systems. We present a method, called ARIES/IM (Algorithm for Recovery and Isolation Exploiting Semantics for Index Management), for concurrency control and recovery of B+-trees. ARIES/IM guarantees serializability and uses write-ahead logging for recovery. It supports very high concurrency and good performance by (1) treating as the lock of a key the same lock as the one on the corresponding record data in a data page (e.g., at the record level), (2) not acquiring, in the interest of permitting very high concurrency, commit duration locks on index pages even during index structure modification operations (SMOs) like page splits and page deletions, and (3) allowing retrievals, inserts, and deletes to go on concurrently with SMOs. During restart recovery, any necessary redos of index changes are always performed in a page-oriented fashion (i.e., without traversing the index tree) and, during normal processing and restart recovery, whenever possible undos are performed in a page-oriented fashion. ARIES/IM permits different granularities of locking to be supported in a flexible manner. A subset of ARIES/IM has been implemented in the OS/2 Extended Edition Database Manager. Since the locking ideas of ARIES/IM have general applicability, some of them have also been implemented in SQL/DS and the VM Shared File System, even though those systems use the shadow-page technique for recovery.
Keyphrases
aries lm high concurrency restart recovery index change page-oriented fashion data page vm shared file system transaction system general applicability comprehensive treatment good performance extended edition database manager permit different granularity page deletion ation exploiting semantics forlndex management pageoriented fashion index tree page split corresponding record data shadow-page technique record level possible undos flexible manner index structure modification operation necessary redos commit duration lock ari e lm guarantee serializability normal processing index management concurrency control write-ahead logging index page
