Re: Timeline switch problem with streaming replication with 3 nodes

From: Stuart Bishop <stuart(at)stuartbishop(dot)net>
To: Mads(dot)Tandrup(at)schneider-electric(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Timeline switch problem with streaming replication with 3 nodes
Date: 2012-09-25 04:38:21
Message-ID: CADmi=6PMh3cR4dN_uczv346qrOo9Gv3ujjO8dnq4YE=qnYy9rA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Sep 24, 2012 at 7:37 PM, <Mads(dot)Tandrup(at)schneider-electric(dot)com> wrote:

> I've found a discussion
> (http://archives.postgresql.org/pgsql-general/2011-12/msg00553.php) on a
> similar issue a while back. They talk about sharing WAL files as the
> solution. But I thought that the idea with streaming replication was that I
> would not need a shared storage.
>
> Is that the only solution or is there another way?

Things should work if you manually copy across the 0000010.history
file from the new master's pg_xlog directory to the slave's.

This method isn't documented, but seems to work. I believe the problem
is being fixed, by letting the history files be shipped along with the
WAL files.

http://archives.postgresql.org/pgsql-general/2011-12/msg00456.php

--
Stuart Bishop <stuart(at)stuartbishop(dot)net>
http://www.stuartbishop.net/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Amit Kapila 2012-09-25 04:56:19 Re: In one of negative test row-level trigger results into loop
Previous Message ichBinRene 2012-09-25 03:27:56 plpython2u not getting any output -> on independent script I get the desired output