Re: Quorum commit for multiple synchronous replication.
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Fujii Masao <masao.fujii@gmail.com>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>,
Sawada Masahiko <sawada.mshk@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Petr Jelinek <petr@2ndquadrant.com>, Vik Fearing <vik@2ndquadrant.fr>, Simon Riggs <simon@2ndquadrant.com>, Josh Berkus <josh@agliodbs.com>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2016-12-15T05:13:30Z
Lists: pgsql-hackers
On Thu, Dec 15, 2016 at 7:53 AM, Michael Paquier <michael.paquier@gmail.com> wrote: > On Thu, Dec 15, 2016 at 11:04 AM, Fujii Masao <masao.fujii@gmail.com> wrote: >> On Thu, Dec 15, 2016 at 6:47 AM, Michael Paquier >> <michael.paquier@gmail.com> wrote: > >> So I'd like to propose to keep the backward compatibility fully for s_s_names >> (i.e., both "standby_list" and "N (standby_list)" mean the priority method) >> at the first commit, then continue discussing this and change it if we reach >> the consensus until PostgreSQL 10 is actually released. Thought? > > +1 on that. > +1. That is the safest option to proceed. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Set the priorities of all quorum synchronous standbys to 1.
- 346199dcab4c 10.0 landed
-
Improve documentation and comment for quorum-based sync replication.
- a790ed9f69ef 10.0 landed