Re: WAL log management w/ multiple slaves - Mailing list pgsql-admin

From Vasilis Ventirozos
Subject Re: WAL log management w/ multiple slaves
Date
Msg-id CAF8jcqo3dbBzE6iA_SjxQ2WH2kkHiCKq-qfzWNsSLVcdHzXg8A@mail.gmail.com
Whole thread Raw
In response to Re: WAL log management w/ multiple slaves  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-admin


On Wed, Dec 3, 2014 at 10:30 AM, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
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

 
check out OmniPITR it rocks when it comes to wal management
https://github.com/omniti-labs/omnipitr

Regards,
Vasilis Ventirozos

pgsql-admin by date:

Previous
From: Albe Laurenz
Date:
Subject: Re: WAL log management w/ multiple slaves
Next
From: Raj Gandhi
Date:
Subject: Postgres log configuration for locking