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

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-24 14:38:39
Message-ID: CANP8+jLKD5u-R4aR78_-DKV2Wd1Q8wFNE0nh19wxVkyAX8uXLw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Erikjan Rijkers 2017-11-24 15:08:08 Re: Add RANGE with values and exclusions clauses to the Window Functions
Previous Message Oliver Ford 2017-11-24 14:11:17 Add RANGE with values and exclusions clauses to the Window Functions