Re: Measuring replay lag

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: David Steele <david(at)pgmasters(dot)net>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, 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-22 11:29:39
Message-ID: CA+TgmoYzUXtMbiSgS2JLiJU33ebkAn0qY6s3Svoths+6i2TG+w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 22, 2017 at 6:57 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Not sure whether this a 6 day lag, or we should show NULL because we
> are up to date.

OK, that made me laugh.

Thanks for putting in the effort on this patch, BTW.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-03-22 11:32:25 Re: Monitoring roles patch
Previous Message Simon Riggs 2017-03-22 11:27:11 Re: Patch to improve performance of replay of AccessExclusiveLock