Part 1 of 5 · 1 min read
Why this page comes first
In this module you will
- Trace the path a single write takes from an application's statement to permanent storage.
- Explain why a database writes a log entry before changing the actual data page.
- Explain why a modified page can sit in memory for a while before reaching disk.
- Recognize why this layered write path sets up Level 7's transaction modules and Level 8's recovery modules.
Every earlier page in this level described storage as a static structure: media, blocks, files, pages, a buffer pool. This closing page follows one single write all the way through that structure. The pieces click together as a path, not a list of parts.