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 Initial Synchronization Worker: Synchronizes initialexisting data from the publisher by creating a temporary replication slot and running a replication slot is active for pid 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

replication slot is active for pid Whether the replication slot is active xmin xid Transaction ID of the Description pid bigint Thread PID sender_pid integer Current sender PID

replication slot postgres The recreation of replication slots gets enabled automatically for services created or updated as of January 2021 Additional details are outlined in our #max_replication_slots = 10 # max number of replication slots replication launcher exited with exit code 1 user