| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Wayne E(dot) Seguin" <wayneeseguin(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [BDR] vs pgpool-II v3 |
| Date: | 2015-08-17 01:35:48 |
| Message-ID: | CAMsr+YHsgrg=nDW5U4wC44Hnc1ns-wXJzU3HgQhsp_jkQqrG7g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 13 August 2015 at 23:52, Wayne E. Seguin <wayneeseguin(at)gmail(dot)com> wrote:
> The context of this is using BDR to implement a HA solution where we have
> one node getting all connections at a time, if the node fails we move all
> connections to another node. (eg. only one node gets all connections at any
> given time).
This sounds like a job better suited to a normal active/standby
configuration with regular built-in streaming replication. Use a tool
like repmgr to manage failover and a proxy like pgbouncer to redirect
traffic.
There's no reason to use async multi-master replication when simple
single-master replication will do just as well.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jony Cohen | 2015-08-17 05:49:36 | Re: repmgr won't update witness after failover |
| Previous Message | Deepak Balasubramanyam | 2015-08-16 17:31:34 | Re: Postgresql jsonb |