Doc: fix a few oddly-spelled SGML ID attributes.

Avoid use of "_" in SGML IDs.  Awhile back that was actually
disallowed by the toolchain, as a consequence of which our convention
has been to use "-" instead.  Fix a couple of stragglers that are
particularly inconsistent with that convention and with related IDs.

This is just neatnik-ism, so no need for back-patch.

Discussion: https://postgr.es/m/769446.1673478332@sss.pgh.pa.us

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 77574e2d4ec1f735acbd4cacc3d9e3a61c72af60..89d53f2a6458a78fef54bf4e06216699a79e149f 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -6062,7 +6062,7 @@ SELECT * FROM parent WHERE key = 2400;
       </listitem>
      </varlistentry>
 
-     <varlistentry id="guc-plan-cache_mode" xreflabel="plan_cache_mode">
+     <varlistentry id="guc-plan-cache-mode" xreflabel="plan_cache_mode">
       <term><varname>plan_cache_mode</varname> (<type>enum</type>)
       <indexterm>
        <primary><varname>plan_cache_mode</varname> configuration parameter</primary>

diff --git a/doc/src/sgml/pgbuffercache.sgml b/doc/src/sgml/pgbuffercache.sgml
index fc101cf1908b44729c1f870ee297b03a690bfd78..7b118f2030b78844327b24acf1fb5ef6d22dbaff 100644 (file)
--- a/doc/src/sgml/pgbuffercache.sgml
+++ b/doc/src/sgml/pgbuffercache.sgml
@@ -183,10 +183,10 @@
   <title>The <function>pg_buffercache_summary()</function> Function</title>
 
   <para>
-   The definitions of the columns exposed by the function are shown in <xref linkend="pgbuffercache_summary-columns"/>.
+   The definitions of the columns exposed by the function are shown in <xref linkend="pgbuffercache-summary-columns"/>.
   </para>
 
-  <table id="pgbuffercache_summary-columns">
+  <table id="pgbuffercache-summary-columns">
    <title><function>pg_buffercache_summary()</function> Output Columns</title>
    <tgroup cols="1">
     <thead>

diff --git a/doc/src/sgml/ref/pg_checksums.sgml b/doc/src/sgml/ref/pg_checksums.sgml
index bab9501ce098df938f1c92127625c92825b04759..a3d0b0f0a3d64e26792e89dbed52c16642c19774 100644 (file)
--- a/doc/src/sgml/ref/pg_checksums.sgml
+++ b/doc/src/sgml/ref/pg_checksums.sgml
@@ -33,7 +33,7 @@ PostgreSQL documentation
   </cmdsynopsis>
  </refsynopsisdiv>
 
- <refsect1 id="r1-app-pg_checksums-1">
+ <refsect1 id="r1-app-pgchecksums-1">
   <title>Description</title>
   <para>
    <application>pg_checksums</application> checks, enables or disables data

diff --git a/doc/src/sgml/ref/prepare.sgml b/doc/src/sgml/ref/prepare.sgml
index aae91946c75760cb04e3415f38979e8bec0894ef..f9e0cdc69a154873db87a9039072bc5ea3f00bd5 100644 (file)
--- a/doc/src/sgml/ref/prepare.sgml
+++ b/doc/src/sgml/ref/prepare.sgml
@@ -139,7 +139,7 @@ PREPARE <replaceable class="parameter">name</replaceable> [ ( <replaceable class
   </para>
 
   <para>
-   By default (that is, when <xref linkend="guc-plan-cache_mode"/> is set
+   By default (that is, when <xref linkend="guc-plan-cache-mode"/> is set
    to <literal>auto</literal>), the server will automatically choose
    whether to use a generic or custom plan for a prepared statement that
    has parameters.  The current rule for this is that the first five