hesela.devWAL archiving
WAL archiving preserves write-ahead-log segments for later recovery before normal log recycling can remove them.
PostgreSQL 18 archives completed segments; low activity can delay archival. Local commit durability therefore does not by itself prove archive coverage. [1]
Relations
- related
- point-in-time-recovery, recovery-target, write-ahead-log, backup-verification
Limitations
- A successful archive command must mean the file is safely preserved, not merely that copying was attempted. [1]
- archive_timeout schedules segment switches, not completed transfers; treating it alone as an end-to-end RPO bound is unjustified. This is Hesela's inference from the documented mechanism. [3]
- last_archived_wal does not prove all earlier segments were archived: ordering is not guaranteed. Some failures that restart the archiver are not counted in pg_stat_archiver. [4, 1]