Write-ahead logging

In <a href="/facts/Computer_science/lN3pEyPz">computer science</a>, write-ahead logging (WAL) is a family of techniques for providing <a href="/facts/Atomicity_(database_systems)/A356GsoW">atomicity</a> and <a href="/facts/Durability_(database_systems)/KHYwqzG0">durability</a> (two of the <a href="/facts/ACID/XdHkYzHN">ACID</a> properties) in <a href="/facts/Database_system/VYcpkevb">database systems</a>.
A write ahead log is an append-only auxiliary disk-resident structure used for crash and transaction recovery. The changes are first recorded in the log, which must be written to <a href="/facts/Stable_storage/tHyCo10u">stable storage</a>, before the changes are written to the database.
The main functionality of a write-ahead log can be summarized as:

<ul><li>Allow the page cache to buffer updates to disk-resident pages while ensuring durability semantics in the larger context of a database system.</li>
<li>Persist all operations on disk until the cached copies of pages affected by these operations are synchronized on disk. Every operation that modifies the database state has to be logged on disk before the contents on the associated pages can be modified</li>
<li>Allow lost in-memory changes to be reconstructed from the operation log in case of a crash.</li></ul>
In a system using WAL, all modifications are written to a <a href="/facts/Database_log/R7fDybpe">log</a> before they are applied. Usually both redo and undo information is stored in the log.
The purpose of this can be illustrated by an example. Imagine a program that is in the middle of performing some operation when the machine it is running on loses power. Upon restart, that program might need to know whether the operation it was performing succeeded, succeeded partially, or failed. If a write-ahead log is used, the program can check this log and compare what it was supposed to be doing when it unexpectedly lost power to what was actually done. On the basis of this comparison, the program could decide to undo what it had started, complete what it had started, or keep things as they are.
After a certain amount of operations, the program should perform a <a href="/facts/Application_checkpointing/KjeTCpSB">checkpoint</a>, writing all the changes specified in the WAL to the database and clearing the log.
WAL allows updates of a database to be done <a href="/facts/In-place_algorithm/Ghe2PJUF">in-place</a>. Another way to implement atomic updates is with <a href="/facts/Shadow_paging/SChW4g3x">shadow paging</a>, which is not in-place. The main advantage of doing updates in-place is that it reduces the need to modify indexes and block lists.
<a href="/facts/Algorithms_for_Recovery_and_Isolation_Exploiting_Semantics/KYLGWQQF">ARIES</a> is a popular algorithm in the WAL family.
Modern <a href="/facts/File_system/FdPm90uc">file systems</a> typically use a variant of WAL for at least file system <a href="/facts/Metadata/qt35z79C">metadata</a>; this is called <a href="/facts/Journaling_file_system/UCAaSBrD">journaling</a>.

Write-ahead logging open-in-new

Write-ahead logging