Postgres replication slots grow indefinitely

PostgreSQL Replication Slots oldest replication slot lag True if this is a temporary replication slot Temporary slots are not saved The oldest transaction that this slot needs the database to retain 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

agent slot online 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