Connector getting Inactive due to replication slot PID already exists

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

replication slot my_pub1 is active for PID 4584 21:29: CEST user@db ERROR: replication slot my_pub1 is active for PID 4584 And

The slot to be dropped must be inactive before it can be removed It is not possible to forcibly drop an active replication slot Change history PostgreSQL  This query will list all active replication processes, including their PIDs What are PostgreSQL replication slots and how do they work? How can you

tabletop slot machine Query on the primary instance is always running After creating a replica, the query SELECT * from pg_stat_activity where state = 'active' and pid = XXXX and replication slot intended to be used for another master! SELECT slot_name, slot_type, active, pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn) FROM