Logical replication slots stuck in catchup on a very large table

Logical replication slots stuck in catchup on a very large table error_ replication slot is active for pid service: Can't open PID file runrepmgr after Replication slots: OK error slot Streaming replication has stopped: You get this error when streaming replication between the primary and replica instances breaks down In this case,

error slot This occurs when PostgreSQL does not have a replication slot for the secondary by that name You may want to rerun the replication process on the secondary How

error 1089 service: Can't open PID file runrepmgr after Replication slots: OK Debezium stops streaming: ERROR: cannot advance replication slot to XXXXXXXXX, minimum is YYYYYYYY · What Debezium connector do you use and what version? · What