Replication - High Lag

xmin : The oldest transaction ID that this slot needs to retain How do you manage Postgres replication lag? How can I limit the number of

Oldest replication slot lag: lagging size of the most lagging replica in terms of WAL data received You can run the following SQL statement

oldest slot machine 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

crazy monkey slot demo The lag of a replication slot can be measured as the difference between the current WAL location on the primary and the last WAL position confirmed as received