Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M53727=pgsql-performance-ar@postgresql.org>)
 id 1a79zs-0004N0-Gi
 for pgsql-performance@arkaria.postgresql.org; Thu, 10 Dec 2015 22:47:36 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.84) (envelope-from
 <pgsql-performance-owner+M53727=pgsql-performance-ar@postgresql.org>)
 id 1a79zr-00048Y-W0
 for pgsql-performance@arkaria.postgresql.org; Thu, 10 Dec 2015 22:47:36 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
 (Exim 4.84) (envelope-from <alvherre@alvh.no-ip.org>)
 id 1a79yD-0000sx-Qz
 for pgsql-performance@postgresql.org; Thu, 10 Dec 2015 22:45:53 +0000
Received: from out.smtp-auth.no-ip.com ([8.23.224.60])
 by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
 (Exim 4.84) (envelope-from <alvherre@alvh.no-ip.org>)
 id 1a79y6-0004DF-4K
 for pgsql-performance@postgresql.org; Thu, 10 Dec 2015 22:45:53 +0000
X-No-IP: alvh.no-ip.org@noip-smtp
X-Report-Spam-To: abuse@no-ip.com
Received: from alvin.alvh.no-ip.org (unknown [200.104.53.52])
 (Authenticated sender: alvh.no-ip.org@noip-smtp)
 by smtp-auth.no-ip.com (Postfix) with ESMTPA id D9DC2401202;
 Thu, 10 Dec 2015 14:45:42 -0800 (PST)
Received: by alvin.alvh.no-ip.org (Postfix, from userid 1000)
 id 219841EE9; Thu, 10 Dec 2015 19:45:41 -0300 (CLT)
Date: Thu, 10 Dec 2015 19:45:41 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: checkpoints, proper config
Message-ID: <20151210224541.GQ2763@alvherre.pgsql>
References: 
 <CAEaSS0af0GpqQYSwePKRQq6RtX-x9NXDm=jOXcbcGAmGHXapFw@mail.gmail.com>
 <5669B47B.9010504@commandprompt.com>
 <5669FF52.2030303@2ndquadrant.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5669FF52.2030303@2ndquadrant.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Pg-Spam-Score: -2.6 (--)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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.

-- 
Álvaro Herrera                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