| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Martin Gudmundsson <martingudmundsson(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Bi-Directional replication client awareness |
| Date: | 2014-07-12 10:33:07 |
| Message-ID: | 20140712103307.GA3494@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2014-07-12 18:22:30 +0800, Craig Ringer wrote:
> On 07/12/2014 02:24 PM, Martin Gudmundsson wrote:
> > Any ideas giving BDR an option to be synchronous. I mean in ”close quarters” with low latency it should work ok.
>
> BDR doesn't do synchronous replication _yet_, but it's on the roadmap.
Just to clarify: There's two things that sometimes are referred to as
'synchronous' in the context of multimaster replication.
Just like with HS' builtin synchronous replication it can mean that the
client doesn't get a reply until the COMMIT has safely been replicated
to other systems. That's supported by BDR today.
The more complex thing is support for performing transactions that, when
the COMMIT returns successfully, can't have conflicts. That's *not* yet
supported, but we're thinking of implementing it for individual
transactions.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Gudmundsson | 2014-07-12 10:55:22 | Re: Bi-Directional replication client awareness |
| Previous Message | Craig Ringer | 2014-07-12 10:22:30 | Re: Bi-Directional replication client awareness |