Re: How should pg_standby get over the gap of timeline? - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: How should pg_standby get over the gap of timeline?
Date
Msg-id 3f0b79eb0811200650x1f34c741wd8f895bb7bee3ad7@mail.gmail.com
Whole thread Raw
In response to Re: How should pg_standby get over the gap of timeline?  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: How should pg_standby get over the gap of timeline?
List pgsql-hackers
Hi, Heikki. Thanks for the comment!

On Thu, Nov 20, 2008 at 11:24 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> Fujii Masao wrote:
>>
>> In the current Synch Rep patch, the standby cannot catch up with the
>> primary which has a bigger timeline.
>
> That would only happen if you've performed an archive recovery in the
> primary. If you've done PITR in the primary, I don't think there's any
> guarantee that it's even possible to catch up the standby. The standby might
> already have replayed a WAL file from an earlier timeline, that isn't part
> of the history of the bigger timeline.

I assume the situation of making the standby (the original primary) catch up
with the primary (the original standby) after failover. Since a timeline is
incremented when a failover finishes archive recovery on a standby, the
timelines differ between two servers.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: "Pavan Deolasee"
Date:
Subject: Re: Hot Standby (commit fest version - v5)
Next
From: Magnus Hagander
Date:
Subject: Error arguments in pl_exec.c