Monitoring PostgreSQL replication lag

Monitoring PostgreSQL replication lag oldest replication slot lag replication slots preserve WAL files, allowing the master to track standby lag xmin: This represents the oldest transaction this slot 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

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

slot terbaru 4d Oldest query start time pg_waiting_backends, gauge, wait_type Oldest xmin Age, oldest_backend_xmin_age, Count, Age in units of the Maximum lag across all asynchronous physical replication slots