From: Tomas Vondra <tomas.vondra@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: checkpoints, proper config
Date: Fri, 11 Dec 2015 02:20:29 +0100
Message-ID: <566A24DD.8020106@2ndquadrant.com> (raw)
In-Reply-To: <20151210224541.GQ2763@alvherre.pgsql>
References: <CAEaSS0af0GpqQYSwePKRQq6RtX-x9NXDm=jOXcbcGAmGHXapFw@mail.gmail.com>
<5669B47B.9010504@commandprompt.com>
<5669FF52.2030303@2ndquadrant.com>
<20151210224541.GQ2763@alvherre.pgsql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tomas.vondra@2ndquadrant.com, alvherre@2ndquadrant.com
Subject: Re: checkpoints, proper config
In-Reply-To: <566A24DD.8020106@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox