Write-Ahead Log

A technique that records every change to a sequential log before applying it to the actual data, ensuring atomicity and crash recovery.

2 articlesLast mentioned

A write-ahead log (WAL) is a technique in which a database or storage system records each change to an append-only log file before modifying the data itself. Because the actual data structures are updated only after the log entry is durable, the system can replay the log after a crash to recover or roll back changes. It is the standard method for guaranteeing the atomicity and durability of transactions.

Most databases, including PostgreSQL, SQLite, and MySQL's InnoDB, use it, and because it involves only sequential writes it is faster than random writes. In distributed systems a single log shared by many nodes is also used to establish the order of writes, in which case appending to the end of the log becomes the serialization point.

This entry is based on AIPOST articles and widely known facts. If something is wrong, please send us a correction request.

Articles covering this entry

  • Pando: The Git Backend OpenAI Built for a 2,442% Surge in CommitsAI News ·

    â–² Three-Phase Commit and Write-Ahead Log bottlenecks

    Read article
  • Past Git's Breaking Point: Anthropic's Scion and 30,000 Merges a DayAI News ·

    Scion's basic unit is the changeset, an entry in a write-ahead log, an append-only record of changes kept in order.

    Read article

Found a mistake or missing an entry?

Wiki entries are based on AIPOST articles and widely known facts. If an entry is wrong, send us a correction request and we will check and fix it. Names from new articles are added to the wiki after the article is published.