Horton
Menu

Re: Quorum commit for multiple synchronous replication.

Petr Jelinek <petr@2ndquadrant.com>

View thread
From: Petr Jelinek <petr@2ndquadrant.com>
To: Vik Fearing <vik@2ndquadrant.fr>, Michael Paquier <michael.paquier@gmail.com>, Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Josh Berkus <josh@agliodbs.com>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-09-09T08:43:08Z
Lists: pgsql-hackers 

On 09/09/16 08:23, Vik Fearing wrote:
> On 09/09/2016 03:28 AM, Michael Paquier wrote:
>> On Thu, Sep 8, 2016 at 6:26 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>>> "k (n1, n2, n3)" == "first k (n1, n2, n3)" doesn't break backward
>>> compatibility but most users would think "k(n1, n2, n3)" as quorum
>>> after introduced quorum.
>>> I wish we can change the s_s_names syntax of 9.6 to "first k(n1, n2,
>>> n3)" style before 9.6 releasing if we got consensus.
>>
>> Considering breaking backward-compatibility in the next release does
>> not sound like a good idea to me for a new feature that is going to be
>> GA soon.
>
> Indeed.  I'll vote for pulling a fast one on 9.6 for this.
>

+1

-- 
   Petr Jelinek                  http://www.2ndQuadrant.com/
   PostgreSQL Development, 24x7 Support, Training & Services

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Set the priorities of all quorum synchronous standbys to 1.

  2. Improve documentation and comment for quorum-based sync replication.