Re: timeline X of the primary does not match recovery target timeline Y - Mailing list pgsql-general

From Adam Tistler
Subject Re: timeline X of the primary does not match recovery target timeline Y
Date
Msg-id D5696AC8-3F79-4EBF-98FE-E0DF0A66AEDA@gmail.com
Whole thread Raw
In response to Re: timeline X of the primary does not match recovery target timeline Y  (Jeff Davis <pgsql@j-davis.com>)
Responses Re: timeline X of the primary does not match recovery target timeline Y  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-general
Yes you understood correctly.  Would the same apply for a hot standby situation?

On Oct 20, 2011, at 12:00 PM, Jeff Davis wrote:

> On Mon, 2011-09-26 at 08:54 -0400, Adam Tistler wrote:
>> I am trying to set up master/slave warm standby streaming replication
>> (9.1).  I am not doing archiving/log shipping.  I have read that you
>> cannot reverse roles between the master and slave, and that once a
>> slave is "promoted", you need to use  pg_basebackup or rsync to copy
>> files from the newly promoted master to the old master.  I am fine
>> with this, however, in my case all I am trying to do is re-enable the
>> slave to be in recovery mode. I am doing this by deleting the trigger
>> file ( which I had originally created to promote the slave to master )
>> and moving recovery.done to recovery.conf, then restarting postgres.
>> As a result I get the following error:
>>
>> FATAL:  timeline 2 of the primary does not match recovery target
>> timeline 3
>
> Once it's promoted to a primary, you can't set it to start recovering
> from another system again (without taking a new base backup).
>
> Did I understand your question correctly?
>
> Regards,
>     Jeff Davis
>


pgsql-general by date:

Previous
From: Ronan Dunklau
Date:
Subject: Postgresql - FDW, ForeignScanState and subqueries
Next
From: Jeff Davis
Date:
Subject: Re: timeline X of the primary does not match recovery target timeline Y