• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • DMCA
  • Donate

CiteSeerX logo

Advanced Search Include Citations
Advanced Search Include Citations

DMCA

Aries: A transaction recovery method supporting fine-granularity locking and partial rollbacks using write-ahead logging (1992)

Cached

  • Download as a PDF

Download Links

  • [www.sai.msu.su]
  • [www.bme.ogi.edu]
  • [pages.cs.wisc.edu]
  • [www.cs.ubc.ca]
  • [cs.ubc.ca]
  • [www.cs.wisc.edu]
  • [www.cs.columbia.edu]
  • [www.cs.wisc.edu]
  • [www.cs.wisc.edu]
  • [www.cs.brown.edu]
  • [pages.cs.wisc.edu]
  • [pages.cs.wisc.edu]
  • [db.lcs.mit.edu]
  • [people.csail.mit.edu]
  • [www.cs.duke.edu]
  • [pages.cs.wisc.edu]
  • [www.cs.ubc.ca]
  • [users.csc.calpoly.edu]
  • [pages.cs.wisc.edu]
  • [web.eecs.umich.edu]
  • [db.cs.berkeley.edu]
  • [www.cs.berkeley.edu]
  • [www.eecs.berkeley.edu]
  • [www.cs.berkeley.edu]

  • Other Repositories/Bibliography

  • DBLP
  • Save to List
  • Add to Collection
  • Correct Errors
  • Monitor Changes
by C. Mohan , Don Haderle , Bruce Lindsay , Hamid Pirahesh , Peter Schwarz
Venue:ACM Transactions on Database Systems
Citations:388 - 10 self
  • Summary
  • Citations
  • Active Bibliography
  • Co-citation
  • Clustered Documents
  • Version History

BibTeX

@ARTICLE{Mohan92aries:a,
    author = {C. Mohan and Don Haderle and Bruce Lindsay and Hamid Pirahesh and Peter Schwarz},
    title = {Aries: A transaction recovery method supporting fine-granularity locking and partial rollbacks using write-ahead logging},
    journal = {ACM Transactions on Database Systems},
    year = {1992},
    volume = {17},
    pages = {94--162}
}

Share

Facebook Twitter Reddit Bibsonomy

OpenURL

 

Abstract

In this paper we present a simple and efficient method, called ARIES ( Algorithm for Recouery and Isolation Exploiting Semantics), which supports partial rollbacks of transactions, finegranularity (e.g., record) locking and recovery using write-ahead logging (WAL). We introduce the paradigm of repeating history to redo all missing updates before performing the rollbacks of the loser transactions during restart after a system failure. ARIES uses a log sequence number in each page to correlate the state of a page with respect to logged updates of that page. All updates of a transaction are logged, including those performed during rollbacks. By appropriate chaining of the log records written during rollbacks to those written during forward progress, a bounded amount of logging is ensured during rollbacks even in the face of repeated failures during restart or of nested rollbacks We deal with a variety of features that are very Important in building and operating an industrial-strength transaction processing system ARIES supports fuzzy checkpoints, selective and deferred restart, fuzzy image copies, media recovery, and high concurrency lock modes (e. g., increment /decrement) which exploit the semantics of the operations and require the ability to perform operation logging. ARIES is flexible with respect to the kinds of buffer management policies that can be implemented. It supports objects of

Keyphrases

partial rollback    write-ahead logging    fine-granularity locking    transaction recovery method    deferred restart    increment decrement    fuzzy checkpoint    isolation exploiting semantics    repeated failure    industrial-strength transaction processing system aries    log sequence number    efficient method    medium recovery    fuzzy image copy    buffer management policy    bounded amount    appropriate chaining    nested rollback    loser transaction    high concurrency lock mode    log record    system failure   

Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2019 The Pennsylvania State University