From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Ashwin Agrawal <aagrawal(at)pivotal(dot)io>, 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> |
Subject: | Re: [HACKERS] Commits don't block for synchronous replication |
Date: | 2017-11-22 17:57:22 |
Message-ID: | CANP8+jJQi9tYKorNAbq7exYpT8duxy1-k6Q6ZYgvKC6_14XDAA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 15 November 2017 at 10:07, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
> 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".
The patch has been applied - look at the code. Marking back to committed.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-11-22 18:01:22 | Re: [HACKERS] SQL procedures |
Previous Message | Tom Lane | 2017-11-22 17:34:36 | Re: [PATCH] using arc4random for strong randomness matters. |