From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Cc: | leiyanliang(at)highgo(dot)com |
Subject: | BUG #16972: parameter parallel_leader_participation's category problem |
Date: | 2021-04-20 06:45:50 |
Message-ID: | 16972-42d4b0c15aa1d5f5@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 16972
Logged by: yanliang lei
Email address: leiyanliang(at)highgo(dot)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 ?
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2021-04-20 07:17:18 | BUG #16973: Backward compatibility: pg_restore: [archiver] unsupported version (1.14) in file header |
Previous Message | Stepan Yankevych | 2021-04-19 18:49:15 | RE: BUG #16961: Could not access status of transaction |