https://bitpage.me/tags/replication/Recent content in Replication on BitPageHugoen-usWed, 29 Jul 2026 06:43:03 +0000https://bitpage.me/databases/postgres-conflict-with-recovery-patroni-haproxy/Wed, 29 Jul 2026 06:43:03 +0000https://bitpage.me/databases/postgres-conflict-with-recovery-patroni-haproxy/Short answer: Both top search results for canceling statement due to conflict with recovery are wrong on a Patroni cluster with replication slots and one replica. hot_standby_feedback=on parks the xmin horizon inside the slot, where it survives the replica’s death and bloats the primary; raising max_standby_streaming_delay converts held-back replay into the exact lag your load balancer ejects the replica for. What I shipped instead was removing on-marked-down shutdown-sessions from the read backend, after measuring that replica lag is 11.