Re: [HACKERS] Measuring replay lag - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] Measuring replay lag
Date
Msg-id CAEepm=1uDGfwWWrah8qEj3j0ZAZo8kT0Rg0t_B8b0hy9F2JQKA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Measuring replay lag  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Measuring replay lag  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Wed, Mar 22, 2017 at 11:57 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>>> I accept your proposal for how we handle these, on condition that you
>>> write up some docs that explain the subtle difference between the two,
>>> so we can just show people the URL. That needs to explain clearly the
>>> difference in an impartial way between "what is the most recent lag
>>> measurement" and "how long until we are caught up" as possible
>>> intrepretations of these values. Thanks.
>>
>>
>> This thread has been idle for six days.  Please respond and/or post a new
>> patch by 2017-03-24 00:00 AoE (UTC-12) or this submission will be marked
>> "Returned with Feedback".
>
> Thomas, Are you working on another version even? You've not replied to
> me or David, so its difficult to know what next.
>
> Not sure whether this a 6 day lag, or we should show NULL because we
> are up to date.

Hah.  Apologies for the delay -- I will post a patch with
documentation as requested within 24 hours.

-- 
Thomas Munro
http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Measuring replay lag
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Measuring replay lag