Commit c1ef4e5c authored by Robert Haas's avatar Robert Haas

Make some more improvements to parallel query documentation.

Many places that mentioned only Gather should also mention Gather
Merge, or should be phrased in a more neutral way.  Be more clear
about the fact that max_parallel_workers_per_gather affects the number
of workers the planner may want to use.  Fix a typo.  Explain how
Gather Merge works.  Adjust wording around parallel scans to be a bit
more clear.  Adjust wording around parallel-restricted operations for
the fact that uncorrelated subplans are no longer restricted.

Patch by me, reviewed by Erik Rijkers

Discussion: http://postgr.es/m/CA+TgmoZsTjgVGn=ei5ht-1qGFKy_m1VgB3d8+Rg304hz91N5ww@mail.gmail.com
parent e6940107
...@@ -2050,8 +2050,8 @@ include_dir 'conf.d' ...@@ -2050,8 +2050,8 @@ include_dir 'conf.d'
<listitem> <listitem>
<para> <para>
Sets the maximum number of workers that can be started by a single Sets the maximum number of workers that can be started by a single
<literal>Gather</literal> node. Parallel workers are taken from the <literal>Gather</literal> or <literal>Gather Merge</literal> node.
pool of processes established by Parallel workers are taken from the pool of processes established by
<xref linkend="guc-max-worker-processes">, limited by <xref linkend="guc-max-worker-processes">, limited by
<xref linkend="guc-max-parallel-workers">. Note that the requested <xref linkend="guc-max-parallel-workers">. Note that the requested
number of workers may not actually be available at run time. If this number of workers may not actually be available at run time. If this
......
This diff is collapsed.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment