| From: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
|---|---|
| To: | "Wells Oliver *EXTERN*" <wellsoliver(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: WAL log management w/ multiple slaves |
| Date: | 2014-12-03 08:30:14 |
| Message-ID: | A737B7A37273E048B164557ADEF4A58B17DA73E2@ntex2010a.host.magwien.gv.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Wells Oliver wrote:
> Hi all. I currently have one master and one slave, and the slave cleans up the unneeded WAL files via
> pg_archivecleanup.
>
> I'm adding a third slave and I was wondering what the best practices are in terms of managing these
> WAL files when there's more than one dependent server, in a situation where you can't have a slave
> removing the files.
>
> I thought I could just cron up a removal of logs older than X days, which seems pretty easy, but not
> sure.
cron would work fine.
My scripts clean up old archived WAL as part of the backup job - that way I can be sure
that no archives are deleted unless they have been backed up first.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vasilis Ventirozos | 2014-12-03 10:06:52 | Re: WAL log management w/ multiple slaves |
| Previous Message | David G Johnston | 2014-12-03 06:19:54 | Re: pgpool use up memory |