Re: Quorum commit for multiple synchronous replication.
Josh Berkus <josh@berkus.org>
From: Josh Berkus <josh@berkus.org>
To: Masahiko Sawada <sawada.mshk@gmail.com>,
Robert Haas <robertmhaas@gmail.com>
Cc: Michael Paquier <michael.paquier@gmail.com>,
Noah Misch <noah@leadboat.com>, Petr Jelinek <petr.jelinek@2ndquadrant.com>,
Fujii Masao <masao.fujii@gmail.com>,
Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>,
Amit Kapila <amit.kapila16@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: 2017-08-23T18:11:29Z
Lists: pgsql-hackers
On 08/22/2017 11:04 PM, Masahiko Sawada wrote: > WARNING: what you did is ok, but you might have wanted to do something else > > First of all, whether or not that can properly be called a warning is > highly debatable. Also, if you do that sort of thing to your spouse > and/or children, they call it "nagging". I don't think users will > like it any more than family members do. Realistically, we'll support the backwards-compatible syntax for 3-5 years. Which is fine. I suggest that we just gradually deprecate the old syntax from the docs, and then around Postgres 16 eliminate it. I posit that that's better than changing the meaning of the old syntax out from under people. -- Josh Berkus Containers & Databases Oh My!
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