From: Adam Tistler <atistler@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: timeline X of the primary does not match recovery target timeline Y
Date: Mon, 26 Sep 2011 08:54:43 -0400
Message-Id: <34F74A50-6132-4603-8133-447B2AEF9953@gmail.com>
To: pgsql-general@postgresql.org
Mime-Version: 1.0 (Apple Message framework v1244.3)

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

Relevant info:

on master: postgresql.conf

max_wal_senders =3D 5
wal_keep_segments =3D 32
checkpoint_segments =3D 8
wal_level =3D hot_standby

on slave: recovery.conf

standby_mode =3D on
primary_conninfo =3D 'host=3D172.16.135.205 port=3D5432 user=3Dreplicator =
password=3Dreplicator'
trigger_file =3D '/tmp/pgsql.trigger'

everything in postgresql.conf on the slave is default related to =
replication.


On a side note I am slightly confused as to why someone would use =
"archive mode/restore_command" in combination with streaming =
replication.  As I stated above, I am not archiving/restoring on either =
the master or slave, I am simply relying on streaming replication.... is =
this the wrong approach??


Thanks in advance for the help.=