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.
Keep practising Database Management Systems
Browse all Database Management Systems questions for GATE CSE, or explore more Computer Science topics.