Re: should we enable log_checkpoints out of the box?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Jan Wieck <jan(at)wi3ck(dot)info>, Bruce Momjian <bruce(at)momjian(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: should we enable log_checkpoints out of the box?
Date: 2021-11-05 15:04:40
Message-ID: CA+TgmoatvoWUBD9PVXjSJ6s40PN1V8_V+_yWvbr8Jvmt6AHkfQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 5, 2021 at 10:50 AM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> I think what we need is an orthogonal classification. "This FATAL here
> is routine; that ERROR there denotes a severe problem in the underlying
> OS". Additional levels won't help with that. Maybe adding the concept
> of "severity" or "criticality" to some messages would be useful to
> decide what to keep and what to discard.

It would be really nice if we could do that in some kind of sensible
way. I think it's hard to get agreement though because different
people are going to care about different things. In fact, that
consideration weighs heavily against trying to adopt any sort of
project policy at all: somebody's bound to think it sucks. Even people
who mostly like it will demand the ability to customize it. On the
other hand, I also can't endorse the current policy of generating a
paper trail long enough to reach Alpha Centauri, so maybe we ought to
try harder to reach some sort of consensus.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-11-05 15:08:42 Re: [PATCH] rename column if exists
Previous Message David G. Johnston 2021-11-05 15:00:49 Re: [PATCH] rename column if exists