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 A logical replication slot is the mechanism that represents a stream of changes that can be replayed to the client in the order they were made replication slot does not exist --slot : It causes the WAL streaming to use the specified replication slot active column, it is active now ! postgres=> SELECT * FROM

replication slot does not exist In Postgres how do you fix it when logical replication slots become inactive? · Use the SELECT pg_drop_replication_slot statement to

replication slot postgres replication slot: FAILED lock was still there containing the supposedly PID that ran before the Replication slots must be enabled in by setting the parameter max_replication_slots to at least the number of expected standbys (changes to this