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 = 5 wal_keep_segments = 32 checkpoint_segments = 8 wal_level = hot_standby on slave: recovery.conf standby_mode = on primary_conninfo = 'host=172.16.135.205 port=5432 user=replicator password=replicator' trigger_file = '/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. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
