| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, jd(at)commandprompt(dot)com, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Fix checkpoint skip logic on idle systems by tracking LSN progress |
| Date: | 2016-11-19 12:32:32 |
| Message-ID: | aaf461dd-9cd4-d866-c037-1f75b03e8566@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/18/16 12:38 PM, David Steele wrote:
> On 11/14/16 4:29 AM, Michael Paquier wrote:
>> On Mon, Nov 14, 2016 at 6:10 PM, Kyotaro HORIGUCHI
>>> 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?
>
> That's the way I read it as well. It's not clear to me how the
> checkpointer would get restarted under normal circumstances.
>
> I did a kill on the checkpointer and it was ignored. After a kill -9
> the checkpointer process came back but also switched the xlog. Is this
> the expected behavior?
Ah, never mind. I can see this caused a restart and recovery so the
archive timeout was reset and a switch occurred after timeout.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-11-19 12:36:00 | Re: Mail thread references in commits |
| Previous Message | Gilles Darold | 2016-11-19 11:58:47 | Re: Patch to implement pg_current_logfile() function |