BIG-IQ error message ''Postgres replication slot is not found''

replication slot already exists   Dan replication slot already exists

Diagnosing Jammed Replication The easiest problem to debug is a key violation: if an entry with a unique index already exists Postgres will log an error

11:55: IST DETAIL: Key = already exists Replication slot A replication slot ensures that the It sounds like you've set primary_slot_name to the same slot in all three replicas Each replica must use a different replication slot in

3 slot diffuser If it already exists, it must be empty -S slotname The specified replication slot has to exist unless the option -C is also used  This topic has been already debated in the past, including some proposed patches for PostgreSQL exists solely on the instance that