Re: Fix checkpoint skip logic on idle systems by tracking LSN progress - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Fix checkpoint skip logic on idle systems by tracking LSN progress
Date
Msg-id CAB7nPqQhYhbtevxUrOBK0wFo6pVi6LcqwpAX+CnKXtzLRfxMVw@mail.gmail.com
Whole thread Raw
In response to Re: Fix checkpoint skip logic on idle systems by tracking LSN progress  (Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>)
Responses Re: Fix checkpoint skip logic on idle systems by tracking LSN progress  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On Mon, Nov 14, 2016 at 6:10 PM, Kyotaro HORIGUCHI
<horiguchi.kyotaro@lab.ntt.co.jp> wrote:
> It applies the master and compiled cleanly and no error by
> regtest.  (I didn't confirmed that the problem is still fixed but
> seemingly no problem)

Thanks for double-checking.

> If I'm not missing something, at the worst we have a checkpoint
> after a checkpointer restart that should have been supressed. Is
> it worth picking it up for the complexity?

I think so, that's not that much code if you think about it as there
is already a routine to get the timestamp of the lastly switched
segment that gets used by checkpointer.c.
-- 
Michael



pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [PATCH] Allow TAP tests to be run individually
Next
From: Ashutosh Bapat
Date:
Subject: Re: [RFC] Should we fix postmaster to avoid slow shutdown?