Skip site navigation (1) Skip section navigation (2)

Re: BUG #5011: Standby recovery unable to follow timeline change

From: james bardin <jbardin(at)bu(dot)edu>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5011: Standby recovery unable to follow timeline change
Date: 2009-08-26 14:16:22
Message-ID: a3b675320908260716kff5de74p7b998830ba416a65@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Wed, Aug 26, 2009 at 4:40 AM, Heikki
Linnakangas<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> Is this currently possible, or do I have to send a full file-level backup to
>> sync the ex-master server with the new master?
>
> That should work. (Note that you do need to restore the ex-master from
> the old base backup; you can't just copy recovery.conf to the old
> master's data directory.)

I'm relying on an rsync for the data directories after the recovery to
bring up the ex-master.
This works fine, but I'd rather be able to simply rely on wall
shipping to keep them synced without the extra backup procedures.
Thanks for looking into this.

Is this the type of fix that would make it into the next 8.4.x release?

-jim

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-08-26 14:42:46
Subject: Re: BUG #5011: Standby recovery unable to follow timeline change
Previous:From: Tom LaneDate: 2009-08-26 13:57:33
Subject: Re: BUG #5008: Server Startup Problem - When server is configured for SSL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group