Roman Neuhauser wrote:
# [EMAIL PROTECTED] / 2005-02-06 09:34:53 -:
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?
snmp?
Send out a NOTIFY that can be LISTENed for.
--
Richard Huxt
# [EMAIL PROTECTED] / 2005-02-06 09:34:53 -:
> 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?
snmp?
--
If you cc me or remove the list(s) completely I'll most likely ignore
you
Tatsuo Ishii wrote:
Pgpool 2.5b2 supports "master slave mode" which can cope with
master/slave replication softwares such as Slony-I. In this mode
pgpool sends non SELECT queries to master only. SELECTs are load
balanced by pgpool.
First of all, thanks so much Tatsuo for such a great project!
This
> After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] ("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 t
After takin a swig o' Arrakan spice grog, [EMAIL PROTECTED] ("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 nee
> I'm not suggesting that it's the place of pgpool to *force* a failover. I
> am suggesting that one of the criteria that is likely to be useful is the
> inability to connect to the master, and that's something that pgpool,
> apparently, detects. It seems unnecessary to use completely different
>
From: "Joshua D. Drake" <[EMAIL PROTECTED]>
> >Since pgpool has this capability, how about including a hook that allows
a
> >script to be run when pgpool detects a problem with the master? That
would
> >allow action to be taken to investigate further and, if required,
switchover
> >or failover an
pgpool 2.5 has the capabilty to perform periodical health checking to
PostgreSQL.
Since pgpool has this capability, how about including a hook that allows a
script to be run when pgpool detects a problem with the master? That would
allow action to be taken to investigate further and, if requ
On 2/2/2005 11:57 AM, Bruce Momjian wrote:
Tatsuo Ishii wrote:
Pgpool 2.5b2 supports "master slave mode" which can cope with
master/slave replication softwares such as Slony-I. In this mode
pgpool sends non SELECT queries to master only. SELECTs are load
balanced by pgpool.
Other features of 2.5b2
> > Does it attempt any interaction with Slony when it detects a failure of
the
> > master? It would seem a pity to have pgpool watching the pair to detect
> > failure but having to have a separate watcher process to tell Slony to
> > failover.
>
> If pgpool detects PostgreSQL failure, Slony shoul
> > Pgpool 2.5b2 supports "master slave mode" which can cope with
> > master/slave replication softwares such as Slony-I. In this mode
> > pgpool sends non SELECT queries to master only. SELECTs are load
> > balanced by pgpool.
>
> Sounds good!
Thanks. Yesterday I have put offcial release of pgpo
From: "Tatsuo Ishii" <[EMAIL PROTECTED]>
> Pgpool 2.5b2 supports "master slave mode" which can cope with
> master/slave replication softwares such as Slony-I. In this mode
> pgpool sends non SELECT queries to master only. SELECTs are load
> balanced by pgpool.
Sounds good!
Does it attempt any i
Tatsuo Ishii wrote:
> Pgpool 2.5b2 supports "master slave mode" which can cope with
> master/slave replication softwares such as Slony-I. In this mode
> pgpool sends non SELECT queries to master only. SELECTs are load
> balanced by pgpool.
>
> Other features of 2.5b2 include:
> - ability to add ti
13 matches
Mail list logo
