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

From Dimitri Fontaine
Subject Re: Sync Replication with transaction-controlled durability
Date
Msg-id m239sgibwd.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: Sync Replication with transaction-controlled durability  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Sync Replication with transaction-controlled durability
List pgsql-hackers
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.

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: GIN vs. Partial Indexes
Next
From: Marko Tiikkaja
Date:
Subject: Re: Review: Fix snapshot taking inconsistencies