From: | Piotr Gasidło <quaker(at)barbara(dot)eu(dot)org> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | pg_basebackup from new master's slave then recovery from new master. |
Date: | 2013-08-17 11:47:10 |
Message-ID: | CAF8akQswy_tGfAWEkDFkPeetvccfgsWYTvk3fiZ2twsM=30P3g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Piotr Gasidło | 2013-08-17 11:50:18 | Re: pg_basebackup from new master's slave then recovery from new master. |
Previous Message | S H | 2013-08-17 05:38:39 | Re: Commit problem in read-commited isolation level |