pg_basebackup from new master's slave then recovery from new master. - Mailing list pgsql-general

From Piotr Gasidło
Subject pg_basebackup from new master's slave then recovery from new master.
Date
Msg-id CAF8akQswy_tGfAWEkDFkPeetvccfgsWYTvk3fiZ2twsM=30P3g@mail.gmail.com
Whole thread Raw
Responses Re: pg_basebackup from new master's slave then recovery from new master.  (Piotr Gasidło <quaker@barbara.eu.org>)
Re: pg_basebackup from new master's slave then recovery from new master.  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-general
All on 9.3beta2. Current setup:

server1 (MASTER) -> server2 (SLAVE) -> server3 (SLAVE)

server2 is hot_standby and gets WALs from server1
server3 is hot_standby and gets WALs from server2

In every recovery.conf I have:

recovery_target_timeline='latest'

Now i do switchover by touching recovery.conf's trigger_file on server2.

server1 (OLD MASTER)
server2 (NEW MASTER) -> server3 (SLAVE)

Then, I take down server1 (OLD MASTER), do fresh pg_basebackup data
from server3 (SLAVE) to server1 (OLD MASTER).

Now:

1. I edit recovery.conf on server1 to NOT point to server3 (SLAVE) but
server2 (NEW MASTER) and start server1
2. I edit recovery.conf on server2 to NOT point to server2 (NEW
MASTER) but server3 (OLD MASTER) and restart server3

I get this replication setup:

server2 (NEW MASTER) -> server2 (OLD MASTER, SLAVE) -> server3 (SLAVE)

Are these (1,2) operations safe? I did it on test environment but I
need to be sure if I won't loose any data doing such things.

--
Piotr Gasidło


pgsql-general by date:

Previous
From: S H
Date:
Subject: Re: Commit problem in read-commited isolation level
Next
From: Piotr Gasidło
Date:
Subject: Re: pg_basebackup from new master's slave then recovery from new master.