Logical replication slots stuck in catchup on a very large table

Caused by: io debezium DebeziumException: Failed to start replication stream at LSN{11284201208}; when setting up multiple connectors for the same database

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

error 1089 JDBC_00 ERROR: replication slot sdc is active for PID 22025 · Sign up · Login to the community · Scanning file for viruses · This file cannot

error slot slot are reserved forever Message: FATAL: could not start WAL streaming: ERROR: replication slot