Re: Measuring replay lag
| От | Thomas Munro |
|---|---|
| Тема | Re: Measuring replay lag |
| Дата | |
| Msg-id | CAEepm=0vv_YetnKEheCYULQU6RT3yZonVmeioCr_mad7a=BeYQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Measuring replay lag (Masahiko Sawada <sawada.mshk@gmail.com>) |
| Ответы |
Re: [HACKERS] Measuring replay lag
|
| Список | pgsql-hackers |
On Tue, Nov 8, 2016 at 2:35 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote: > replay_lag_sample_interval is 1s by default but I got 1000s by SHOW command. > postgres(1:36789)=# show replay_lag_sample_interval ; > replay_lag_sample_interval > ---------------------------- > 1000s > (1 row) Oops, fixed. >> 1. The lag is measured in time, not LSN difference. >> 2. The lag time is computed using two observations of a single >> server's clock, so there is no clock skew. >> 3. The lag is updated even between commits (during large data loads etc). > > I agree with this approach. Thanks for the feedback. > I think that you need to change sendFeedback() in pg_recvlogical.c and > receivexlog.c as well. Right, fixed. Thanks very much for testing! New version attached. I will add this to the next CF. -- Thomas Munro http://www.enterprisedb.com
Вложения
В списке pgsql-hackers по дате отправления: