crash: replication slot already exists #22 - supabaserealtime

crash: replication slot already exists #22 - supabaserealtime replication slot already exists 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 replication slot does not exist done by pg_ctl promote When the failback to VPSFRSQLPAC1 is performed, the replication slot standby1 already exists ,

replication slot does not exist replication slot, increasing this value just causes a different connection error saying the replication slot is already in use Here is the

replication slot postgres 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 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