How do you monitor and manage PostgreSQL replication slot lag?

High replica_lag means that the replica can't apply replication changes fast enough The total lag can be observed via replica_byte_lag metric, which has labels

How do you monitor and manage PostgreSQL replication slot lag? A newly created standby is not a valid failover-promotion candidate for a logical replication primary until an initial period where slots exist

High replica_lag means that the replica can't apply replication changes fast enough The total lag can be observed via replica_byte_lag metric, which has labels

demo slot money train 3 I have replication slots which are inactive and their xmin date is now a few days old This matches up with oldest replication slot lag metric

Spikes in Oldest Replication Slot Lag · Mohammad Hafizullah · alex @ · Christophe Pettus

oldest slot machine if there's no circle placed after, it will loop around to the oldest one GGE - Damage Replication -

replication slot, nil, (>= 0 oldest transaction that this slot needs the database to retain VACUUM