Re: Measuring replay lag

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: 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 11:10:59
Message-ID: CAEepm=10kGC15gVz0xd=EQF3EGf6+ymD57byi2DDTv4GvAEj6A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jan 5, 2017 at 12:03 AM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> So perhaps I should get rid of that replication_lag_sample_interval
> GUC and send back apply timestamps frequently, as you were saying. It
> would add up to a third more replies.

Oops, of course I meant to say up to 50% more replies...

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Sharma 2017-01-04 11:13:38 Re: Microvacuum support for Hash Index
Previous Message Artur Zakirov 2017-01-04 11:06:44 Re: [PATCH] Generic type subscription