Skip site navigation (1) Skip section navigation (2)

Re: PATCH: regular logging of checkpoint progress

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tomas Vondra" <tv(at)fuzzy(dot)cz>,"Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: "Magnus Hagander" <magnus(at)hagander(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PATCH: regular logging of checkpoint progress
Date: 2011-09-02 15:14:36
Message-ID: 4E60AC8C0200002500040B2D@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
."Tomas Vondra" <tv(at)fuzzy(dot)cz> wrote:
> On 2 Zá*í 2011, 15:44, Peter Eisentraut wrote:
 
>> Changing the log level is not the appropriate solution.  Make it
>> a configuration parameter.
> 
> Why is it inappropriate solution? There's a log_checkpoints GUC
> that drives it and you can either get basic info (summary of the
> checkpoint) or detailed log (with a lower log level).
 
Maybe?:
 
log_checkpoints = 'verbose'
 
It seems to me that one of the most likely uses of this is for
investigating performance issues in production.  Like with
log_statement, you might want to turn it on briefly and examine
results.
 
-Kevin


In response to

pgsql-hackers by date

Next:From: Jaime CasanovaDate: 2011-09-02 15:18:31
Subject: Re: PATCH: regular logging of checkpoint progress
Previous:From: Tomas VondraDate: 2011-09-02 15:13:03
Subject: Re: PATCH: regular logging of checkpoint progress

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group