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/ref/copy.sgml

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,4 +1,4 @@
-<!-- $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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,5 +1,5 @@
 <!--
-$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

@@ -1,4 +1,4 @@
-<!-- $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

@@ -1,4 +1,4 @@
-<!-- $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

@@ -1,4 +1,4 @@
-<!-- $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

@@ -1,5 +1,5 @@
 <!--
-$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>