From: | "Wayne E(dot) Seguin" <wayneeseguin(at)gmail(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: [BDR] vs pgpool-II v3 |
Date: | 2015-08-13 17:37:43 |
Message-ID: | CANf8RLviThDfp61DJiq2iE2Lx2b3S470iNwCV1RZBxTRK5ifxg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The question is specifically about the replication feature mentioned here
http://www.pgpool.net/mediawiki/index.php/Main_Page for the purposes of
failing over minimizing downtime.
On Thu, Aug 13, 2015 at 12:28 PM, Joshua D. Drake <jd(at)commandprompt(dot)com>
wrote:
>
> On 08/13/2015 08:52 AM, Wayne E. Seguin wrote:
>
> "BDR is only one in Beta compare to stable options:
>>
>> https://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling
>> .
>> Not sure why this solution would be chosen. Experience with pgpool is
>> that you only needed to change a port and no SQL changes required on an
>> application side."
>>
>> I appreciate any input as to pros/cons of BDR vs PGPool-II v3 in this
>>
>
> BDR is async multi master. PGPool is largely just a connection pooler with
> load balancing (although it has other features). They play different sports.
>
> 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.
>
--
~Wayne
Wayne E. Seguin
wayneeseguin(at)gmail(dot)com
wayneeseguin on irc.freenode.net
http://twitter.com/wayneeseguin/
https://github.com/wayneeseguin/
From | Date | Subject | |
---|---|---|---|
Next Message | Wayne E. Seguin | 2015-08-13 17:38:03 | Re: [BDR] vs pgpool-II v3 |
Previous Message | Joshua D. Drake | 2015-08-13 16:28:21 | Re: [BDR] vs pgpool-II v3 |