Re: pgpool 2.5b2 released

From: "Julian Scarfe" <julian(at)avbrief(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: pgpool 2.5b2 released
Date: 2005-02-06 09:34:53
Message-ID: 158601c50c2f$1e2a44d0$0600a8c0@Wilbur
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> After takin a swig o' Arrakan spice grog, julian(at)avbrief(dot)com ("Julian
Scarfe") belched out:
> > So all I'm looking for is a way for pgpool to shout if it detects a
> > failure. That could initiate the investigation of the other
> > criteria required for failover.
>
> _There_ lies the one change that is needed. Given that, some outside
> 'oracle' can be used to decide if it's appropriate to do a FAILOVER.
>
> It's quite important for this not to be deeply embedded in pgpool...

I think we have a consensus on that. So what's the most sensible mechanism
for the "shout". Since I posted my original question, I realized that
pgpool notes a failure of either master or slave in its log. Would we want
something more proactive?

Julian

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jean-Paul Argudo 2005-02-06 10:32:20 Re: pgpool 2.5b2 released
Previous Message David Fetter 2005-02-06 07:00:28 Re: security