| 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-12-29 14:45:09 |
| Message-ID: | CANP8+jL5q1yMwvh-ZukMP4nagBvfAUZVZ_faRv4oJzLX=G-0vQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1 December 2017 at 02:50, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
> On Fri, Nov 24, 2017 at 11:38 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On 23 November 2017 at 11:11, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote:
>>
>>> This is older than the bug report of this thread. All those
>>> indications point out that the patch has *not* been committed. So it
>>> seems to me that you perhaps committed it to your local repository,
>>> but forgot to push it to the remote. I am switching back the patch
>>> status to what looks correct to me "Ready for committer". Thanks.
>>
>> Yes, that looks like it's my mistake. Thanks for rechecking.
>>
>> Will commit and backpatch when I get home.
>
> Ping. Simon, are you planning to look at this patch, and potentially commit it?
>
> I am moving this item to next CF for now.
Applied, thanks.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-12-29 15:48:41 | Re: Basebackups reported as idle |
| Previous Message | Tatsuo Ishii | 2017-12-29 14:39:39 | Re: [HACKERS] [PATCH] Lockable views |