| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remove checkpoint_warning |
| Date: | 2016-07-11 18:20:38 |
| Message-ID: | 20160711182038.ip5uinmzpxo4ahy3@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2016-07-11 11:14:29 -0700, Peter Geoghegan wrote:
> On Mon, Jul 11, 2016 at 7:25 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> >> Or in short, this may be a fine change to make, but I don't like your
> >> argument for it.
> >
> > I don't agree that it's sensible to get rid of. Having just
> > log_checkpoints will have the logs filled with checkpoints starting
> > because of XLOG, but there's no indication of that being a bad thing.
>
> I agree. checkpoint_warning exists for the benefit of novice DBAs.
> I've seen those warnings in customer logs on several occasions, at
> least back when I was a consultant.
Note that the situation changed a bit with 9.5, because our defaults
aren't absurdly conservative (checkpoint_segments = 3) anymore.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2016-07-11 18:26:09 | Re: Disable WAL completely - Performance and Persistency research |
| Previous Message | Peter Geoghegan | 2016-07-11 18:14:29 | Re: remove checkpoint_warning |