Data Monitoring / PostgreSQL Monitoring
PostgreSQL: Archive pipeline failures
Backups exist but WAL archival has stopped advancing. Inspect pg_stat_archiver and the configured archive destination alongside recent WAL production.
Environment and inputs: PostgreSQL 18 documentation baseline; views, extensions and permissions vary across versions and managed services.
Failure scenario
Backups exist but WAL archival has stopped advancing. Confirm the cause before choosing a fix.
Evidence to collect
Inspect pg_stat_archiver and the configured archive destination alongside recent WAL production. Record the time, affected scope and a healthy comparison interval.
Fix the confirmed cause
Repair archive delivery and verify continuity required by the recovery plan. Write the expected result first. Change one relevant setting at a time.
Check the result and hand over
Repeat the check for archive pipeline failures using the same scope and a representative interval. Check that the symptom is resolved, expected records are present and downstream results are correct. If coverage, correctness or latency worsens, restore the recorded configuration through the agreed rollback process.
Scope and precautions
Prefer read-only access and limit queries to the relevant period or dataset. This example has not been tested on your systems. Test changes in an approved environment. Keep credentials and sensitive data out of shared evidence.