Re: [HACKERS] Commits don't block for synchronous replication - Mailing list pgsql-hackers

From Ashwin Agrawal
Subject Re: [HACKERS] Commits don't block for synchronous replication
Date
Msg-id CALfoeit4+Uw8c0FxnUFc9SSr_cLV7d1ApX_DuDLuMR64+e8dkQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Commits don't block for synchronous replication  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Commits don't block for synchronous replication  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers

On Wed, Nov 22, 2017 at 9:57 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
On 15 November 2017 at 10:07, Michael Paquier <michael.paquier@gmail.com> wrote:
> On Wed, Nov 15, 2017 at 7:28 AM, Ashwin Agrawal <aagrawal@pivotal.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".

The patch has been applied - look at the code. Marking back to committed.

I have no idea which magical place this is being committed, atleast don't see on master unless checking something wrong, please can you post the commit here ?

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] SQL procedures
Next
From: Corey Huinker
Date:
Subject: Re: [HACKERS] SQL procedures