| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Melanie Plageman <melanieplageman(at)gmail(dot)com> |
| Subject: | Re: Logging parallel worker draught |
| Date: | 2023-04-22 11:06:02 |
| Message-ID: | CAA4eK1+2_te1KYFkSoagdK4Okj0Ob_17KmMGf=qdZ0H4Muzjcw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Apr 21, 2023 at 6:34 PM Benoit Lobréau
<benoit(dot)lobreau(at)dalibo(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2023-04-22 11:42:36 | Re: run pgindent on a regular basis / scripted manner |
| Previous Message | Amit Kapila | 2023-04-22 10:29:38 | Re: The order of queues in row lock is changed (not FIFO) |