From: Adam Tistler <atistler@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: pgsql-general@postgresql.org
Subject: Re: timeline X of the primary does not match recovery target timeline Y
Date: Thu, 20 Oct 2011 12:45:43 -0400
Message-ID: <D5696AC8-3F79-4EBF-98FE-E0DF0A66AEDA@gmail.com> (raw)
In-Reply-To: <1319126408.16256.66.camel@jdavis>
References: <34F74A50-6132-4603-8133-447B2AEF9953@gmail.com>
<1319126408.16256.66.camel@jdavis>
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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: atistler@gmail.com, pgsql@j-davis.com, pgsql-general@postgresql.org
Subject: Re: timeline X of the primary does not match recovery target timeline Y
In-Reply-To: <D5696AC8-3F79-4EBF-98FE-E0DF0A66AEDA@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox