Postgres WAL Overflow without Replication volumes -

Postgres WAL Overflow without Replication volumes - replication slot does not exist However, the above does not use replication slots, and if you want Do + * not error out if the slot already exists, other errors are already + replication slot does not exist The PostgreSQL replication slot used by the Pipeline is not able to complete the IO event WALRead, and is waiting for data to be read from the

replication slot does not exist The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL

replication slot postgres replication slot geo_secondary_my_domain_com does not exist? This occurs when PostgreSQL does not have a replication slot for the secondary node by that name 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