Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Fix typo in commit 99ae342fc4.
authorAmit Kapila <akapila@postgresql.org>
Tue, 20 Oct 2020 03:01:43 +0000 (08:31 +0530)
committerAmit Kapila <akapila@postgresql.org>
Tue, 20 Oct 2020 03:01:43 +0000 (08:31 +0530)
In v13, the id for max_parallel_maintenance_workers is defined differently
as compared to HEAD in docs, so adjust the docs accordingly.

Reported-by: Magnus Hagander and Tom Lane
Discussion: https://postgr.es/m/CABUevEyAFQZ_jvjY_KtRUWbci4YMyQC1QAMzDQAbLs=XCo3m5Q@mail.gmail.com

doc/src/sgml/ref/vacuum.sgml

index 21ab57d880489e536918821371c34dcc0b9d75c8..e232aba7c4816a193ae8b62964b934d66759128f 100644 (file)
@@ -239,7 +239,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ <replaceable class="paramet
       to perform the operation is equal to the number of indexes on the
       relation that support parallel vacuum which is limited by the number of
       workers specified with <literal>PARALLEL</literal> option if any which is
-      further limited by <xref linkend="guc-max-parallel-maintenance-workers"/>.
+      further limited by <xref linkend="guc-max-parallel-workers-maintenance"/>.
       An index can participate in parallel vacuum if and only if the size of the
       index is more than <xref linkend="guc-min-parallel-index-scan-size"/>.
       Please note that it is not guaranteed that the number of parallel workers