The editorialized title doesn't reflect the original one ("How to Survive Database Failover – Debezium and PostgreSQL in Production"), nor does it correctly rep

The editorialized title doesn't reflect the original one ("How to Survive Database Failover – Debezium and PostgreSQL in Production"), nor does it correctly represent how these systems behave. Postgres 16 added support for replication slots on stand-by servers, which allows you to point Debezium to a promoted stand-by after failover and resume from there, no events will be missed. It required manual advancement of the stand-by slots though [1]. Postgres 17 brought full support for failover slots, fully automating the entire process [2]. [1] https://www.morling.dev/blog/logical-replication-from-postgres-stand-by-servers-debezium-and-failover-slots/#_towards_fail_over_slots https://www.morling.dev/blog/logical-replication-from-postgr... [2] https://www.morling.dev/blog/failover-replication-slots-with-postgres-17/ https://www.morling.dev/blog/failover-replication-slots-with...