ERROR: replication slot debezium already exists

replication slot already exists   Dan replication slot is active for pid

already exists 15:53: UTC LOG: background move the step to create the replication slot to after we executed the

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  slot is specified and a slot with 48 the specified name already exists 49 156 157 --drop-slot 158 Drop the replication slot with the name specified in --slot

which gpu slot to use already been removed 19:01:10 UTC Recovering a read replica using its replication slot is faster than recovering from Amazon S3 archive  because it's one more step to run CREATE_REPLICATION_SLOT manually So I propose the attached tiny patch to just create the slot