PostgreSQL Failback without rebuild
Hello All,
http://www.postgresql.org/message-id/CAF8Q-Gy7xa60HwXc0MKajjkWFEbFDWTG=gGyu1KmT+s2xcQ-bw@mail.gmail.com
http://www.postgresql.org/message-id/CAF8Q-Gxg3PQTf71NVECe-6OzRaew5pWhk7yQtbJgWrFu513s+Q@mail.gmail.com
http://www.postgresql.org/message-id/519DF910.4020609@vmware.com
I have been reading through some of the recent discussions about failback when in a streaming replication setup. I define failback as:
- Node A is master, Node B is slave
- Node A crashes || Node A is stopped || nothing happens
- Promote Node B to Master
- Attach Node A as slave
This is very undesirable for many users, especially if they have a very large database.
From the discussions I can see that the problem is to do with Node A writing changes to disk that Node B are not streamed before Node A crashes.
Has there been any consensus on this issue? Are there any solutions which might make it into 9.4 or 9.5? I've seen some proposals and a tool (pg_rewind), but all seem to have draw backs.
I've been looking mainly at these threads:
http://www.postgresql.org/message-id/CAF8Q-Gxg3PQTf71NVECe-6OzRaew5pWhk7yQtbJgWrFu513s+Q@mail.gmail.com
http://www.postgresql.org/message-id/519DF910.4020609@vmware.com
Cheers,
James Sewell,
PostgreSQL Team Lead / Solutions Architect
______________________________________
PostgreSQL Team Lead / Solutions Architect
______________________________________
The contents of this email are confidential and may be subject to legal or professional privilege and copyright. No representation is made that this email is free of viruses or other defects. If you have received this communication in error, you may not copy or distribute any part of it or otherwise disclose its contents to anyone. Please advise the sender of your incorrect receipt of this correspondence.
В списке pgsql-hackers по дате отправления: