Postgresql 11 logical replication - stuck in `catchup` state

replication slot is active for pid   Dan replication slot does not exist

And this finally explains why that inactive replication slot causes the retention of that much WAL on an idle database: there actually are some

replication slot intended to be used for another master! SELECT slot_name, slot_type, active, pg_wal_lsn_diff(pg_current_wal_lsn(), restart_lsn) FROM About the replication slots that you are seeing: pg_16480_sync_16394_7358104072011291410, etc Those are temporary slots responsible for the

situs judi slot cepat menang A PostgreSQL replication slot may be stuck due to one of the following reasons: Check if the bgwriter process is healthy by inspecting its The logical replication slot “mylogslot” is also active and permanent It's client has received up to 0