| 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-03 23:27:11 |
| Message-ID: | CAEepm=2V2_wCvZ-6K=rsQi3YTqPG4ceCT4XJwgj2PRA6iLGRKA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 4, 2017 at 12:22 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> The patch streams (time-right-now, end-of-wal) to the standby in every
> outgoing message, and then sees how long it takes for those timestamps
> to be fed back to it.
Correction: we already stream (time-right-now, end-of-wal) to the
standby in every outgoing message. The patch introduces a new use of
that information by feeding them back upstream.
--
Thomas Munro
http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-01-03 23:40:59 | Re: Measuring replay lag |
| Previous Message | Thomas Munro | 2017-01-03 23:22:52 | Re: Measuring replay lag |