Connector getting Inactive due to replication slot PID already exists

error_ replication slot is active for pid   Dan error_ replication slot is active for pid

The other application using the same configuration will show the following error message: replication slot slot_name is already active for PID x

ereport(ERROR, (errcode, errmsg(replication slot %s is active for PID %d, NameStr, active_pid))); } else if The other application using the same configuration will show the following error message: replication slot slot_name is already active for PID x

88 raja slot Currently postgres doesn't allow dropping a replication slot that's active This can make certain operations more time-consuming or stuck in production Connect ERROR: logical replication target relation has neither REPLICA IDENTITY