| From: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: checkpoints, proper config |
| Date: | 2015-12-11 01:20:29 |
| Message-ID: | 566A24DD.8020106@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 12/10/2015 11:45 PM, Alvaro Herrera wrote:
> Tomas Vondra wrote:
>
>> Also, I don't think it makes much sense to set
>>
>> (checkpoint_warning > checkpoint_timeout)
>>
>> as it kinda defeats the whole purpose of the warning.
>
> I agree, but actually, what is the sense of checkpoint_warning? I think
> it was useful back when we didn't have log_checkpoints, but now that we
> have detailed checkpoint logging I think it's pretty much useless noise.
>
Not entirely. The WARNING only triggers when you get below the 30s (or
whatever value is set in the config) and explicitly warns you about
doing checkpoints too often. log_checkpoints=on logs all checkpoints and
you have to do further analysis on the data (and it's just LOG).
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ankur_adwyze | 2015-12-11 04:38:22 | Advise needed for a join query with a where conditional |
| Previous Message | Alvaro Herrera | 2015-12-10 22:45:41 | Re: checkpoints, proper config |