full-page-write · shipping · also full_page_writes

Full-page write

A PostgreSQL full-page write records a recoverable page image in WAL to support recovery from an incomplete data-page write.

With full_page_writes enabled, PostgreSQL normally logs a page image on its first modification after a checkpoint. The image provides a reconstruction basis that ordinary change records alone may not supply. This is a PostgreSQL mechanism, not a universal name for all torn-page defenses.

Relations

related

write-ahead-log, database-checkpoint, torn-write

Advantages

• Supports reconstruction of a page interrupted during writeback. [1]

Limitations

• Adds WAL traffic; it is not a substitute for an independently recoverable backup. [1, 2]

Citations

1. PostgreSQL 18: WAL settings (accessed 2026-10-11)
2. PostgreSQL 18: Continuous Archiving and Point-in-Time Recovery (accessed 2026-10-11)
3. WAL, checkpoints and torn pages: three different recovery guarantees (accessed 2026-10-11)

JSON: /data/terms/full-page-write.json