Message-ID: <1426334484.3775.6.camel@gmail.com>
Subject: Re: WAL log management w/ multiple slaves
From: jaime soler <jaime.soler@gmail.com>
Reply-To: jaime.soler@gmail.com
To: Wells Oliver <wellsoliver@gmail.com>
Cc: pgsql-admin@postgresql.org
Date: Sat, 14 Mar 2015 13:01:24 +0100
In-Reply-To: 
 <CAOC+FBUxYXrz0vZ5pkHAbMLfUPXsq3sTyC_PvcLFhSQ0riFtng@mail.gmail.com>
References: 
 <CAOC+FBUxYXrz0vZ5pkHAbMLfUPXsq3sTyC_PvcLFhSQ0riFtng@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin