From: | William Dunn <dunnwjr(at)gmail(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | Aviel Buskila <aviel33(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Setting up HA postgresql |
Date: | 2015-07-21 20:21:25 |
Message-ID: | CAEva=Vnyi7cOBxWwkKe26iJ_p_NDAY-geCZevHV-brX6UZ73qQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
That's pretty cool! But the intended use of watchdog is so you can have
multiple pgpool-II instances and failover among them (
http://www.pgpool.net/docs/latest/pgpool-en.html#watchdog) rather than
failure of Postgres. In the configuration described in that wiki what
happens when the DBMS goes down but pgpool-II is fine? The watchdog appears
to be monitoring the pgpool-II process, not the postgres/postmaster process.
*Will J. Dunn*
*willjdunn.com <http://willjdunn.com>*
On Tue, Jul 21, 2015 at 3:31 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:
>
> On 07/21/2015 11:04 AM, William Dunn wrote:
>
>> If you dig deeper into pgpool-II you will find that it does not have
>> failover logic. Its intention is to pool connections and distribute
>> query load among replicas, but it cannot differentiate node failure from
>> network partition and cannot promote a standby to master in the case of
>> failure.
>>
>
> If you dig deeper, I think you would find your statement is no longer
> accurate:
>
>
> http://www.pgpool.net/pgpool-web/contrib_docs/watchdog_master_slave_3.3/en.html
>
>
> JD
>
> --
> Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564
> PostgreSQL Centered full stack support, consulting and development.
> Announcing "I'm offended" is basically telling the world you can't
> control your own emotions, so everyone else should do it for you.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2015-07-21 20:27:32 | Re: Setting up HA postgresql |
Previous Message | Adrian Klaver | 2015-07-21 20:16:53 | Re: Cannot reach pg server using -h localhost |