Subject: Re: timeline X of the primary does not match recovery target timeline
	Y
Mime-Version: 1.0 (Apple Message framework v1251.1)
Content-Type: text/plain; charset=us-ascii
From: Adam Tistler <atistler@gmail.com>
In-Reply-To: <1319126408.16256.66.camel@jdavis>
Date: Thu, 20 Oct 2011 12:45:43 -0400
Cc: pgsql-general@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D5696AC8-3F79-4EBF-98FE-E0DF0A66AEDA@gmail.com>
References: <34F74A50-6132-4603-8133-447B2AEF9953@gmail.com>
	<1319126408.16256.66.camel@jdavis>
To: Jeff Davis <pgsql@j-davis.com>

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:
>>=20
>> FATAL:  timeline 2 of the primary does not match recovery target
>> timeline 3
>=20
> 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).
>=20
> Did I understand your question correctly?
>=20
> Regards,
> 	Jeff Davis
>=20