Postgres replication slots grow indefinitely
Postgres replication slots grow indefinitely
What is restart_lsn? This is the start LSN of the oldest transaction which is not replicated to the target side yet Postgres won't delete the
A replication slot ensures that the WAL will not go away if the replica lags behind Without a replication slot, a primary will recycle its WAL as soon as it 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
wide slot toaster The morale of the story? Don't leave your replication slots unattended! There shouldn't be any slots which are inactive for too long For Fixing PostgreSQL database replication errors · Removing an inactive replication slot · Message: WARNING: oldest xmin is far in the past and pg_wal size growing
