From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Warm standby failover mechanism |
Date: | 2009-02-25 09:35:02 |
Message-ID: | 20090225093502.GD3820@merkur.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Feb 25, 2009 at 09:26:26AM +0000, Thom Brown wrote:
> We've set up a primary server in archive mode to continuously archive to an
> NFS mount, and the standby server to continuously recovery from that
> directory (although I'm not sure that's actually working... I've probably
> overlooked something). The problem we face is working out how to tell the
> standby server that it is the primary. Yes this can be done with a trigger
> file in /tmp, but how would that automatically appear there?
Think backwards: How would it automatically *dis*appear from
there. Have the secondary create it and check for existance
at regular intervals. Have the primary delete it at slightly
shorter intervals.
When the secondary finds it again after the check interval
the primary didn't delete it. Wait some more for good
measure and/or try to ping the primary some other way...
Just my 2 cents,
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2009-02-25 09:48:13 | Re: Warm standby failover mechanism |
Previous Message | Ivan Sergio Borgonovo | 2009-02-25 09:32:08 | Re: where to divide application and database |