github
/
developer-roadmap
mirror of https://github.com/kamranahmedse/developer-roadmap.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Roadmap to becoming a developer in 2022
3099 Commits
211 Branches
4 Tags
446 MiB
 
 
 
 
 
developer-roadmap/src/data/roadmaps/postgresql-dba/content/105-configuring-postgresql/101-write-ahead-log.md

2.9 KiB
Raw Blame History

Write-ahead Log

Write Ahead Log (WAL)

The Write Ahead Log (WAL) is an essential component of PostgreSQL's architecture. It ensures data consistency and durability by recording all the changes made to the database before they are actually applied to the data files. When a transaction is committed, its data is written to the WAL, and only after that, it is applied to the database.

How WAL works

The basic flow of data through a PostgreSQL system with WAL includes:

  1. Changes made to the database are first recorded in the WAL.
  2. WAL data is flushed to disk periodically or when a transaction commits.
  3. Checkpoints occur at intervals, ensuring all changes are applied to the database files.
  4. In case of a crash, the WAL is used to recover the uncommitted transactions.

This process guarantees that even if the database crashes, all the committed transactions can be recovered by reapplying the WAL entries.

Benefits of WAL

  • Data integrity: WAL ensures that the data remains consistent across crashes or failures, as it logs all the changes before they are written to the data files.
  • Crash recovery: In case of a crash, the WAL can be used to recover the committed transactions by replaying them.
  • Performance improvements: Periodic flushing of WAL data reduces the number of random I/O operations and improves write performance.
  • Support for replication and backup: WAL can be archived and used for Point-In-Time Recovery (PITR). Additionally, it enables streaming replication and other advanced techniques to ensure high availability.

Configuring WAL

You can configure WAL by adjusting the postgresql.conf file or by modifying the startup command options. Here are some important configuration settings related to WAL:

  • wal_level: Determines the amount of information written to the WAL. Set it to 'minimal', 'replica', or 'logical'.
  • fsync: Determines if the PostgreSQL server should request the operating system to flush the WAL data to disk. Set it to 'on' (recommended) for the majority of situations or 'off' to improve performance at the cost of data integrity.
  • synchronous_commit: Specifies whether transaction commits should wait for WAL records to be flushed to disk. Set it to 'on' (default) for full transaction durability or 'off' for improved write performance at the risk of losing recent transactions.

In addition to these settings, there are several other options related to WAL archiving, checkpoint settings, and replication. For a complete list, refer to the official documentation.

In conclusion, Write Ahead Log (WAL) is a vital part of PostgreSQL's architecture that ensures data consistency, durability, and overall performance. Understanding and configuring WAL settings can help you tailor your PostgreSQL database to match your specific requirements and performance goals.