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

doc/src/sgml/docguide.sgml

-<!-- $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

 <!--
-$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

 <!--
-$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

 <!--
-$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

 <!--
-$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

-<!-- $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>

doc/src/sgml/installation.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.140 2003/09/01 23:01:49 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.141 2003/09/11 21:42:20 momjian Exp $ -->
 
 <chapter id="installation">
  <title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -406,13 +406,14 @@ JAVACMD=$JAVA_HOME/bin/java
      To make the backup, you can use the <command>pg_dumpall</command>
      command from the version you are currently running.  For best
      results, however, try to use the <command>pg_dumpall</command>
-     command from PostgreSQL &version;, since this version contains
-     bug fixes and improvements over older versions.  While this
-     advice might seem idiosyncratic since you haven't installed the
-     new version yet, it is advisable to follow it if you plan to
-     install the new version in parallel with the old version.  In
-     that case you can complete the installation normally and transfer
-     the data later.  This will also decrease the downtime.
+     command from <productname>PostgreSQL</productname> &version;,
+     since this version contains bug fixes and improvements over older
+     versions.  While this advice might seem idiosyncratic since you
+     haven't installed the new version yet, it is advisable to follow
+     it if you plan to install the new version in parallel with the
+     old version.  In that case you can complete the installation
+     normally and transfer the data later.  This will also decrease
+     the downtime.
     </para>
    </step>
 

doc/src/sgml/intro.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.21 2003/09/08 23:02:28 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.22 2003/09/11 21:42:20 momjian Exp $
 -->
 
 <preface id="preface">
  <title>Preface</title>
 
  <para>
-  This book is the official documentation of PostgreSQL.  It is being
-  written by the PostgreSQL developers and other volunteers in
-  parallel to the development of the PostgreSQL software.  It
-  describes all the functionality that the current version of
-  PostgreSQL officially supports.
+  This book is the official documentation of
+  <productname>PostgreSQL</productname>.  It is being written by the
+  <productname>PostgreSQL</productname> developers and other
+  volunteers in parallel to the development of the
+  <productname>PostgreSQL</productname> software.  It describes all
+  the functionality that the current version of
+  <productname>PostgreSQL</productname> officially supports.
  </para>
 
  <para>
-  To make the large amount of information about PostgreSQL manageable,
-  this book has been organized in several parts.  Each part is
-  targeted at a different class of users, or at users in different
-  stages of their PostgreSQL experience:
+  To make the large amount of information about
+  <productname>PostgreSQL</productname> manageable, this book has been
+  organized in several parts.  Each part is targeted at a different
+  class of users, or at users in different stages of their
+  <productname>PostgreSQL</productname> experience:
 
   <itemizedlist>
    <listitem>
@@ -38,16 +41,17 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.21 2003/09/08 23:02:28 peter
    <listitem>
     <para>
      <xref linkend="admin"> describes the installation and
-     administration of the server.  Everyone that runs a PostgreSQL
-     server, be it for private use or for others, should read this
-     part.
+     administration of the server.  Everyone that runs a
+     <productname>PostgreSQL</productname> server, be it for private
+     use or for others, should read this part.
     </para>
    </listitem>
 
    <listitem>
     <para>
      <xref linkend="client-interfaces"> describes the programming
-     interfaces for PostgreSQL client programs.
+     interfaces for <productname>PostgreSQL</productname> client
+     programs.
     </para>
    </listitem>
 
@@ -111,8 +115,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.21 2003/09/08 23:02:28 peter
     </listitem>
    </itemizedlist>
 
-   Also, PostgreSQL can be extended by the user in many ways, for
-   example by adding new
+   Also, <productname>PostgreSQL</productname> can be extended by the
+   user in many ways, for example by adding new
 
    <itemizedlist spacing="compact">
     <listitem>
@@ -137,9 +141,10 @@ $Header: /cvsroot/pgsql/doc/src/sgml/intro.sgml,v 1.21 2003/09/08 23:02:28 peter
   </para>
 
   <para>
-   And because of the liberal license, PostgreSQL can be used,
-   modified, and distributed by everyone free of charge for any
-   purpose, be it private, commercial, or academic.
+   And because of the liberal license,
+   <productname>PostgreSQL</productname> can be used, modified, and
+   distributed by everyone free of charge for any purpose, be it
+   private, commercial, or academic.
   </para>
  </sect1>
 

doc/src/sgml/libpq.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.135 2003/09/03 22:05:01 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/libpq.sgml,v 1.136 2003/09/11 21:42:20 momjian Exp $
 -->
 
  <chapter id="libpq">
@@ -2049,11 +2049,13 @@ unsigned char *PQescapeBytea(const unsigned char *from,
    <parameter>from</parameter> parameter binary string in memory
    allocated with <function>malloc()</>.  This memory must be freed
    using <function>PQfreemem()</> when the result is no longer needed.
-   The return string has all special characters replaced
-   so that they can be properly processed by the PostgreSQL string literal
-   parser, and the <type>bytea</type> input function. A terminating zero
-   byte is also added.  The single quotes that must surround
-   PostgreSQL string literals are not part of the result string.
+   The return string has all special characters replaced so that they
+   can be properly processed by the
+   <productname>PostgreSQL</productname> string literal parser, and
+   the <type>bytea</type> input function. A terminating zero byte is
+   also added.  The single quotes that must surround
+   <productname>PostgreSQL</productname> string literals are not part
+   of the result string.
   </para>
   </listitem>
   </varlistentry>

doc/src/sgml/plpgsql.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/plpgsql.sgml,v 1.24 2003/09/11 18:30:38 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/plpgsql.sgml,v 1.25 2003/09/11 21:42:20 momjian Exp $
 -->
 
 <chapter id="plpgsql"> 
@@ -2056,9 +2056,10 @@ RAISE <replaceable class="parameter">level</replaceable> '<replaceable class="pa
     (raise an error and abort the current transaction). Whether
     messages of a particular priority are reported to the client,
     written to the server log, or both is controlled by the
-    <option>log_min_messages</option> and
-    <option>client_min_messages</option> configuration variables. See
-    <xref linkend="runtime-config"> for more information.
+    <varname>log_min_messages</varname> and
+    <varname>client_min_messages</varname> configuration
+    variables. See <xref linkend="runtime-config"> for more
+    information.
    </para>
 
    <para>
@@ -2448,7 +2449,8 @@ show errors;
        <para>
         The <literal>RETURN</literal> key word in the function
         prototype (not the function body) becomes
-        <literal>RETURNS</literal> in PostgreSQL.
+        <literal>RETURNS</literal> in
+        <productname>PostgreSQL</productname>.
        </para>
       </listitem>
 
@@ -2805,7 +2807,8 @@ END;
 
    <para>
     This section explains a few other things to watch for when porting
-    Oracle <application>PL/SQL</> functions to PostgreSQL.
+    Oracle <application>PL/SQL</> functions to
+    <productname>PostgreSQL</productname>.
    </para>
 
    <sect3>

doc/src/sgml/protocol.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.43 2003/09/03 22:05:07 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/protocol.sgml,v 1.44 2003/09/11 21:42:20 momjian Exp $ -->
 
 <chapter id="protocol">
  <title>Frontend/Backend Protocol</title>
 
  <para>
-  <application>PostgreSQL</application> uses a message-based protocol
+  <productname>PostgreSQL</productname> uses a message-based protocol
   for communication between frontends and backends (clients and servers).
   The protocol is supported over <acronym>TCP/IP</acronym> and also over
   Unix-domain sockets.  Port number 5432 has been registered with IANA as
@@ -14,7 +14,7 @@
 
  <para>
   This document describes version 3.0 of the protocol, implemented in
-  <application>PostgreSQL</application> 7.4 and later.  For descriptions
+  <productname>PostgreSQL</productname> 7.4 and later.  For descriptions
   of the earlier protocol versions, see previous releases of the
   <productname>PostgreSQL</productname> documentation.  A single server
   can support multiple protocol versions.  The initial
@@ -165,7 +165,7 @@
 
    <para>
     Data of a particular datatype might be transmitted in any of several
-    different <firstterm>formats</>.  As of <application>PostgreSQL</> 7.4
+    different <firstterm>formats</>.  As of <productname>PostgreSQL</> 7.4
     the only supported formats are <quote>text</> and <quote>binary</>,
     but the protocol makes provision for future extensions.  The desired
     format for any value is specified by a <firstterm>format code</>.

doc/src/sgml/ref/copy.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.49 2003/09/09 18:28:52 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/copy.sgml,v 1.50 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -201,7 +201,7 @@ COPY <replaceable class="parameter">table</replaceable> [ ( <replaceable class="
     directly by the server, not by the client application. Therefore,
     they must reside on or be accessible to the database server machine,
     not the client. They must be accessible to and readable or writable
-    by the <application>PostgreSQL</application> user (the user ID the
+    by the <productname>PostgreSQL</productname> user (the user ID the
     server runs as), not the client. <command>COPY</command> naming a
     file is only allowed to database superusers, since it allows reading
     or writing any file that the server has privileges to access.
@@ -367,7 +367,7 @@ COPY <replaceable class="parameter">table</replaceable> [ ( <replaceable class="
 
    <para>
     The file format used for <command>COPY BINARY</command> changed in
-    <application>PostgreSQL</application> 7.4. The new format consists
+    <productname>PostgreSQL</productname> 7.4. The new format consists
     of a file header, zero or more tuples containing the row data, and
     a file trailer. Headers and data are now in network byte order.
    </para>
@@ -474,7 +474,7 @@ to be specified.
 
     <para>
 To determine the appropriate binary format for the actual tuple data you
-should consult the <application>PostgreSQL</application> source, in
+should consult the <productname>PostgreSQL</productname> source, in
 particular the <function>*send</> and <function>*recv</> functions for
 the data type (typically found in the <filename>src/backend/utils/adt</filename>
 directory). The <application>contrib/binarycopy</application> module

doc/src/sgml/ref/create_function.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.51 2003/09/10 20:13:45 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_function.sgml,v 1.52 2003/09/11 21:42:20 momjian Exp $
 -->
 
 <refentry id="SQL-CREATEFUNCTION">
@@ -382,7 +382,7 @@ CREATE FUNCTION add(integer, integer) RETURNS integer
 
   <para>
    A <command>CREATE FUNCTION</command> command is defined in SQL99.
-   The <application>PostgreSQL</application> version is similar but
+   The <productname>PostgreSQL</productname> version is similar but
    not fully compatible.  The attributes are not portable, neither are the
    different available languages.
   </para>

doc/src/sgml/ref/create_index.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.41 2003/09/09 18:28:52 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/create_index.sgml,v 1.42 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -53,7 +53,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
   </para>
 
   <para>
-   <application>PostgreSQL</application> provides the index methods
+   <productname>PostgreSQL</productname> provides the index methods
    B-tree, R-tree, hash, and GiST. The B-tree index method is an
    implementation of Lehman-Yao high-concurrency B-trees. The R-tree
    index method implements standard R-trees using Guttman's quadratic
@@ -198,7 +198,7 @@ CREATE [ UNIQUE ] INDEX <replaceable class="parameter">index_name</replaceable>
    Currently, only the B-tree and GiST index methods support
    multicolumn indexes. Up to 32 fields may be specified by default.
    (This limit can be altered when building
-   <application>PostgreSQL</application>.)  Only B-tree currently
+   <productname>PostgreSQL</productname>.)  Only B-tree currently
    supports unique indexes.
   </para>
 

doc/src/sgml/ref/declare.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.26 2003/08/31 17:32:22 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/declare.sgml,v 1.27 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -105,9 +105,9 @@ DECLARE <replaceable class="parameter">cursorname</replaceable> [ BINARY ] [ INS
      <para>
       Indicates that data retrieved from the cursor should be
       unaffected by updates to the tables underlying the cursor while
-      the cursor exists.  In PostgreSQL, all cursors are insensitive;
-      this key word currently has no effect and is present for
-      compatibility with the SQL standard.
+      the cursor exists.  In <productname>PostgreSQL</productname>,
+      all cursors are insensitive; this key word currently has no
+      effect and is present for compatibility with the SQL standard.
      </para>
     </listitem>
    </varlistentry>

doc/src/sgml/ref/end.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.10 2003/08/31 17:32:23 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/end.sgml,v 1.11 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -30,9 +30,9 @@ END [ WORK | TRANSACTION ]
   <para>
    <command>END</command> commits the current transaction. All changes
    made by the transaction become visible to others and are guaranteed
-   to be durable if a crash occurs.  It is a PostgreSQL extension that
-   is equivalent to <xref linkend="sql-commit"
-   endterm="sql-commit-title">.
+   to be durable if a crash occurs.  It is a
+   <productname>PostgreSQL</productname> extension that is equivalent
+   to <xref linkend="sql-commit" endterm="sql-commit-title">.
   </para>
  </refsect1>
   

doc/src/sgml/ref/grant.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.34 2003/08/31 17:32:23 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/grant.sgml,v 1.35 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -375,8 +375,8 @@ GRANT <replaceable class="PARAMETER">privileges</replaceable>
 
    <para>
     The <literal>RULE</literal> privilege, and privileges on
-    databases, schemas, languages, and sequences are PostgreSQL
-    extensions.
+    databases, schemas, languages, and sequences are
+    <productname>PostgreSQL</productname> extensions.
    </para>
  </refsect1>
 

doc/src/sgml/ref/load.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/load.sgml,v 1.18 2003/08/31 17:32:23 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/load.sgml,v 1.19 2003/09/11 21:42:20 momjian Exp $
 -->
 
 <refentry id="SQL-LOAD">
@@ -50,7 +50,7 @@ LOAD '<replaceable class="PARAMETER">filename</replaceable>'
   <title>Compatibility</title>
 
   <para>
-   <command>LOAD</command> is a <application>PostgreSQL</application>
+   <command>LOAD</command> is a <productname>PostgreSQL</productname>
    extension.
   </para>
  </refsect1>

doc/src/sgml/ref/lock.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.37 2003/09/09 18:28:53 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/lock.sgml,v 1.38 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -201,7 +201,7 @@ COMMIT WORK;
   <para>
    There is no <command>LOCK TABLE</command> in the SQL standard,
    which instead uses <command>SET TRANSACTION</command> to specify
-   concurrency levels on transactions.  PostgreSQL supports that too;
+   concurrency levels on transactions.  <productname>PostgreSQL</productname> supports that too;
    see <xref linkend="SQL-SET-TRANSACTION"
    endterm="SQL-SET-TRANSACTION-TITLE"> for details.
   </para>

doc/src/sgml/ref/pg_dump.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.63 2003/08/31 17:32:23 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.64 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -705,7 +705,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
    The <application>pg_dump</application> utility first appeared in
    <application>Postgres95</application> release 0.02.  The
    non-plain-text output formats were introduced in
-   <application>PostgreSQL</application> release 7.1.
+   <productname>PostgreSQL</productname> release 7.1.
   </para>
  </refsect1>
 

doc/src/sgml/ref/pg_restore.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.41 2003/08/31 17:32:24 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.42 2003/09/11 21:42:20 momjian Exp $ -->
 
 <refentry id="APP-PGRESTORE">
  <refmeta>
@@ -659,7 +659,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
 
   <para>
    The <application>pg_restore</application> utility first appeared in
-   PostgreSQL 7.1.
+   <productname>PostgreSQL</productname> 7.1.
   </para>
  </refsect1>
 

doc/src/sgml/ref/reindex.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.19 2003/09/09 18:28:53 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/reindex.sgml,v 1.20 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -46,11 +46,12 @@ REINDEX { DATABASE | TABLE | INDEX } <replaceable class="PARAMETER">name</replac
     <listitem>
      <para>
       The index in question contains a lot of dead index pages that
-      are not being reclaimed. This can occur with B-tree indexes in PostgreSQL
-      under certain access patterns. <command>REINDEX</command>
-      provides a way to reduce the space consumption of the index by
-      writing a new version of the index without the dead pages. See
-      <xref linkend="routine-reindex"> for more information.
+      are not being reclaimed. This can occur with B-tree indexes in
+      <productname>PostgreSQL</productname> under certain access
+      patterns. <command>REINDEX</command> provides a way to reduce
+      the space consumption of the index by writing a new version of
+      the index without the dead pages. See <xref
+      linkend="routine-reindex"> for more information.
      </para>
     </listitem>
    </itemizedlist>

doc/src/sgml/ref/select.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.69 2003/08/31 17:32:24 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/select.sgml,v 1.70 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -798,10 +798,10 @@ FOR UPDATE [ OF <replaceable class="parameter">table_name</replaceable> [, ...]
 
    <para>
     <literal>FOR UPDATE</literal> may appear before
-    <literal>LIMIT</literal> for compatibility with PostgreSQL
-    versions before 7.3.  It effectively executes after
-    <literal>LIMIT</literal>, however, and so that is the recommended
-    place to write it.
+    <literal>LIMIT</literal> for compatibility with
+    <productname>PostgreSQL</productname> versions before 7.3.  It
+    effectively executes after <literal>LIMIT</literal>, however, and
+    so that is the recommended place to write it.
    </para>
   </refsect2>
  </refsect1>
@@ -1008,11 +1008,12 @@ SELECT d.* FROM distributors d;
 SELECT distributors.* FROM distributors d, distributors distributors;
 </programlisting>
     that he will actually get.  To help detect this sort of mistake,
-    PostgreSQL will warn if the implicit-<literal>FROM</literal>
-    feature is used in a <command>SELECT</command> statement that also
-    contains an explicit <literal>FROM</literal> clause.  Also, it is
-    possible to disable the implicit-<literal>FROM</literal> feature
-    by setting the <varname>ADD_MISSING_FROM</> parameter to false.
+    <productname>PostgreSQL</productname> will warn if the
+    implicit-<literal>FROM</literal> feature is used in a
+    <command>SELECT</command> statement that also contains an explicit
+    <literal>FROM</literal> clause.  Also, it is possible to disable
+    the implicit-<literal>FROM</literal> feature by setting the
+    <varname>ADD_MISSING_FROM</> parameter to false.
    </para>
   </refsect2>
 

doc/src/sgml/ref/set_constraints.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_constraints.sgml,v 1.7 2003/08/31 17:32:24 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_constraints.sgml,v 1.8 2003/09/11 21:42:20 momjian Exp $ -->
 <refentry id="SQL-SET-CONSTRAINTS">
  <refmeta>
   <refentrytitle id="SQL-SET-CONSTRAINTS-title">SET CONSTRAINTS</refentrytitle>
@@ -77,8 +77,9 @@ SET CONSTRAINTS { ALL | <replaceable class="parameter">constraint</replaceable>
 
   <para>
    This command complies with the behavior defined in the SQL
-   standard, except for the limitation that, in PostgreSQL, it only
-   applies to foreign-key constraints.
+   standard, except for the limitation that, in
+   <productname>PostgreSQL</productname>, it only applies to
+   foreign-key constraints.
   </para>
  </refsect1>
 </refentry>

doc/src/sgml/ref/set_session_auth.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_session_auth.sgml,v 1.10 2003/08/31 17:32:24 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_session_auth.sgml,v 1.11 2003/09/11 21:42:20 momjian Exp $ -->
 <refentry id="SQL-SET-SESSION-AUTHORIZATION">
  <refmeta>
   <refentrytitle id="sql-set-session-authorization-title">SET SESSION AUTHORIZATION</refentrytitle>
@@ -89,10 +89,10 @@ SELECT SESSION_USER, CURRENT_USER;
   <para>
    The SQL standard allows some other expressions to appear in place
    of the literal <replaceable>username</replaceable> which are not
-   important in practice.  <application>PostgreSQL</application>
+   important in practice.  <productname>PostgreSQL</productname>
    allows identifier syntax (<literal>"username"</literal>), which SQL
    does not.  SQL does not allow this command during a transaction;
-   <application>PostgreSQL</application> does not make this
+   <productname>PostgreSQL</productname> does not make this
    restriction because there is no reason to.  The privileges
    necessary to execute this command are left implementation-defined
    by the standard.

doc/src/sgml/ref/set_transaction.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.16 2003/09/09 18:28:53 tgl Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/ref/set_transaction.sgml,v 1.17 2003/09/11 21:42:20 momjian Exp $ -->
 <refentry id="SQL-SET-TRANSACTION">
  <refmeta>
   <refentrytitle id="SQL-SET-TRANSACTION-TITLE">SET TRANSACTION</refentrytitle>
@@ -122,7 +122,7 @@ SET default_transaction_isolation = '<replaceable>value</replaceable>'
   <para>
    Both commands are defined in the <acronym>SQL</acronym> standard.
    <literal>SERIALIZABLE</literal> is the default transaction
-   isolation level in the standard; in PostgreSQL the default is
+   isolation level in the standard; in <productname>PostgreSQL</productname> the default is
    ordinarily <literal>READ COMMITTED</literal>, but you can change it as
    described above.  <productname>PostgreSQL</productname> does not
    provide the isolation levels <literal>READ UNCOMMITTED</literal>

doc/src/sgml/ref/update.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.24 2003/08/31 17:32:24 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/update.sgml,v 1.25 2003/09/11 21:42:20 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -164,7 +164,8 @@ UPDATE weather SET temp_lo = temp_lo+1, temp_hi = temp_lo+15, prcp = DEFAULT
 
   <para>
    This command conforms to the SQL standard.  The
-   <literal>FROM</literal> clause is a PostgreSQL extension.
+   <literal>FROM</literal> clause is a
+   <productname>PostgreSQL</productname> extension.
   </para>
  </refsect1>
 </refentry>

doc/src/sgml/release.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.206 2003/08/27 03:35:35 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.207 2003/09/11 21:42:20 momjian Exp $
 -->
 
 <appendix id="release">
@@ -10,8 +10,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/release.sgml,v 1.206 2003/08/27 03:35:35 mo
 
   <para>
    Below is a subset of the changes that have gone into the
-   development branch of PostgreSQL since version 7.3.  For a complete
-   list of changes, consult the CVS logs.
+   development branch of <productname>PostgreSQL</productname> since
+   version 7.3.  For a complete list of changes, consult the CVS logs.
   </para>
 
 <!--

doc/src/sgml/rules.sgml

-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.29 2003/08/31 17:32:19 petere Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/rules.sgml,v 1.30 2003/09/11 21:42:20 momjian Exp $ -->
 
 <Chapter Id="rules">
 <Title>The Rule System</Title>
@@ -8,16 +8,17 @@
  </indexterm>
 
 <Para>
-     This chapter discusses the rule system in PostgreSQL.
-     Production rule systems are conceptually simple, but
-     there are many subtle points involved in actually using
-     them.
+     This chapter discusses the rule system in
+     <productname>PostgreSQL</productname>.  Production rule systems
+     are conceptually simple, but there are many subtle points
+     involved in actually using them.
 </Para>
 
 <Para>
      Some other database systems define active database rules, which
-     are usually stored procedures and triggers.  In PostgreSQL, these
-     can be implemented using functions and triggers as well.
+     are usually stored procedures and triggers.  In
+     <productname>PostgreSQL</productname>, these can be implemented
+     using functions and triggers as well.
 </Para>
 
 <Para>

doc/src/sgml/xfunc.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.73 2003/08/31 17:32:20 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.74 2003/09/11 21:42:20 momjian Exp $
 -->
 
  <sect1 id="xfunc">
@@ -814,15 +814,15 @@ CREATE FUNCTION square_root(double precision) RETURNS double precision
 
     <para>
      To know how to write C-language functions, you need to know how
-     PostgreSQL internally represents base data types and how they can
-     be passed to and from functions.
-     Internally, <productname>PostgreSQL</productname> regards a
-     base type as a <quote>blob of memory</quote>.   The  user-defined  
-     functions that you define over a type in turn define the 
-     way  that  <productname>PostgreSQL</productname> can operate  
-     on  it.  That is, <productname>PostgreSQL</productname> will 
-     only store and retrieve the data from disk and use  your  
-     user-defined functions to input, process, and output the data.
+     <productname>PostgreSQL</productname> internally represents base
+     data types and how they can be passed to and from functions.
+     Internally, <productname>PostgreSQL</productname> regards a base
+     type as a <quote>blob of memory</quote>.  The user-defined
+     functions that you define over a type in turn define the way that
+     <productname>PostgreSQL</productname> can operate on it.  That
+     is, <productname>PostgreSQL</productname> will only store and
+     retrieve the data from disk and use your user-defined functions
+     to input, process, and output the data.
     </para>
 
     <para>
@@ -1249,13 +1249,14 @@ CREATE FUNCTION concat_text(text, text) RETURNS text
 
     <para>
      Here, <replaceable>DIRECTORY</replaceable> stands for the
-     directory of the shared library file (for instance the PostgreSQL
-     tutorial directory, which contains the code for the examples used
-     in this section).  (Better style would be to use just
-     <literal>'funcs'</> in the <literal>AS</> clause, after having
-     added <replaceable>DIRECTORY</replaceable> to the search path.
-     In any case, we may omit the system-specific extension for a
-     shared library, commonly <literal>.so</literal> or
+     directory of the shared library file (for instance the
+     <productname>PostgreSQL</productname> tutorial directory, which
+     contains the code for the examples used in this section).
+     (Better style would be to use just <literal>'funcs'</> in the
+     <literal>AS</> clause, after having added
+     <replaceable>DIRECTORY</replaceable> to the search path.  In any
+     case, we may omit the system-specific extension for a shared
+     library, commonly <literal>.so</literal> or
      <literal>.sl</literal>.)
     </para>
 
@@ -1483,15 +1484,16 @@ concat_text(PG_FUNCTION_ARGS)
 
     <para>
      Before we turn to the more advanced topics, we should discuss
-     some coding rules for PostgreSQL C-language functions.  While it
-     may be possible to load functions written in languages other than
-     C into <productname>PostgreSQL</productname>, this is usually
-     difficult (when it is possible at all) because other languages,
-     such as C++, FORTRAN, or Pascal often do not follow the same
-     calling convention as C.  That is, other languages do not pass
-     argument and return values between functions in the same way.
-     For this reason, we will assume that your C-language functions
-     are actually written in C.
+     some coding rules for <productname>PostgreSQL</productname>
+     C-language functions.  While it may be possible to load functions
+     written in languages other than C into
+     <productname>PostgreSQL</productname>, this is usually difficult
+     (when it is possible at all) because other languages, such as
+     C++, FORTRAN, or Pascal often do not follow the same calling
+     convention as C.  That is, other languages do not pass argument
+     and return values between functions in the same way.  For this
+     reason, we will assume that your C-language functions are
+     actually written in C.
     </para>
 
     <para>