This patch fixes a few missed GUC variables that were still upper case,

makes a few more small improvements to runtime.sgml, and makes some SGML
conventions more consistent.

Neil Conway

Author: bmomjian

doc/src/sgml/docguide.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.44 2003/06/06 14:17:08 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/docguide.sgml,v 1.45 2003/09/11 21:42:19 momjian Exp $ -->
 
 <appendix id="docguide">
  <title>Documentation</title>
@@ -497,8 +497,9 @@ CATALOG "docbook-dsssl--1.<replaceable>xx</>/catalog
   <para>
    Before you can build the documentation you need to run the
    <filename>configure</filename> script as you would when building
-   the PostgreSQL programs themselves.  Check the output near the end
-   of the run, it should look something like this:
+   the <productname>PostgreSQL</productname> programs themselves.
+   Check the output near the end of the run, it should look something
+   like this:
 <screen>
 <computeroutput>
 checking for onsgmls... onsgmls
@@ -640,7 +641,7 @@ gmake man.tar.gz
    <title>Print Output via <acronym>RTF</acronym></title>
 
    <para>
-    You can also create a printable version of the PostgreSQL
+    You can also create a printable version of the <productname>PostgreSQL</productname>
     documentation by converting it to <acronym>RTF</acronym> and
     applying minor formatting corrections using an office suite.
     Depending on the capabilities of the particular office suite, you
@@ -651,7 +652,7 @@ gmake man.tar.gz
 
    <note>
     <para>
-     It appears that current versions of the PostgreSQL documentation
+     It appears that current versions of the <productname>PostgreSQL</productname> documentation
      trigger some bug in or exceed the size limit of OpenJade.  If the
      build process of the <acronym>RTF</acronym> version hangs for a
      long time and the output file still has size 0, then you may have

doc/src/sgml/ecpg.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.50 2003/09/09 10:54:44 meskes Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ecpg.sgml,v 1.51 2003/09/11 21:42:19 momjian Exp $
 -->
 
 <chapter id="ecpg">
@@ -1153,10 +1153,11 @@ struct
     condition.  A successful state is indicated by the code
     <literal>00000</literal>.  Further information about the codes can
     be found XXX.  The <literal>SQLSTATE</literal> codes are for the
-    most part defined in the SQL standard.  The PostgreSQL server
-    natively supports <literal>SQLSTATE</literal> error codes;
-    therefore a high degree of consistency can be achieved by using
-    this error code scheme throughout all applications.
+    most part defined in the SQL standard.  The
+    <productname>PostgreSQL</productname> server natively supports
+    <literal>SQLSTATE</literal> error codes; therefore a high degree
+    of consistency can be achieved by using this error code scheme
+    throughout all applications.
    </para>
 
    <para>
@@ -1168,11 +1169,11 @@ struct
     affected zero rows, and no specific negative values.  Therefore,
     this scheme can only achieve poor portability and does not have a
     hierarchical code assignment.  Historically, the embedded SQL
-    processor for PostgreSQL has assigned some specific
-    <literal>SQLCODE</literal> values for its use, which are listed
-    below with their numeric value and their symbolic name.  Remember
-    that these are not portable to other SQL implementations.  To
-    simplify the porting of applications to the
+    processor for <productname>PostgreSQL</productname> has assigned
+    some specific <literal>SQLCODE</literal> values for its use, which
+    are listed below with their numeric value and their symbolic name.
+    Remember that these are not portable to other SQL implementations.
+    To simplify the porting of applications to the
     <literal>SQLSTATE</literal> scheme, the corresponding
     <literal>SQLSTATE</literal> is also listed.  There is, however, no
     one-to-one or one-to-many mapping between the two schemes (indeed
@@ -1291,9 +1292,10 @@ struct
      <term>-208 (<symbol>ECPG_EMPTY</symbol>)</term>
      <listitem>
       <para>
-       The statement sent to the PostgreSQL server was empty.  (This
-       cannot normally happen in an embedded SQL program, so it may
-       point to an internal error.)  (SQLSTATE YE002)
+       The statement sent to the <productname>PostgreSQL</productname>
+       server was empty.  (This cannot normally happen in an embedded
+       SQL program, so it may point to an internal error.)  (SQLSTATE
+       YE002)
       </para>
      </listitem>
     </varlistentry>

doc/src/sgml/extend.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.24 2003/08/31 17:32:18 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.25 2003/09/11 21:42:19 momjian Exp $
 -->
 
  <chapter id="extend">
@@ -69,14 +69,16 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.24 2003/08/31 17:32:18 pete
    </para>
 
    <para>
-    The PostgreSQL server can moreover incorporate user-written code into
-    itself through dynamic loading.  That is, the user  can
-    specify  an  object code file (e.g., a shared library) that implements a new type or  function,
-    and <productname>PostgreSQL</productname> will load it as required.  Code written 
-    in <acronym>SQL</acronym> is even more trivial to add to the  server.
-    This ability to modify its operation <quote>on the fly</quote> makes
-    <productname>PostgreSQL</productname> uniquely suited for rapid prototyping  of  new
-    applications and storage structures.
+    The <productname>PostgreSQL</productname> server can moreover
+    incorporate user-written code into itself through dynamic loading.
+    That is, the user can specify an object code file (e.g., a shared
+    library) that implements a new type or function, and
+    <productname>PostgreSQL</productname> will load it as required.
+    Code written in <acronym>SQL</acronym> is even more trivial to add
+    to the server.  This ability to modify its operation <quote>on the
+    fly</quote> makes <productname>PostgreSQL</productname> uniquely
+    suited for rapid prototyping of new applications and storage
+    structures.
    </para>
   </sect1>
 

doc/src/sgml/features.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.18 2003/03/13 01:30:28 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.19 2003/09/11 21:42:19 momjian Exp $
 -->
 
 <appendix id="features">
@@ -63,11 +63,12 @@ $Header: /cvsroot/pgsql/doc/src/sgml/features.sgml,v 2.18 2003/03/13 01:30:28 pe
   In the following two sections, we provide a list of those features
   that <productname>PostgreSQL</productname> supports, followed by a
   list of the features defined in SQL99 which are not yet supported in
-  PostgreSQL.  Both of these lists are approximate: There may be minor
-  details that are nonconforming for a feature that is listed as
-  supported, and large parts of an unsupported feature may in fact be
-  implemented.  The main body of the documentation always contains the
-  most accurate information about what does and does not work.
+  <productname>PostgreSQL</productname>.  Both of these lists are
+  approximate: There may be minor details that are nonconforming for a
+  feature that is listed as supported, and large parts of an
+  unsupported feature may in fact be implemented.  The main body of
+  the documentation always contains the most accurate information
+  about what does and does not work.
  </para>
 
  <note>

doc/src/sgml/history.sgml

@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.21 2003/09/08 23:02:28 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.22 2003/09/11 21:42:19 momjian Exp $
 -->
 
 <sect1 id="history">
@@ -206,8 +206,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.21 2003/09/08 23:02:28 pet
   </para>
 
   <para>
-   Details about what has happened in PostgreSQL since then can be
-   found in <xref linkend="release">.
+   Details about what has happened in <productname>PostgreSQL</> since
+   then can be found in <xref linkend="release">.
   </para>
  </sect2>
 </sect1>

doc/src/sgml/indices.sgml

@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/indices.sgml,v 1.43 2003/08/31 17:32:19 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/indices.sgml,v 1.44 2003/09/11 21:42:19 momjian Exp $ -->
 
 <chapter id="indexes">
  <title id="indexes-title">Indexes</title>
@@ -194,11 +194,11 @@ CREATE INDEX <replaceable>name</replaceable> ON <replaceable>table</replaceable>
 </synopsis>
    <note>
     <para>
-     Testing has shown PostgreSQL's hash indexes to be similar or slower
-     than B-tree indexes, and the index size and build time for hash
-     indexes is much worse. Hash indexes also suffer poor performance
-     under high concurrency. For these reasons, hash index use is
-     presently discouraged.
+     Testing has shown <productname>PostgreSQL</productname>'s hash
+     indexes to be similar or slower than B-tree indexes, and the
+     index size and build time for hash indexes is much worse. Hash
+     indexes also suffer poor performance under high concurrency. For
+     these reasons, hash index use is presently discouraged.
     </para>
    </note>  
   </para>