Proceedings of IEEE 9th International Conference on Data Engineering
DOI: 10.1109/icde.1993.344071
|View full text |Cite
|
Sign up to set email alerts
|

Post-crash log processing for fuzzy checkpointing main memory databases

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
23
0

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 25 publications
(23 citation statements)
references
References 8 publications
0
23
0
Order By: Relevance
“…Li et al [17] also suggest run-time optimizations for reduc ing log size by using shadow pages for updates but also require all shadow updates as well as the log buffer to reside in non volatile memory. Lehman and Carey's recovery algorithm [14] also requires presence of non-volatile RAM to be able to store log tails.…”
Section: Related Workmentioning
confidence: 99%
“…Li et al [17] also suggest run-time optimizations for reduc ing log size by using shadow pages for updates but also require all shadow updates as well as the log buffer to reside in non volatile memory. Lehman and Carey's recovery algorithm [14] also requires presence of non-volatile RAM to be able to store log tails.…”
Section: Related Workmentioning
confidence: 99%
“…As fuzzy checkpointing in MMDB has little synchronization with executing transactions, a consecutive fuzzy checkpointing has been considered in some previous MMDB recovery methods [14,11]. That is, the end chkpt of a checkpoint becomes the begin chkpt of the next checkpoint.…”
Section: Applying To Segmented Mmdbmentioning
confidence: 99%
“…Table 2 shows some parameters and their default values. They are derived from [11] and [14]. For the simplicity, the recovery time of the last complete checkpoint is considered.…”
Section: Performance Evaluationmentioning
confidence: 99%
See 2 more Smart Citations