| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | alvherre(at)2ndquadrant(dot)com |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: standby apply lag on inactive servers |
| Date: | 2020-01-29 04:52:58 |
| Message-ID: | 20200129.135258.244060982658264378.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 28 Jan 2020 11:18:50 -0300, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote in
> On 2020-Jan-27, Alvaro Herrera wrote:
>
> > Actually looking again, getRecordTimestamp is looking pretty strange.
> > It looks much more natural by using nested switch/case blocks, as with
> > this diff. I think the compiler does a better job this way too.
>
> I hadn't noticed I forgot to attach the diff here :-(
Yeay, that patch bases the apply-lag patch:) And contains
XLOG_CHECKPOINT_*. But otherwise looks good to me.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2020-01-29 05:03:14 | Re: standby apply lag on inactive servers |
| Previous Message | Kohei KaiGai | 2020-01-29 04:16:30 | Re: Is custom MemoryContext prohibited? |