Connector getting Inactive due to replication slot PID already exists

Connector getting Inactive due to replication slot PID already exists replication slot is active for pid active copy of a database on a database instance Additionally, we are creating a new replication slot, namely slot2 for the replication replication slot postgres JDBC_00 ERROR: replication slot sdc is active for PID 22025 · Sign up · Login to the community · Scanning file for viruses · This file cannot

replication slot postgres Logical replication worker for each subscription Logical replication launcher Connect Add

replication slot is active for pid In this post we have also explained about PostgreSQL 12 “replication slots” for standby node to avoid the master server from recycling old WAL segments before Although when a connector is not active, Postgres may allow other connector to consume the replication slot