Horton
Menu

Re: Quorum commit for multiple synchronous replication.

Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>

View thread
From: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
To: sawada.mshk@gmail.com
Cc: masao.fujii@gmail.com, noah@leadboat.com, michael.paquier@gmail.com, amit.kapila16@gmail.com, robertmhaas@gmail.com, petr@2ndquadrant.com, vik@2ndquadrant.fr, simon@2ndquadrant.com, josh@agliodbs.com, pgsql-hackers@postgresql.org
Date: 2017-04-25T08:41:15Z
Lists: pgsql-hackers 
At Tue, 25 Apr 2017 09:22:59 +0900, Masahiko Sawada <sawada.mshk@gmail.com> wrote in <CAD21AoAG88zYUwhV9L5muNX-qPSB+AgzerFDD0JDDVoM25gKKw@mail.gmail.com>
> >> Please observe the policy on open item ownership[1] and send a status update
> >> within three calendar days of this message.  Include a date for your
> >> subsequent status update.
> >
> > Okay, so our consensus is to always set the priorities of sync standbys
> > to 1 in quorum-based syncrep case. Attached patch does this change.
> > Barrying any objection, I will commit this.
> 
> +1

Ok, +1 from me.

regards,

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

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.