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

From jaime soler
Subject Re: WAL log management w/ multiple slaves
Date
Msg-id 1426334484.3775.6.camel@gmail.com
Whole thread Raw
In response to WAL log management w/ multiple slaves  (Wells Oliver <wellsoliver@gmail.com>)
List pgsql-admin
El mar, 02-12-2014 a las 10:30 -0800, Wells Oliver escribió:
> 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.

Maybe you should use new feature of postgresql 9.4, replication slot:

"Replication slots provide an automated way to ensure that the master
does not remove WAL segments until they have been received by all
standbys, and that the master does not remove rows which could cause a
recovery conflict even when the standby is disconnected."
>
> I thought I could just cron up a removal of logs older than X days,
> which seems pretty easy, but not sure.
>
>
> Thanks!
>
>
> --
> Wells Oliver
> wellsoliver@gmail.com




pgsql-admin by date:

Previous
From: Thomas Kellerer
Date:
Subject: Re: PITR compatible backup with exclusion
Next
From: Josef Springer
Date:
Subject: Re: Installing PostgreSQL fails