Re: Logging parallel worker draught - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Logging parallel worker draught
Date
Msg-id CA+Tgmob91fKoE1QoTqGomBTUZT9JcXwFYrPEmm3arapak-WTsA@mail.gmail.com
Whole thread Raw
In response to Re: Logging parallel worker draught  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Logging parallel worker draught
Re: Logging parallel worker draught
List pgsql-hackers
On Sat, Apr 22, 2023 at 7:06 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> I don't think introducing a GUC for this is a good idea. We can
> directly output this message in the server log either at LOG or DEBUG1
> level.

Why not? It seems like something some people might want to log and
others not. Running the whole server at DEBUG1 to get this information
doesn't seem like a suitable answer.

What I was wondering was whether we would be better off putting this
into the statistics collector, vs. doing it via logging. Both
approaches seem to have pros and cons.

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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Overhauling "Routine Vacuuming" docs, particularly its handling of freezing
Next
From: Aleksander Alekseev
Date:
Subject: Re: base backup vs. concurrent truncation