Re: [HACKERS] Commits don't block for synchronous replication

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Ashwin Agrawal <aagrawal(at)pivotal(dot)io>
Cc: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Xin Zhang <xzhang(at)pivotal(dot)io>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Asim Praveen <apraveen(at)pivotal(dot)io>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Subject: Re: [HACKERS] Commits don't block for synchronous replication
Date: 2017-11-14 23:07:54
Message-ID: CAB7nPqQtn4Z_jQr4Tvxkvjag2pYFQrWJBL3_W2SM3oycG_qO5w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Nov 15, 2017 at 7:28 AM, Ashwin Agrawal <aagrawal(at)pivotal(dot)io> wrote:
>
> https://commitfest.postgresql.org/15/1297/
>
> Am I missing something or not looking at right place, this is marked as
> committed but don't see the change in latest master ?

Good thing you double-checked. This has been marked as committed
eleven day ago by Simon (added in CC), but no commit has happened. I
am switching back the status as "ready for committer".
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2017-11-14 23:09:50 Separate leader buffer info and worker wait info in EXPLAIN output?
Previous Message Peter Eisentraut 2017-11-14 22:47:25 Re: [HACKERS] SQL procedures