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

From solai v
Subject Re: Logging parallel worker draught
Date
Msg-id CAF0whucpa40tw_S_qOEyZ0PCpDuWuWxmZjwmR_8ZehDNTBTcyQ@mail.gmail.com
Whole thread
In response to Re: Logging parallel worker draught  (Álvaro Herrera <alvherre@kurilemu.de>)
List 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



pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Fix unqualified catalog references in psql describe queries
Next
From: Andrei Lepikhov
Date:
Subject: Show hashed SAOP decision in EXPLAIN