Logical replication slots stuck in catchup on a very large table

Logical replication slots stuck in catchup on a very large table replication slot is active for pid When this slot should be active, because you have a secondary site configured using that slot, look for the PostgreSQL logs for the secondary site, to view why replication slot does not exist service: Can't open PID file runrepmgr after Replication slots: OK

replication slot does not exist To resolve these errors, remove the used replication slots, or increase the value of the max_replication_slots parameter Resolution Remove used replication

replication slot active_pid : The PID of the WAL sender process that is using this slot, if active xmin : The oldest transaction ID that this slot needs to retain  replication slot started lagging