Physical replication slots and xlog space exhaust

From: Alex Balashov <abalashov(at)evaristesys(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Physical replication slots and xlog space exhaust
Date: 2019-04-26 18:28:30
Message-ID: 5C492AE6-272A-451D-9563-59A93162F2E6@evaristesys.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

We have a recurring human error problem where, upon doing a base copy to a new slave, we accidentally leave the master’s physical replication slots in place, forgetting to drop them from the slave config.

After a while, transaction logs pile up on the slave — since no slaves are consuming them — and blow it out. This then causes the slave to stop downloading transaction logs from the master, causing them to accumulate due to its own replication slots.

I understand the ultimate solution to this is to mind one’s replication slots and monitor disk usage fastidiously, but is there a config parameter for the maximum overall amount of transaction logs that can be kept accumulated on the master, irrespectively of physical replication slots commitments?

Thanks!

—
Sent from mobile, with due apologies for brevity and errors.

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message arvind chikne 2019-04-26 19:22:24 Re: BDR
Previous Message Alvaro Aguayo Garcia-Rada 2019-04-26 18:15:59 Re: BDR