Re: O(n) tasks cause lengthy startups and checkpoints - Mailing list pgsql-hackers

From Andres Freund
Subject Re: O(n) tasks cause lengthy startups and checkpoints
Date
Msg-id 20221128183129.ip3g5vrcbjrngpp2@awork3.anarazel.de
Whole thread Raw
In response to Re: O(n) tasks cause lengthy startups and checkpoints  (Simon Riggs <simon.riggs@enterprisedb.com>)
Responses Re: O(n) tasks cause lengthy startups and checkpoints
List pgsql-hackers
On 2022-11-28 13:08:57 +0000, Simon Riggs wrote:
> On Sun, 27 Nov 2022 at 23:34, Nathan Bossart <nathandbossart@gmail.com> wrote:
> > > Rather than explicitly use DEBUG1 everywhere I would have an
> > > #define CUSTODIAN_LOG_LEVEL     LOG
> > > so we can run with it in LOG mode and then set it to DEBUG1 with a one
> > > line change in a later phase of Beta
> >
> > I can create a separate patch for this, but I don't think I've ever seen
> > this sort of thing before.
> 
> Much of recovery is coded that way, for the same reason.

I think that's not a good thing to copy without a lot more justification than
"some old code also does it that way". It's sometimes justified, but also
makes code harder to read (one doesn't know what it does without looking up
the #define, line length).



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: TAP output format in pg_regress
Next
From: Robert Haas
Date:
Subject: Re: O(n) tasks cause lengthy startups and checkpoints