How we used delayed replication for disaster recovery with PostgreSQL

This post details the implementation and benefits of using delayed replication with PostgreSQL for disaster recovery. It explains how a delayed replica, configured with `recovery_min_apply_delay` and using archive recovery with `wal-e`, can be used for point-in-time recovery from accidental data deletions. The process involves pausing the replica, adjusting recovery targets to a specific time, and then exporting/importing recovered data. It highlights the advantages over cold backups by eliminating the need to restore a full basebackup and reducing the WAL replay window.