Re: [HACKERS] Small bug in replication lag tracking - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] Small bug in replication lag tracking
Date
Msg-id CAEepm=1uQ3VSNO2LdZJxeCjS5Sez_2M=SX0DDr3wAogX2oTCxQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Small bug in replication lag tracking  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Sat, Jun 24, 2017 at 6:07 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On 23 June 2017 at 08:18, Simon Riggs <simon@2ndquadrant.com> wrote:
>> On 23 June 2017 at 06:45, Thomas Munro <thomas.munro@enterprisedb.com> wrote:
>>
>>> I discovered a thinko in the new replication lag interpolation code
>>> that can cause a strange number to be reported occasionally.
>>
>> Thanks, will review.
>
> I've pushed this, but I think we should leave the code alone after
> this and wait for user feedback.

Thanks!  Yeah, I haven't heard any feedback about this, which I've
been interpreting as good news...  but if anyone's looking for
something to beta test, reports would be most welcome.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Can ICU be used for a database's default sort order?
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Logical replication: stuck spinlock atReplicationSlotRelease