Logical replication slots stuck in catchup on a very large table

Currently postgres doesn't allow dropping a replication slot that's active This can make certain operations more time-consuming or stuck in production

Active: inactive since Wed 13:34:08 +03; 26s ago Docs Replication slot: FAILED (replication slot 'barman' doesn't exist Please

replication slot already exists Although when a connector is not active, Postgres may allow other connector to consume the replication slot

replication slot active active_pid xmin catalog_xmin