Postgresql 11 logical replication - stuck in `catchup` state

Postgresql 11 logical replication - stuck in `catchup` state error_ replication slot is active for pid Connect ERROR: logical replication target relation has neither REPLICA IDENTITY error slot The other application using the same configuration will show the following error message: replication slot slot_name is already active for PID x

error slot @kiwicopple This is an ongoing problem with, for example, ECS tasks in AWS, when the new one has started before the old one is killed The old one hasn't

error_ draggable element must have an item slot Fixing PostgreSQL database replication errors · Removing an inactive replication slot · Message: WARNING: oldest xmin is far in the past and pg_wal size growing  This option causes the command to wait if the slot is active until it becomes inactive, instead of the default behavior of raising an error BASE_BACKUP