| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Measuring replay lag |
| Date: | 2017-03-23 10:13:58 |
| Message-ID: | CAEepm=2BnmDCob8x7SZ+AyHToO8FobcPoAej3YqedopTqr0Prw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 23, 2017 at 10:50 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> Second thoughts... I'll just make LagTrackerWrite externally
>> available, so a plugin can send anything it wants to the tracker.
>> Which means I'm explicitly removing the "logical replication support"
>> from this patch.
>
> Done.
>
> Here's the patch I'm looking to commit, with some docs and minor code
> changes as discussed.
Giving LagTrackerWrite external linkage seems sensible, assuming there
is a reasonable way for logical replication to decide when to call it.
+ system. Monitoring systems should choose whether the represent this
+ as missing data, zero or continue to display the last known value.
s/whether the/whether to/
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavan Deolasee | 2017-03-23 10:14:22 | Re: Patch: Write Amplification Reduction Method (WARM) |
| Previous Message | Vitaly Burovoy | 2017-03-23 10:09:32 | Re: identity columns |