Re: Logging parallel worker draught

From: solai v <solai(dot)cdac(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Benoit Lobréau <benoit(dot)lobreau(at)dalibo(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Logging parallel worker draught
Date: 2026-06-09 09:35:03
Message-ID: CAF0whucpa40tw_S_qOEyZ0PCpDuWuWxmZjwmR_8ZehDNTBTcyQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

> Yeah, I think some hunks disappeared from 0001, in the .h files as well
> as the .sgml docs. Probably just a borked merge. I re-merged them,
> here's the patchset again. I did not review this.
I retested the updated v11 patch series.
The patches applied cleanly and postgresql built successfully.
I verified that the new GUC log_parallel_workers is available .Using
SET log_parallel_workers = ' shortage ' ;
I reproduced a parallel worker shortage scenario where the query
planned 2 workers but launched only 1 worker.
The server log correctly reported LOG: launched 1 parallel workers
(planned:2)
and EXPLAIN ANALYZE showed
Workers planned: 2
workers Launched: 1
So the updated patch appears to work intended in this test case.

Regards
solai

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2026-06-09 09:51:07 Show hashed SAOP decision in EXPLAIN
Previous Message Bertrand Drouvot 2026-06-09 09:08:50 Re: Fix unqualified catalog references in psql describe queries