| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. |
| Date: | 2011-03-06 23:28:45 |
| Message-ID: | 1299454125.1696.6138.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Sun, 2011-03-06 at 18:09 -0500, Andrew Dunstan wrote:
>
> On 03/06/2011 05:51 PM, Simon Riggs wrote:
> > Efficient transaction-controlled synchronous replication.
> >
>
> I'm glad this is in, but I thought we agreed NOT to call it "synchronous
> replication".
The discussion on the thread was that its not sync rep unless we have
the strictest guarantees. We have the strictest guarantees, so it
qualifies as sync rep.
Relaxations are possible and, to some people, desirable.
Perhaps there is a more marketable term, and if so, we can rebrand. It
wouldn't be the first time things got renamed in beta.
--
Simon Riggs http://www.2ndQuadrant.com/books/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2011-03-06 23:36:30 | Re: pgsql: Efficient transaction-controlled synchronous replication. |
| Previous Message | Tom Lane | 2011-03-06 23:28:13 | Re: pgsql: Efficient transaction-controlled synchronous replication. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2011-03-06 23:36:30 | Re: pgsql: Efficient transaction-controlled synchronous replication. |
| Previous Message | Tom Lane | 2011-03-06 23:28:13 | Re: pgsql: Efficient transaction-controlled synchronous replication. |