Instant recovery with write-ahead logging

Härder, Theo; Sauer, Caetano; Graefe, Goetz; Guy, Wey

doi:10.1007/s13222-015-0204-3

Cited by 8 publications

(1 citation statement)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…WBL also does not require an WALstyle undo phase. Instead, the DBMS only tracks the transactions active in the current group commit interval as determined by the analysis phase, so that it can ignore the effects of the associated uncommitted transactions [15,44,46]. In case of a transaction failure, the transaction manager rolls back any dirty changes flushed to NVM using the meta-data that it records in the dirty tuple table.…”

Section: Logging and Recoverymentioning

confidence: 99%

How to Build a Non-Volatile Memory Database Management System

Arulraj

Pavlo

2017

Proceedings of the 2017 ACM International Conference on Management of Data

View full text Add to dashboard Cite

The difference in the performance characteristics of volatile (DRAM) and non-volatile storage devices (HDD/SSDs) influences the design of database management systems (DBMSs). The key assumption has always been that the latter is much slower than the former. This affects all aspects of a DBMS's runtime architecture. But the arrival of new non-volatile memory (NVM) storage that is almost as fast as DRAM with fine-grained read/writes invalidates these previous design choices. In this tutorial, we provide an outline on how to build a new DBMS given the changes to hardware landscape due to NVM. We survey recent developments in this area, and discuss the lessons learned from prior research on designing NVM database systems. We highlight a set of open research problems, and present ideas for solving some of them. 1 NVM is also referred to as storage-class memory or persistent memory.

show abstract

Section: Logging and Recoverymentioning

confidence: 99%