pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: 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 17:47:36 -0600
Message-ID: <566B6098.6020508@BlueTreble.com> (raw)
In-Reply-To: <566A24DD.8020106@2ndquadrant.com>
References: <CAEaSS0af0GpqQYSwePKRQq6RtX-x9NXDm=jOXcbcGAmGHXapFw@mail.gmail.com>
	<5669B47B.9010504@commandprompt.com>
	<5669FF52.2030303@2ndquadrant.com>
	<20151210224541.GQ2763@alvherre.pgsql>
	<566A24DD.8020106@2ndquadrant.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (11+ messages)

Message-ID: <566B6098.6020508@BlueTreble.com>
Permalink:  ../566B6098.6020508@BlueTreble.com/
Also on:    postgresql.org/message-id/566B6098.6020508@BlueTreble.com

 · 

reply

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: Jim.Nasby@BlueTreble.com, tomas.vondra@2ndquadrant.com, alvherre@2ndquadrant.com
  Subject: Re: checkpoints, proper config
  In-Reply-To: <566B6098.6020508@BlueTreble.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