Physical Replication Mechanisms in PostgreSQL
Physical Replication Mechanisms in PostgreSQL
A PostgreSQL replication slot may be stuck due to one of the following reasons: Check if the bgwriter process is healthy by inspecting its
Based on this I'd say you didn't have enough wal_keep_segments on the master, weren't using a replication slot, and either had A limitation of the PostgreSQL implementation is that replication slots are not cluster-aware: a replication slot exists solely on the instance
baking bonanza slot Also, replication slots on a given standby persist the promotion of that standby to a primary This means that in the event of a primary DB instance failover or Before replication slots, it was not possible for the primary to determine this, and you'd end up in situations where a standby was left stranded because a WAL
