mirror of
https://github.com/postgres/postgres.git
synced 2025-08-22 21:53:06 +03:00
Eliminate "parallel degree" terminology.
This terminology provoked widespread complaints. So, instead, rename the GUC max_parallel_degree to max_parallel_workers_per_gather (leaving room for a possible future GUC max_parallel_workers that acts as a system-wide limit), and rename the parallel_degree reloption to parallel_workers. Rename structure members to match. These changes create a dump/restore hazard for users of PostgreSQL 9.6beta1 who have set the reloption (or applied the GUC using ALTER USER or ALTER DATABASE).
This commit is contained in:
@@ -909,14 +909,14 @@ CREATE [ [ GLOBAL | LOCAL ] { TEMPORARY | TEMP } | UNLOGGED ] TABLE [ IF NOT EXI
|
||||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><literal>parallel_degree</> (<type>integer</>)</term>
|
||||
<term><literal>parallel_workers</> (<type>integer</>)</term>
|
||||
<listitem>
|
||||
<para>
|
||||
The parallel degree for a table is the number of workers that should
|
||||
be used to assist a parallel scan of that table. If not set, the
|
||||
system will determine a value based on the relation size. The actual
|
||||
number of workers chosen by the planner may be less, for example due to
|
||||
the setting of <xref linkend="guc-max-parallel-degree">.
|
||||
This sets the number of workers that should be used to assist a parallel
|
||||
scan of this table. If not set, the system will determine a value based
|
||||
on the relation size. The actual number of workers chosen by the planner
|
||||
may be less, for example due to
|
||||
the setting of <xref linkend="guc-max-worker-processes">.
|
||||
</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
Reference in New Issue
Block a user