On Tue, Apr 20, 2021 at 12:54 PM PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 16972
> Logged by: yanliang lei
> Email address: leiyanliang@highgo.com
> PostgreSQL version: 13.1
> Operating system: CentOS7.6
> Description:
>
> In the following SQL statement, parallel_leader_participation's category is
> ' Resource Usage / Asynchronous Behavior'
>
> postgres=# select * from pg_settings where
> name='parallel_leader_participation';
> -[ RECORD 1
> ]---+--------------------------------------------------------------
> name | parallel_leader_participation
> setting | on
> unit |
> category | Resource Usage / Asynchronous Behavior
> short_desc | Controls whether Gather and Gather Merge also run
> subplans.
> extra_desc | Should gather nodes also run subplans, or just gather
> tuples?
> context | user
> vartype | bool
> source | default
> min_val |
> max_val |
> enumvals |
> boot_val | on
> reset_val | on
> sourcefile |
> sourceline |
> pending_restart | f
>
> postgres=#
>
> but in the documents
> (https://www.postgresql.org/docs/13/runtime-config-query.html#RUNTIME-CONFIG-QUERY-OTHER)
> parallel_leader_participation's category is 'Query Tuning / Other Planner
> Options'
> and in the category "Asynchronous
>
Behavior"(https://www.postgresql.org/docs/13/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-ASYNC-BEHAVIOR),there
> is no parallel_leader_participation parameter.
>
> so, what is parallel_leader_participation's category ?
Thanks for reporting.
I think it comes under the category "Resource Usage / Asynchronous
Behavior", so what pg_settings showing is correct. ISTM that we need
to correct the docs, attached a patch for that.
With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com
