Fix XML id to match GUC name

For some reason, the id of the description of
max_parallel_maintenance_workers has been
guc-max-parallel-workers-maintenance since the beginning.  Flip that
around to make it consistent.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 8eabf93834a495cd7b9298e1b569fb5f9cabfe1d..06405f359cdfe163b9e7ce2acb2db544be2e63c1 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -2367,7 +2367,7 @@ include_dir 'conf.d'
         
          When changing this value, consider also adjusting
          ,
-         workers-maintenance"/>, and
+         maintenance-workers"/>, and
          .
         
        
@@ -2415,7 +2415,7 @@ include_dir 'conf.d'
        
       
 
-      workers-maintenance" xreflabel="max_parallel_maintenance_workers">
+      maintenance-workers" xreflabel="max_parallel_maintenance_workers">
        max_parallel_maintenance_workers (integer)
        
         max_parallel_maintenance_workers configuration parameter
@@ -2464,7 +2464,7 @@ include_dir 'conf.d'
          Sets the maximum number of workers that the system can support for
          parallel operations.  The default value is 8.  When increasing or
          decreasing this value, consider also adjusting
-         workers-maintenance"/> and
+         maintenance-workers"/> and
          .
          Also, note that a setting for this value which is higher than
           will have no effect,

diff --git a/doc/src/sgml/ref/create_index.sgml b/doc/src/sgml/ref/create_index.sgml
index 33aa64e81d58fd15fb2a304bcfbfa615cbdd5c1b..7fa79f4cbfb0efb1637fd8bc305b0baf39ae9f48 100644 (file)
--- a/doc/src/sgml/ref/create_index.sgml
+++ b/doc/src/sgml/ref/create_index.sgml
@@ -771,7 +771,7 @@ Indexes:
    least a 32MB share of the total
    maintenance_work_mem budget.  There must also be
    a remaining 32MB share for the leader process.
-   Increasing workers-maintenance"/>
+   Increasing maintenance-workers"/>
    may allow more workers to be used, which will reduce the time
    needed for index creation, so long as the index build is not
    already I/O bound.  Of course, there should also be sufficient

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index a48f75ad7baf28a0cd39903c89ad713ae7ebd972..26ede69bb31d9f904be6d55bdc06084de2f4479c 100644 (file)
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -239,7 +239,7 @@ VACUUM [ FULL ] [ FREEZE ] [ VERBOSE ] [ ANALYZE ] [ 
       (without FULL), if the PARALLEL option
       is omitted, then the number of workers is determined based on the number of
       indexes on the relation that support parallel vacuum operation and is further
-      limited by workers-maintenance"/>.  An index
+      limited by maintenance-workers"/>.  An index
       can participate in parallel vacuum if and only if the size of the index is
       more than .  Please note
       that it is not guaranteed that the number of parallel workers specified in