From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Log notice that checkpoint is to be written on shutdown |
Date: | 2014-10-09 13:44:09 |
Message-ID: | 24137.1412862249@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andres Freund (andres(at)2ndquadrant(dot)com) wrote:
>> How about flipping the default for log_checkpoints instead? There really
>> isn't a good reason for having it disabled by default.
> Yeah, I agree with this- it's extremely useful information and it's
> really not that verbose in general..
-1. Every time we've turned on default logging of routine events,
there's been pushback and it was eventually turned off again as log spam.
I guarantee you that logging checkpoints will be seen as log spam, except
by people who are actually having trouble with that behavior, which is
a small minority.
I'm not really convinced that there's a problem here that needs fixing
at all, but certainly putting log_checkpoints on by default is not an
acceptable fix.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | MauMau | 2014-10-09 13:47:48 | [9.4 bug] The database server hangs with write-heavy workload on Windows |
Previous Message | Stephen Frost | 2014-10-09 13:23:22 | Re: Log notice that checkpoint is to be written on shutdown |