Logical replication slots stuck in catchup on a very large table

error_ replication slot is active for pid   Dan error_ replication slot is active for pid

we have couple Postgres RDS connectors and we face sometimes the same error with the replication slot being active

As mentioned earlier, each subscription receives changes from a replication slot on the remote side Additional table Debezium stops streaming: ERROR: cannot advance replication slot to XXXXXXXXX, minimum is YYYYYYYY · What Debezium connector do you use and what version? · What

progressive slot we have couple Postgres RDS connectors and we face sometimes the same error with the replication slot being active  @myazid then there's something really strange in your setup since the logs you provided says that the replication slot has been created, look