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

From Amit Kapila
Subject Re: Logging parallel worker draught
Date
Msg-id CAA4eK1+2_te1KYFkSoagdK4Okj0Ob_17KmMGf=qdZ0H4Muzjcw@mail.gmail.com
Whole thread Raw
In response to Logging parallel worker draught  (Benoit Lobréau <benoit.lobreau@dalibo.com>)
Responses Re: Logging parallel worker draught
Re: Logging parallel worker draught
List pgsql-hackers
On Fri, Apr 21, 2023 at 6:34 PM Benoit Lobréau
<benoit.lobreau@dalibo.com> wrote:
>
> Following my previous mail about adding stats on parallelism[1], this
> patch introduces the log_parallel_worker_draught parameter, which
> controls whether a log message is produced when a backend attempts to
> spawn a parallel worker but fails due to insufficient worker slots.
>

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.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: The order of queues in row lock is changed (not FIFO)
Next
From: Andrew Dunstan
Date:
Subject: Re: run pgindent on a regular basis / scripted manner