Re: Docs: Move parallel_leader_participation GUC description under relevant category - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Docs: Move parallel_leader_participation GUC description under relevant category
Date
Msg-id YH+OPAQRLnRCp5Xb@paquier.xyz
Whole thread Raw
In response to Docs: Move parallel_leader_participation GUC description under relevant category  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Docs: Move parallel_leader_participation GUC description under relevant category  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Tue, Apr 20, 2021 at 09:16:49PM +0530, Bharath Rupireddy wrote:
> It looks like even though the commit e5253fdc4f that added the
> parallel_leader_participation GUC correctly categorized it as
> RESOURCES_ASYNCHRONOUS parameter in the code, but in the docs it is kept
> under irrelevant section i.e. "Query Planning/Other Planner Options". This
> is reported in the bugs list [1], cc-ed the reporter.
>
> Attaching a small patch that moves the GUC description to the right place.
> Thoughts?

I would keep the discussion on the existing thread rather than spawn a
new one on -hackers for exactly the same problem, so I'll reply there
in a minute.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [bug?] Missed parallel safety checks, and wrong parallel safety
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Is it worth to optimize VACUUM/ANALYZE by combining duplicate rel instances into single rel instance?