Re: Warm standby failover mechanism

From: Thom Brown <thombrown(at)gmail(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Warm standby failover mechanism
Date: 2009-02-25 09:48:13
Message-ID: bddc86150902250148t17acd5eeled757de0edb4ee92@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

2009/2/25 Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>

>
> 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...
>
>
Thanks for the suggestion. I'm wondering what the chances of such a
create/delete system would have of accidentally causing failover? Is it
possible to use the archive command parameter to firstly run the pg_standby
command, and follow it by a touch /tmp/pg.triggerfile by using &&?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eus 2009-02-25 09:50:58 Can I use a query with UPDATE on its SET?
Previous Message Karsten Hilbert 2009-02-25 09:35:02 Re: Warm standby failover mechanism