| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2011-09-02 15:18:31 | Re: PATCH: regular logging of checkpoint progress |
| Previous Message | Tomas Vondra | 2011-09-02 15:13:03 | Re: PATCH: regular logging of checkpoint progress |