Re: Sync Replication with transaction-controlled durability - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Sync Replication with transaction-controlled durability
Date
Msg-id AANLkTin=fHmtx0LQqf=JEj834=DfHvWC-8Csptcx6c-9@mail.gmail.com
Whole thread Raw
In response to Re: Sync Replication with transaction-controlled durability  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Fri, Oct 8, 2010 at 5:59 PM, Dimitri Fontaine <dimitri@2ndquadrant.fr> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> It seems like it would be more helpful if you were working on
>> implementing a design that had more than one vote.  As far as I can
>> tell, we have rough consensus that for the first commit we should only
>> worry about the case where k = 1; that is, only one ACK is ever
>> required for commit
>
> My understanding by reading the mails here and quick-reading the patch
> (in my MUA, that's how quick the reading was), is that what you want
> here is what's done in the patch, which has been proposed as a WIP, too.

It's not.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Marko Tiikkaja
Date:
Subject: Re: Review: Fix snapshot taking inconsistencies
Next
From: Brendan Jurd
Date:
Subject: Docs for archive_cleanup_command are poor