| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Markus Wanner <markus(at)bluegap(dot)ch> |
| Cc: | Aidan Van Dyk <aidan(at)highrise(dot)ca>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, MARK CALLAGHAN <mdcallag(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| Date: | 2011-03-23 15:24:30 |
| Message-ID: | AANLkTiki6M8=CmQc-5aPF0HTN9CRY2vuTLuPJusXJjK5@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Wed, Mar 23, 2011 at 8:16 AM, Markus Wanner <markus(at)bluegap(dot)ch> wrote:
> On 03/23/2011 12:52 PM, Robert Haas wrote:
>> Yes. What this won't do is let you build a big load-balancing network
>> (at least not without great caution about what you assume).
>
> This sounds too strong to me. Session-aware load balancing is pretty
> common these days. It's the default mode of PgBouncer, for example.
> Not much caution required there, IMO. Or what pitfalls did you have in
> mind?
Well, just the one we were talking about: a COMMIT on one node doesn't
guarantee that the transactions is visible on the other node, just
that it will become visible there eventually, even if a crash happens.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-23 15:53:25 | pgsql: Remove synchronous_replication/max_wal_senders cross-check. |
| Previous Message | Robert Haas | 2011-03-23 15:19:25 | Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2011-03-23 15:35:31 | making write location work (was: Efficient transaction-controlled synchronous replication) |
| Previous Message | Robert Haas | 2011-03-23 15:19:25 | Re: Re: [COMMITTERS] pgsql: Basic Recovery Control functions for use in Hot Standby. Pause, |