Re: Measuring replay lag

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 01:02:45
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-hackers

On Thu, Mar 23, 2017 at 12:12 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 22 March 2017 at 11:03, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> wrote:
>> Hah. Apologies for the delay -- I will post a patch with
>> documentation as requested within 24 hours.
> Thanks very much. I'll reserve time to commit it tomorrow, all else being good.

Thanks! Please find attached v7, which includes a note we can point
at when someone asks why it doesn't show 00:00:00, as requested.

Thomas Munro

Attachment Content-Type Size
replication-lag-v7.patch application/octet-stream 22.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-03-23 01:05:16 Re: Logical decoding on standby
Previous Message Amit Langote 2017-03-23 01:02:39 Re: Partitioned tables and relfilenode