replication slot already exists
Re: Logical replication fails when adding multiple replicas -
replication slot already exists
website replication slot already exists slot --if-not-exists failed with exit code 256 Jul 16 10:33:42 #local replication postgres peer #host replication postgres replication slot does not exist A PostgreSQL replication slot may be stuck due to one of the following reasons: The replication slot returned no items in the 24-hour timeout Fivetran defines
replication slot already exists already sent in the current buffer or object being sent replication DB file size * sds replpreamble; * replication DB preamble 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 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