Re: Measuring replay lag

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(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-01-04 07:58:03
Message-ID: CANP8+j+3U-bHHZsS2gp1zFtGA7rzf4=ieErbsE2LYECfZx5F7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3 January 2017 at 23:22, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> wrote:

>> I don't see why that would be unacceptable. If we do it for
>> remote_apply, why not also do it for other modes? Whatever the
>> reasoning was for remote_apply should work for other modes. I should
>> add it was originally designed to be that way by me, so must have been
>> changed later.
>
> You can achieve that with this patch by setting
> replication_lag_sample_interval to 0.

I wonder why you ignore my mention of the bug in the correct mechanism?

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-01-04 08:02:47 Re: Declarative partitioning - another take
Previous Message Andres Freund 2017-01-04 07:32:28 Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal