PostgreSQL Replication Slots

Message: replication slot geo_secondary_my_domain_com does not exist This If you suspect the root cause is already resolved, you can manually retry

PostgreSQL Replication Slots Do + * not error out if the slot already exists, other errors are already + * reported by CreateReplicationSlot() + * + if (!stream->temp_slot

Message: replication slot geo_secondary_my_domain_com does not exist This If you suspect the root cause is already resolved, you can manually retry

replication slot postgres The publication has to be created before the replication slot or else it will not find the publication once it does

If for example PostgreSQL Native Replication is already in use and is using all of the currently configured replication slots, increase the value to allow for

replication slot 1 Answer 1 I can't reproduce the issue you describe when restarting a given connector instance It should detect that the slot already exists

After recovering, the Debezium connector can create the replication slot on the newly promoted database if none exists, however there can be some delay in doing