Home › GATE CSE › computerscience › Database Management Systems › Fuzzy checkpoints differ from naive checkpoints by
Fuzzy checkpoints differ from naive checkpoints by
Atransactions continue while dirty pages flush in background
Bskipping the flush step entirely
Cwriting only the commit log records, not the data pages
Dusing a separate disk for the checkpoint marker
Answer & Solution
Correct answer: A. transactions continue while dirty pages flush in background
A naive checkpoint freezes all transactions while every dirty page flushes. That's too slow for production. Fuzzy checkpoints let writers keep running and flush dirty pages in the background; the checkpoint record records which pages are still being written. Recovery handles the in-flight state correctly. Skipping the flush would break the checkpoint guarantee.
Related questions
The main reasons production DBMSs avoid shadow paging in favour of WAL are that shadow pagWhat is the purpose of a Compensation Log Record (CLR) in ARIES?ARIES recovery is structured as exactlyIn standard log-based recovery, the order of operations isAfter a crash, with checkpointing, the recovery system scans the logA complete log record for a write operation includesPer WAL semantics, a transaction is officially committed at the momentThe write-ahead rule states that