| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(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-01 02:50:29 |
| Message-ID: | CAB7nPqQvKfs5x35NPvvot_VBcLwjv2N=EKLozZ0jB30wd0YNtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-12-01 02:51:20 | Re: [HACKERS] Assertion failure when the non-exclusive pg_stop_backup aborted. |
| Previous Message | Michael Paquier | 2017-12-01 02:48:48 | Re: Use of uninitialized variables in ExecFindPartition() for parent partition without leaves (HEAD only) |