Convert SGML IDs to lower case

IDs in SGML are case insensitive, and we have accumulated a mix of upper
and lower case IDs, including different variants of the same ID.  In
XML, these will be case sensitive, so we need to fix up those
differences.  Going to all lower case seems most straightforward, and
the current build process already makes all anchors and lower case
anyway during the SGML->XML conversion, so this doesn't create any
difference in the output right now.  A future XML-only build process
would, however, maintain any mixed case ID spellings in the output, so
that is another reason to clean this up beforehand.

Author: Alexander Lakhin <exclusion@gmail.com>

Author: petere

doc/src/sgml/acronyms.sgml

@@ -232,7 +232,7 @@
     <term><acronym>GIN</acronym></term>
     <listitem>
      <para>
-      <link linkend="GIN">Generalized Inverted Index</link>
+      <link linkend="gin">Generalized Inverted Index</link>
      </para>
     </listitem>
    </varlistentry>
@@ -241,7 +241,7 @@
     <term><acronym>GiST</acronym></term>
     <listitem>
      <para>
-      <link linkend="GiST">Generalized Search Tree</link>
+      <link linkend="gist">Generalized Search Tree</link>
      </para>
     </listitem>
    </varlistentry>
@@ -583,7 +583,7 @@
     <term><acronym>SP-GiST</acronym></term>
     <listitem>
      <para>
-      <link linkend="SPGiST">Space-Partitioned Generalized Search Tree</link>
+      <link linkend="spgist">Space-Partitioned Generalized Search Tree</link>
      </para>
     </listitem>
    </varlistentry>

doc/src/sgml/arch-dev.sgml

@@ -7,7 +7,7 @@
    <title>Author</title>
    <para>
     This chapter originated as part of
-    <xref linkend="SIM98">, Stefan Simkovics'
+    <xref linkend="sim98">, Stefan Simkovics'
     Master's Thesis prepared at Vienna University of Technology under the direction
     of O.Univ.Prof.Dr. Georg Gottlob and Univ.Ass. Mag. Katrin Seyr.
    </para>

doc/src/sgml/biblio.sgml

@@ -18,7 +18,7 @@
   <bibliodiv>
    <title><acronym>SQL</acronym> Reference Books</title>
 
-   <biblioentry id="BOWMAN01">
+   <biblioentry id="bowman01">
     <title>The Practical <acronym>SQL</acronym> Handbook</title>
     <subtitle>Using SQL Variants</subtitle>
     <edition>Fourth Edition</edition>
@@ -43,7 +43,7 @@
     <pubdate>2001</pubdate>
    </biblioentry>
 
-   <biblioentry id="DATE97">
+   <biblioentry id="date97">
     <title>A Guide to the <acronym>SQL</acronym> Standard</title>
     <subtitle>A user's guide to the standard database language <acronym>SQL</acronym></subtitle>
     <edition>Fourth Edition</edition>
@@ -64,7 +64,7 @@
     <pubdate>1997</pubdate>
    </biblioentry>
 
-   <biblioentry id="DATE04">
+   <biblioentry id="date04">
     <title>An Introduction to Database Systems</title>
     <edition>Eighth Edition</edition>
     <authorgroup>
@@ -80,7 +80,7 @@
     <pubdate>2003</pubdate>
    </biblioentry>
 
-  <biblioentry id="ELMA04">
+  <biblioentry id="elma04">
    <title>Fundamentals of Database Systems</title>
    <edition>Fourth Edition</edition>
    <authorgroup>
@@ -100,7 +100,7 @@
    <pubdate>2003</pubdate>
   </biblioentry>
 
-   <biblioentry id="MELT93">
+   <biblioentry id="melt93">
     <title>Understanding the New <acronym>SQL</acronym></title>
     <subtitle>A complete guide</subtitle>
     <authorgroup>
@@ -120,7 +120,7 @@
     <pubdate>1993</pubdate>
    </biblioentry>
 
-   <biblioentry id="ULL88">
+   <biblioentry id="ull88">
     <title>Principles of Database and Knowledge</title>
     <subtitle>Base Systems</subtitle>
     <authorgroup>
@@ -141,7 +141,7 @@
   <bibliodiv>
    <title>PostgreSQL-specific Documentation</title>
 
-   <biblioentry id="SIM98">
+   <biblioentry id="sim98">
     <title>Enhancement of the ANSI SQL Implementation of PostgreSQL</title>
     <authorgroup>
      <author>
@@ -185,7 +185,7 @@ ssimkovi@ag.or.at
     <pubdate>November 29, 1998</pubdate>
    </biblioentry>
 
-   <biblioentry id="YU95">
+   <biblioentry id="yu95">
     <title>The <productname>Postgres95</productname> User Manual</title>
     <authorgroup>
      <author>
@@ -204,7 +204,7 @@ ssimkovi@ag.or.at
     <pubdate>Sept. 5, 1995</pubdate>
    </biblioentry>
 
-  <biblioentry id="FONG">
+  <biblioentry id="fong">
    <title><ulink url="http://db.cs.berkeley.edu/papers/UCB-MS-zfong.pdf">The
    design and implementation of the <productname>POSTGRES</productname> query
    optimizer</ulink></title>
@@ -222,7 +222,7 @@ ssimkovi@ag.or.at
   <bibliodiv>
    <title>Proceedings and Articles</title>
 
-   <biblioentry id="OLSON93">
+   <biblioentry id="olson93">
     <title>Partial indexing in POSTGRES: research project</title>
     <authorgroup>
      <author>
@@ -238,7 +238,7 @@ ssimkovi@ag.or.at
     <pubdate>1993</pubdate>
    </biblioentry>
 
-   <biblioentry id="ONG90">
+   <biblioentry id="ong90">
    <biblioset relation="article">
     <title>A Unified Framework for Version Modeling Using Production Rules in a Database System</title>
     <authorgroup>
@@ -262,7 +262,7 @@ ssimkovi@ag.or.at
    </biblioset>
    </biblioentry>
 
-   <biblioentry id="ROWE87">
+   <biblioentry id="rowe87">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M87-13.pdf">The <productname>POSTGRES</productname>
     data model</ulink></title>
@@ -284,7 +284,7 @@ ssimkovi@ag.or.at
     </confgroup>
    </biblioentry>
 
-   <biblioentry id="SESHADRI95">
+   <biblioentry id="seshadri95">
    <biblioset relation="article">
     <title><ulink url="http://citeseer.ist.psu.edu/seshadri95generalized.html">Generalized
     Partial Indexes</ulink></title>
@@ -313,7 +313,7 @@ ssimkovi@ag.or.at
     <pagenums>420-7</pagenums>
    </biblioentry>
 
-   <biblioentry id="STON86">
+   <biblioentry id="ston86">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M85-95.pdf">The
     design of <productname>POSTGRES</productname></ulink></title>
@@ -335,7 +335,7 @@ ssimkovi@ag.or.at
     </confgroup>
    </biblioentry>
 
-   <biblioentry id="STON87a">
+   <biblioentry id="ston87a">
    <biblioset relation="article">
     <title>The design of the <productname>POSTGRES</productname> rules system</title>
     <authorgroup>
@@ -360,7 +360,7 @@ ssimkovi@ag.or.at
     </confgroup>
    </biblioentry>
 
-   <biblioentry id="STON87b">
+   <biblioentry id="ston87b">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M87-06.pdf">The
     design of the <productname>POSTGRES</productname> storage
@@ -379,7 +379,7 @@ ssimkovi@ag.or.at
     </confgroup>
    </biblioentry>
 
-   <biblioentry id="STON89">
+   <biblioentry id="ston89">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-82.pdf">A
     commentary on the <productname>POSTGRES</productname> rules
@@ -405,7 +405,7 @@ ssimkovi@ag.or.at
    </biblioset>
    </biblioentry>
 
-   <biblioentry id="STON89b">
+   <biblioentry id="ston89b">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M89-17.pdf">The
     case for partial indexes</ulink></title>
@@ -423,7 +423,7 @@ ssimkovi@ag.or.at
    </biblioset>
    </biblioentry>
 
-   <biblioentry id="STON90a">
+   <biblioentry id="ston90a">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-34.pdf">The
     implementation of <productname>POSTGRES</productname></ulink></title>
@@ -451,7 +451,7 @@ ssimkovi@ag.or.at
    </biblioset>
    </biblioentry>
 
-   <biblioentry id="STON90b">
+   <biblioentry id="ston90b">
    <biblioset relation="article">
     <title><ulink url="http://db.cs.berkeley.edu/papers/ERL-M90-36.pdf">On
     Rules, Procedures, Caching and Views in Database Systems</ulink></title>

doc/src/sgml/brin.sgml

@@ -1,6 +1,6 @@
 <!-- doc/src/sgml/brin.sgml -->
 
-<chapter id="BRIN">
+<chapter id="brin">
 <title>BRIN Indexes</title>
 
    <indexterm>

doc/src/sgml/btree-gist.sgml

@@ -36,7 +36,7 @@
   In addition to the typical B-tree search operators, <filename>btree_gist</filename>
   also provides index support for <literal>&lt;&gt;</literal> (<quote>not
   equals</quote>). This may be useful in combination with an
-  <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion constraint</link>,
+  <link linkend="sql-createtable-exclude">exclusion constraint</link>,
   as described below.
  </para>
 
@@ -70,7 +70,7 @@ SELECT *, a &lt;-&gt; 42 AS dist FROM test ORDER BY a &lt;-&gt; 42 LIMIT 10;
 </programlisting>
 
   <para>
-   Use an <link linkend="SQL-CREATETABLE-EXCLUDE">exclusion
+   Use an <link linkend="sql-createtable-exclude">exclusion
    constraint</link> to enforce the rule that a cage at a zoo
    can contain only one kind of animal:
   </para>

doc/src/sgml/config.sgml

@@ -170,7 +170,7 @@ shared_buffers = 128MB
      <filename>postgresql.auto.conf</filename><indexterm><primary>postgresql.auto.conf</primary></indexterm>,
      which has the same format as <filename>postgresql.conf</filename> but should
      never be edited manually.  This file holds settings provided through
-     the <xref linkend="SQL-ALTERSYSTEM"> command.  This file is automatically
+     the <xref linkend="sql-altersystem"> command.  This file is automatically
      read whenever <filename>postgresql.conf</filename> is, and its settings take
      effect in the same way.  Settings in <filename>postgresql.auto.conf</filename>
      override those in <filename>postgresql.conf</filename>.
@@ -191,7 +191,7 @@ shared_buffers = 128MB
      <para>
       <productname>PostgreSQL</productname> provides three SQL
       commands to establish configuration defaults.
-      The already-mentioned <xref linkend="SQL-ALTERSYSTEM"> command
+      The already-mentioned <xref linkend="sql-altersystem"> command
       provides a SQL-accessible means of changing global defaults; it is
       functionally equivalent to editing <filename>postgresql.conf</filename>.
       In addition, there are two commands that allow setting of defaults
@@ -232,15 +232,15 @@ shared_buffers = 128MB
     <itemizedlist>
      <listitem>
      <para>
-      The <xref linkend="SQL-SHOW"> command allows inspection of the
+      The <xref linkend="sql-show"> command allows inspection of the
       current value of all parameters.  The corresponding function is
       <function>current_setting(setting_name text)</function>.
      </para>
      </listitem>
 
      <listitem>
       <para>
-       The <xref linkend="SQL-SET"> command allows modification of the
+       The <xref linkend="sql-set"> command allows modification of the
        current value of those parameters that can be set locally to a
        session; it has no effect on other sessions.
        The corresponding function is
@@ -266,7 +266,7 @@ shared_buffers = 128MB
 
      <listitem>
       <para>
-       Using <xref linkend="SQL-UPDATE"> on this view, specifically
+       Using <xref linkend="sql-update"> on this view, specifically
        updating the <structname>setting</structname> column, is the equivalent
        of issuing <command>SET</command> commands.  For example, the equivalent of
 <programlisting>
@@ -6237,7 +6237,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
 
        <para>
         For more information on row security policies,
-        see <xref linkend="SQL-CREATEPOLICY">.
+        see <xref linkend="sql-createpolicy">.
        </para>
       </listitem>
      </varlistentry>
@@ -7040,7 +7040,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
         This variable specifies one or more shared libraries that are to be
         preloaded at connection start.
         It contains a comma-separated list of library names, where each name
-        is interpreted as for the <xref linkend="SQL-LOAD"> command.
+        is interpreted as for the <xref linkend="sql-load"> command.
         Whitespace between entries is ignored; surround a library name with
         double quotes if you need to include whitespace or commas in the name.
         The parameter value only takes effect at the start of the connection.
@@ -7091,7 +7091,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
         This variable specifies one or more shared libraries that are to be
         preloaded at connection start.
         It contains a comma-separated list of library names, where each name
-        is interpreted as for the <xref linkend="SQL-LOAD"> command.
+        is interpreted as for the <xref linkend="sql-load"> command.
         Whitespace between entries is ignored; surround a library name with
         double quotes if you need to include whitespace or commas in the name.
         The parameter value only takes effect at the start of the connection.
@@ -7133,7 +7133,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
         This variable specifies one or more shared libraries to be preloaded at
         server start.
         It contains a comma-separated list of library names, where each name
-        is interpreted as for the <xref linkend="SQL-LOAD"> command.
+        is interpreted as for the <xref linkend="sql-load"> command.
         Whitespace between entries is ignored; surround a library name with
         double quotes if you need to include whitespace or commas in the name.
         This parameter can only be set at server start.  If a specified