Re: [HACKERS] Replication status in logical replication - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: [HACKERS] Replication status in logical replication
Date
Msg-id CAHGQGwE2HgoZ=mjgMcvg9SO2zPDDr9d3tohcQwJvSt4Pri9MDw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Replication status in logical replication  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Replication status in logical replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Wed, Jan 17, 2018 at 2:16 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 16 January 2018 at 06:21, Michael Paquier <michael.paquier@gmail.com> wrote:
>> On Tue, Jan 16, 2018 at 10:40:43AM +0900, Masahiko Sawada wrote:
>>> On Sun, Jan 14, 2018 at 12:43 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>>> On 9 January 2018 at 04:36, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>>>> We're not talking about standbys, so the message is incorrect.
>>>
>>> Ah, I understood. How about "\"%s\"  has now caught up with upstream
>>> server"?
>>
>> +1.
>
> upstream is what I would have suggested, so +1 here also.
>
> Will commit.

ping?

Regards,

-- 
Fujii Masao


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Enhance pg_stat_wal_receiver view to display connected host
Next
From: Thomas Munro
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS