Logical replication slots stuck in catchup on a very large table

error_ replication slot is active for pid   Dan error slot

Previous PostgreSQL logs shows usage of the replication slot with 2 different PIDs with a delay between the 2 calls of less than a minute

ERROR: could not create replication slot sub1: ERROR: all ERROR: replication origin with OID 1 is already active for PID 5566  Problem of the Logical Replication Slot Failover in a PostgreSQL Cluster create_slot=false, enabled=true, slot_name=repslot); After

scarab kingdom 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 ERROR: could not create replication slot localharvest: ERROR: logical decoding cannot be used while in recovery SELECT slot_name, slot_type, active