Logical replication slots stuck in catchup on a very large table

The other application using the same configuration will show the following error message: replication slot slot_name is already active for PID x

ERROR: replication slots can only be used if max_replication_slots > 0 In • pid: This represents the process ID of the wal_receiver process in charge of

error slot When replication slots is enabled, you might end up running out of disk space due to PostgreSQL trying to retain WAL files requested by a replication slot

error_ replication slot is active for pid Monitoring Replication Slots Each BDR node keeps: One replication slot per active BDR peer; One group replication slot For example: Toggle Wrap Copy bdrdb