Bryan Murphy wrote:
On Fri, Mar 26, 2010 at 1:32 PM, Greg Smith <greg@xxxxxxxxxxxxxxx
<mailto:greg@xxxxxxxxxxxxxxx>> wrote:
If there's another server around, you can have your
archive_command on the master ship to two systems, then use the
second one as a way to jump-start this whole process. After
fail-over, just start shipping from the new primary to that 3rd
server, now the replacement standby, and sync any files it doesn't
have. Then switch it into recovery. Much faster than doing a new
base backup from the standby on larger systems.
Every time I've tried to do this it's failed because the third server
was looking for log files starting with 00000006... but the secondary
server (new master) is now shipping files starting with 00000007...
How do I get the third server to switch over to the higher numbered
files? That's the part I was never able to overcome.
One thing it's easy to miss is that you have to save every incoming WAL
archive file on the standby, and sync them all over to the 3rd system
before you trigger the standby to be active. The archive_command has to
be active and shipping to the 3rd system before the server is triggered too.
You can think of any given standby server as a base backup and some
number of WAL segments applied to it. So long as you never let a WAL
file get applied to or generated by the standby who becomes the master
without making its way to the additional system, it should always be
possible to bring up that additional server up to date without something
being missing. The exact order of operations to ensure that in all case
is certainly not obvious though.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@xxxxxxxxxxxxxxx www.2ndQuadrant.us
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
