From: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Too frequent checkpoints ? |
Date: | 2013-02-11 08:46:08 |
Message-ID: | CABOikdNkgdOyiHVpxubppsM4WvxgDnKTr509AW6GrE3NebTqhA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 8, 2013 at 10:25 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
.>
> BTW, the cause of the problem is that the following sequences happens.
>
> 1. archive_timeout switches WAL file because checkpoint WAL record has
> has been written since last switch
Thank you for explaining that. I also noticed that the WAL file switch
happens after archive_timeout seconds irrespective of whether
archive_mode is turned ON or not. This happens because we don't check
if XLogArchivingActive() in CheckArchiveTimeout() function. It looks
wrong to me. But if it's that way for a good reason, shouldn't we at
least document this behaviour ?
Thanks,
Pavan
--
Pavan Deolasee
http://www.linkedin.com/in/pavandeolasee
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2013-02-11 09:01:28 | Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used |
Previous Message | Yeb Havinga | 2013-02-11 08:21:29 | Re: JSON NULLs |