From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: checkpoints, proper config |
Date: | 2015-12-11 23:47:36 |
Message-ID: | 566B6098.6020508@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 12/10/15 7:20 PM, Tomas Vondra wrote:
>> 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).
Agree, though I also find it pretty useless to set it significantly less
than checkpoint_timeout in almost all cases. If you want ~5 minutes
between checkpoints checkpoint_timeout=30 seconds is way too low to be
useful. We should really change the default.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2015-12-11 23:50:24 | Re: Advise needed for a join query with a where conditional |
Previous Message | Jim Nasby | 2015-12-11 23:45:40 | Re: checkpoints, proper config |