Hi,
First post, forgive me if this is better suited to pgsql-general.
I've got streaming replication set up with two slave servers (PostgreSQL 9.0 on
Ubuntu 10.04 LTS). The master pushes the WAL to an NFS export, which is in turn
mounted on and picked up by the two slaves.
The problem I have i
I think you are using Log-Shipping not Streaming-Replication
http://www.postgresql.org/docs/9.0/static/different-replication-solutions.html
I would just make 2 copies of the WAL file one for each slave in different
folders.
That way if one slave is offline for a period of time it can catch up when
Tim wrote:
> I would just make 2 copies of the WAL file one for each slave in
> different folders.
> That way if one slave is offline for a period of time it can
> catch up when it comes back online.
If you used hard links, that wouldn't even take any extra disk
space (beyond the directory spa
On 20 May 2011, at 12:53, Tim wrote:
> I think you are using Log-Shipping not Streaming-Replication
> http://www.postgresql.org/docs/9.0/static/different-replication-solutions.html
I'm using streaming replication with log shipping as a fallback as per
walkthrough here:
http://brandonkonkle.com/
On Fri, May 20, 2011 at 7:59 PM, Ben Lancaster
wrote:
> The problem I have is that pg_archivecleanup (running on one of the slaves)
> was removing WAL logs before the other slave had picked up the changes, thus
> breaking replication for the second slave. As an interim fix, I simply
> disabled
I don't actually use streaming replication, but what exactly is the problem
with the hard link for each slave solution, and the slaves handling there
own pg_archivecleanup?
On Fri, May 20, 2011 at 11:30 AM, Fujii Masao wrote:
> On Fri, May 20, 2011 at 7:59 PM, Ben Lancaster
> wrote:
> > The pro
On Fri, May 20, 2011 at 4:58 PM, Tim Lewis wrote:
> I don't actually use streaming replication, but what exactly is the problem
> with the hard link for each slave solution, and the slaves handling there
> own pg_archivecleanup?
Doing so creates a single point of failure.
We had problems with l
