| From: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Wayne E(dot) Seguin" <wayneeseguin(at)gmail(dot)com>, "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 21:09:55 |
| Message-ID: | 55CD07A3.3030209@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
El 13/08/15 a las 14:37, Wayne E. Seguin escribió:
> 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.
They aim a completely different problems.
The thing Joshua mentioned about BDR being *async* means that data will
be *eventually* consistent. This tackles the problem with nodes which
are distant (one node in London, another in NY, one in Tokio, ...)
PgPools replication_mode is for nodes on a local network. It would never
scale like BDR with geographically distant nodes.
Conclusion, they don't solve the same problem, so it's hard to compare.
Cheers,
--
Martín Marqués http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | twoflower | 2015-08-13 21:14:44 | Re: SELECT blocks UPDATE |
| Previous Message | Adrian Klaver | 2015-08-13 21:02:15 | Re: Extension to rewrite queries before execution |