More minor updates and copy-editing.

doc/src/sgml/ref/ipcclean.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/ipcclean.sgml,v 1.10 2003/11/29 19:51:39 pgsql Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/ipcclean.sgml,v 1.11 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -12,7 +12,7 @@ PostgreSQL documentation
 
  <refnamediv>
   <refname>ipcclean</refname>
-  <refpurpose>remove shared memory and semaphores from an aborted <productname>PostgreSQL</productname> server</refpurpose>
+  <refpurpose>remove shared memory and semaphores from a failed <productname>PostgreSQL</productname> server</refpurpose>
  </refnamediv>
 
  <indexterm zone="app-ipcclean">
@@ -59,10 +59,11 @@ PostgreSQL documentation
   </para>
 
   <para>
-   The script makes assumption about the format of output of the
+   The script makes assumptions about the output format of the
    <command>ipcs</command>
    utility which may not be true across different operating systems.
-   Therefore, it may not work on your particular OS.
+   Therefore, it may not work on your particular OS.  It's wise to
+   look at the script before trying it.
   </para>
  </refsect1>
 

doc/src/sgml/ref/pg_config-ref.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.18 2004/08/02 12:34:14 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_config-ref.sgml,v 1.19 2005/01/04 03:58:16 tgl Exp $ -->
 
 <refentry id="app-pgconfig">
  <refmeta>
@@ -153,7 +153,7 @@
   </para>
 
   <para>
-   In releases prior to <productname>PostgreSQL</> 7.1, before the
+   In releases prior to <productname>PostgreSQL</> 7.1, before
    <command>pg_config</command> came to be, a method for finding the
    equivalent configuration information did not exist.
   </para>

doc/src/sgml/ref/pg_dump.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.74 2004/10/21 22:48:54 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.75 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -45,21 +45,24 @@ PostgreSQL documentation
   </para>
 
   <para>
-   Dumps can be output in script or archive file formats. The script
-   files are in plain-text format and contain the SQL commands required
+   Dumps can be output in script or archive file formats. Script
+   dumps are plain-text files containing the SQL commands required
    to reconstruct the database to the state it was in at the time it was
-   saved. To restore these scripts, use <xref linkend="app-psql">. They
+   saved. To restore from such a script, feed it to <xref
+   linkend="app-psql">. Script files
    can be used to reconstruct the database even on other machines and
-   other architectures, with some modifications even on other SQL
+   other architectures; with some modifications even on other SQL
    database products.
   </para>
 
   <para>
-   The alternative archive file formats that are meant to be used with
-   <xref linkend="app-pgrestore"> to rebuild the database, and they also
+   The alternative archive file formats must be used with
+   <xref linkend="app-pgrestore"> to rebuild the database.  They
    allow <application>pg_restore</application> to be selective about
    what is restored, or even to reorder the items prior to being
-   restored. The archive files are also designed to be portable across
+   restored.  The archive formats also allow saving and restoring
+   <quote>large objects</>, which is not possible in a script dump.
+   The archive files are also designed to be portable across
    architectures.
   </para>
 
@@ -76,7 +79,7 @@ PostgreSQL documentation
    by default. The <application>tar</application> format
    (<option>-Ft</option>) is not compressed and it is not possible to
    reorder data when loading, but it is otherwise quite flexible;
-   moreover, it can be manipulated with other tools such as
+   moreover, it can be manipulated with standard Unix tools such as
    <command>tar</command>.
   </para>
 
@@ -92,7 +95,8 @@ PostgreSQL documentation
   <title>Options</title>
 
   <para>
-   The following command-line options are used to control the output format.
+    The following command-line options control the content and
+    format of the output.
 
     <variablelist>
      <varlistentry>
@@ -112,12 +116,12 @@ PostgreSQL documentation
       <term><option>--data-only</></term>
       <listitem>
        <para>
-	Dump only the data, not the object definitions (schema)
+        Dump only the data, not the schema (data definitions).
        </para>
 
        <para>
         This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
+        the archive formats, you may specify the option when you
         call <command>pg_restore</command>.
        </para>
       </listitem>
@@ -128,7 +132,8 @@ PostgreSQL documentation
       <term><option>--blobs</></term>
       <listitem>
        <para>
- 	Include large objects in dump.
+        Include large objects in the dump.  A non-text output format
+        must be selected.
        </para>
       </listitem>
      </varlistentry>
@@ -144,7 +149,7 @@ PostgreSQL documentation
 
        <para>
         This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
+        the archive formats, you may specify the option when you
         call <command>pg_restore</command>.
        </para>
       </listitem>
@@ -163,7 +168,7 @@ PostgreSQL documentation
 
        <para>
         This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
+        the archive formats, you may specify the option when you
         call <command>pg_restore</command>.
        </para>
       </listitem>
@@ -308,8 +313,9 @@ PostgreSQL documentation
       <term><option>--oids</></term>
       <listitem>
        <para>
-	Dump object identifiers (<acronym>OID</acronym>s) for every
-	table.  Use this option if your application references the <acronym>OID</>
+        Dump object identifiers (<acronym>OID</acronym>s) as part of the
+        data for every table.  Use this option if your application references
+        the <acronym>OID</>
         columns in some way (e.g., in a foreign key constraint).
         Otherwise, this option should not be used.
        </para>
@@ -324,6 +330,7 @@ PostgreSQL documentation
         Do not output commands to set
         ownership of objects to match the original database.
         By default, <application>pg_dump</application> issues
+        <command>ALTER OWNER</> or 
         <command>SET SESSION AUTHORIZATION</command>
         statements to set ownership of created database objects.
         These statements
@@ -335,7 +342,7 @@ PostgreSQL documentation
 
        <para>
         This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
+        the archive formats, you may specify the option when you
         call <command>pg_restore</command>.
        </para>
       </listitem>
@@ -456,7 +463,7 @@ PostgreSQL documentation
 
        <para>
         This option is only meaningful for the plain-text format.  For
-        the other formats, you may specify the option when you
+        the archive formats, you may specify the option when you
         call <command>pg_restore</command>.
        </para>
       </listitem>
@@ -619,7 +626,7 @@ CREATE DATABASE foo WITH TEMPLATE template0;
   <para>
    Members of tar archives are limited to a size less than 8 GB.
    (This is an inherent limitation of the tar file format.)  Therefore
-   this format cannot be used if the textual representation of a table
+   this format cannot be used if the textual representation of any one table
    exceeds that size.  The total size of a tar archive and any of the
    other output formats is not limited, except possibly by the
    operating system.

doc/src/sgml/ref/pg_dumpall.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.46 2004/07/19 21:39:46 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.47 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -68,7 +68,8 @@ PostgreSQL documentation
 
   <para>
   <application>pg_dumpall</application> needs to connect several
-  times to the <productname>PostgreSQL</productname> server and might be asking for
+  times to the <productname>PostgreSQL</productname> server (once per
+  database).  If you use password authentication it is likely to ask for
   a password each time. It is convenient to have a
   <filename>$HOME/.pgpass</> file in such cases.
   </para>
@@ -79,7 +80,7 @@ PostgreSQL documentation
   <title>Options</title>
 
    <para>
-    The following command-line options are used to control the content and
+    The following command-line options control the content and
     format of the output.
 
     <variablelist>
@@ -110,9 +111,11 @@ PostgreSQL documentation
       <listitem>
        <para>
         Dump data as <command>INSERT</command> commands (rather
-	than <command>COPY</command>). This will make restoration very
-	slow, but it makes the output more portable to other SQL database
-	management systems.
+        than <command>COPY</command>).  This will make restoration very slow;
+        it is mainly useful for making dumps that can be loaded into
+        non-<productname>PostgreSQL</productname> databases.  Note that
+        the restore may fail altogether if you have rearranged column order.
+        The <option>-D</option> option is safer, though even slower.
        </para>
       </listitem>
      </varlistentry>
@@ -127,8 +130,9 @@ PostgreSQL documentation
         column names (<literal>INSERT INTO
         <replaceable>table</replaceable>
         (<replaceable>column</replaceable>, ...) VALUES
-	...</literal>).  This will make restoration very slow,
-	but it is necessary if you desire to rearrange column ordering.
+        ...</literal>).  This will make restoration very slow; it is mainly
+        useful for making dumps that can be loaded into
+        non-<productname>PostgreSQL</productname> databases.
        </para>
       </listitem>
      </varlistentry>
@@ -168,8 +172,9 @@ PostgreSQL documentation
       <term><option>--oids</></term>
       <listitem>
        <para>
-	Dump object identifiers (<acronym>OID</acronym>s) for every
-	table.  Use this option if your application references the OID
+        Dump object identifiers (<acronym>OID</acronym>s) as part of the
+        data for every table.  Use this option if your application references
+        the <acronym>OID</>
         columns in some way (e.g., in a foreign key constraint).
         Otherwise, this option should not be used.
        </para>
@@ -184,6 +189,7 @@ PostgreSQL documentation
         Do not output commands to set
         ownership of objects to match the original database.
         By default, <application>pg_dumpall</application> issues
+        <command>ALTER OWNER</> or 
         <command>SET SESSION AUTHORIZATION</command>
         statements to set ownership of created schema elements.
         These statements
@@ -200,7 +206,7 @@ PostgreSQL documentation
       <term><option>--schema-only</option></term>
       <listitem>
        <para>
-	Dump only the schema (data definitions), no data.
+        Dump only the object definitions (schema), not data.
        </para>
       </listitem>
      </varlistentry>

doc/src/sgml/ref/pg_restore.sgml

-<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.48 2004/08/20 04:20:22 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ref/pg_restore.sgml,v 1.49 2005/01/04 03:58:16 tgl Exp $ -->
 
 <refentry id="APP-PGRESTORE">
  <refmeta>
@@ -247,6 +247,7 @@
         Do not output commands to set
         ownership of objects to match the original database.
         By default, <application>pg_restore</application> issues
+        <command>ALTER OWNER</> or 
         <command>SET SESSION AUTHORIZATION</command>
         statements to set ownership of created schema elements.
         These statements will fail unless the initial connection to the

doc/src/sgml/ref/select.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.78 2004/11/27 21:27:07 petere Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/select.sgml,v 1.79 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -81,6 +81,16 @@ where <replaceable class="parameter">from_item</replaceable> can be one of:
      </para>
     </listitem>
 
+    <listitem>
+     <para>
+      The actual output rows are computed using the
+      <command>SELECT</command> output expressions for each selected
+      row.  (See
+      <xref linkend="sql-select-list" endterm="sql-select-list-title">
+      below.)
+     </para>
+    </listitem>
+
     <listitem>
      <para>
       Using the operators <literal>UNION</literal>,
@@ -100,16 +110,6 @@ where <replaceable class="parameter">from_item</replaceable> can be one of:
      </para>
     </listitem>
 
-    <listitem>
-     <para>
-      The actual output rows are computed using the
-      <command>SELECT</command> output expressions for each selected
-      row.  (See
-      <xref linkend="sql-select-list" endterm="sql-select-list-title">
-      below.)
-     </para>
-    </listitem>
-
     <listitem>
      <para>
       If the <literal>ORDER BY</literal> clause is specified, the
@@ -454,6 +454,34 @@ HAVING <replaceable class="parameter">condition</replaceable>
    </para>
   </refsect2>
 
+  <refsect2 id="sql-select-list">
+   <title id="sql-select-list-title"><command>SELECT</command> List</title>
+
+   <para>
+    The <command>SELECT</command> list (between the key words
+    <literal>SELECT</> and <literal>FROM</>) specifies expressions
+    that form the output rows of the <command>SELECT</command>
+    statement.  The expressions can (and usually do) refer to columns
+    computed in the <literal>FROM</> clause.  Using the clause
+    <literal>AS <replaceable
+    class="parameter">output_name</replaceable></literal>, another
+    name can be specified for an output column.  This name is
+    primarily used to label the column for display.  It can also be
+    used to refer to the column's value in <literal>ORDER BY</> and
+    <literal>GROUP BY</> clauses, but not in the <literal>WHERE</> or
+    <literal>HAVING</> clauses; there you must write out the
+    expression instead.
+   </para>
+
+   <para>
+    Instead of an expression, <literal>*</literal> can be written in
+    the output list as a shorthand for all the columns of the selected
+    rows.  Also, one can write <literal><replaceable
+    class="parameter">table_name</replaceable>.*</literal> as a
+    shorthand for the columns coming from just that table.
+   </para>
+  </refsect2>
+  
   <refsect2 id="SQL-UNION">
    <title id="sql-union-title"><literal>UNION</literal> Clause</title>
 
@@ -486,7 +514,9 @@ HAVING <replaceable class="parameter">condition</replaceable>
    <para>
     The result of <literal>UNION</> does not contain any duplicate
     rows unless the <literal>ALL</> option is specified.
-    <literal>ALL</> prevents elimination of duplicates.
+    <literal>ALL</> prevents elimination of duplicates.  (Therefore,
+    <literal>UNION ALL</> is usually significantly quicker than
+    <literal>UNION</>; use <literal>ALL</> when you can.)
    </para>
     
    <para>
@@ -524,9 +554,9 @@ HAVING <replaceable class="parameter">condition</replaceable>
    <para>
     The result of <literal>INTERSECT</literal> does not contain any
     duplicate rows unless the <literal>ALL</> option is specified.
-    With <literal>ALL</>, a row that has m duplicates in the left
-    table and n duplicates in the right table will appear min(m,n)
-    times in the result set.
+    With <literal>ALL</>, a row that has <replaceable>m</> duplicates in the
+    left table and <replaceable>n</> duplicates in the right table will appear
+    min(<replaceable>m</>,<replaceable>n</>) times in the result set.
    </para>
     
    <para>
@@ -538,6 +568,11 @@ HAVING <replaceable class="parameter">condition</replaceable>
     C</literal> will be read as <literal>A UNION (B INTERSECT
     C)</literal>.
    </para>
+    
+   <para>
+    Currently, <literal>FOR UPDATE</> may not be specified either for
+    an <literal>INTERSECT</> result or for any input of an <literal>INTERSECT</>.
+   </para>
   </refsect2>
 
   <refsect2 id="SQL-EXCEPT">
@@ -562,9 +597,9 @@ HAVING <replaceable class="parameter">condition</replaceable>
    <para>
     The result of <literal>EXCEPT</literal> does not contain any
     duplicate rows unless the <literal>ALL</> option is specified.
-    With <literal>ALL</>, a row that has m duplicates in the left
-    table and n duplicates in the right table will appear max(m-n,0)
-    times in the result set.
+    With <literal>ALL</>, a row that has <replaceable>m</> duplicates in the
+    left table and <replaceable>n</> duplicates in the right table will appear
+    max(<replaceable>m</>-<replaceable>n</>,0) times in the result set.
    </para>
     
    <para>
@@ -573,33 +608,10 @@ HAVING <replaceable class="parameter">condition</replaceable>
     unless parentheses dictate otherwise.  <literal>EXCEPT</> binds at
     the same level as <literal>UNION</>.
    </para>
-  </refsect2>
-
-  <refsect2 id="sql-select-list">
-   <title id="sql-select-list-title"><command>SELECT</command> List</title>
     
    <para>
-    The <command>SELECT</command> list (between the key words
-    <literal>SELECT</> and <literal>FROM</>) specifies expressions
-    that form the output rows of the <command>SELECT</command>
-    statement.  The expressions can (and usually do) refer to columns
-    computed in the <literal>FROM</> clause.  Using the clause
-    <literal>AS <replaceable
-    class="parameter">output_name</replaceable></literal>, another
-    name can be specified for an output column.  This name is
-    primarily used to label the column for display.  It can also be
-    used to refer to the column's value in <literal>ORDER BY</> and
-    <literal>GROUP BY</> clauses, but not in the <literal>WHERE</> or
-    <literal>HAVING</> clauses; there you must write out the
-    expression instead.
-   </para>
-
-   <para>
-    Instead of an expression, <literal>*</literal> can be written in
-    the output list as a shorthand for all the columns of the selected
-    rows.  Also, one can write <literal><replaceable
-    class="parameter">table_name</replaceable>.*</literal> as a
-    shorthand for the columns coming from just that table.
+    Currently, <literal>FOR UPDATE</> may not be specified either for
+    an <literal>EXCEPT</> result or for any input of an <literal>EXCEPT</>.
    </para>
   </refsect2>
 
@@ -707,7 +719,7 @@ OFFSET <replaceable class="parameter">start</replaceable>
     When using <literal>LIMIT</>, it is a good idea to use an
     <literal>ORDER BY</> clause that constrains the result rows into a
     unique order.  Otherwise you will get an unpredictable subset of
-    the query's rows---you may be asking for the tenth through
+    the query's rows &mdash; you may be asking for the tenth through
     twentieth rows, but tenth through twentieth in what ordering?  You
     don't know what ordering unless you specify <literal>ORDER BY</>.
    </para>

doc/src/sgml/ref/select_into.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/select_into.sgml,v 1.31 2004/09/26 23:48:07 neilc Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/select_into.sgml,v 1.32 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -95,12 +95,8 @@ SELECT [ ALL | DISTINCT [ ON ( <replaceable class="PARAMETER">expression</replac
 
   <para>
    Prior to <productname>PostgreSQL</> 8.0, the table created by
-   <command>SELECT INTO</command> always included OIDs. Furthermore,
-   these OIDs were newly generated: they were distinct from the OIDs
-   of any of the rows in the source tables of the <command>SELECT
-   INTO</command> statement. Therefore, if <command>SELECT
-   INTO</command> was frequently executed, the OID counter would be
-   rapidly incremented. As of <productname>PostgreSQL</> 8.0, the
+   <command>SELECT INTO</command> always included OIDs.
+   As of <productname>PostgreSQL</> 8.0, the
    inclusion of OIDs in the table created by <command>SELECT
    INTO</command> is controlled by the
    <xref linkend="guc-default-with-oids"> configuration variable. This

doc/src/sgml/ref/show.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/show.sgml,v 1.36 2004/08/03 20:32:32 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/show.sgml,v 1.37 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -118,7 +118,7 @@ SHOW ALL
     <term><literal>ALL</literal></term>
     <listitem>
      <para>
-      Show the values of all configurations parameters.
+      Show the values of all configuration parameters.
      </para>
     </listitem>
    </varlistentry>
@@ -165,16 +165,16 @@ SHOW geqo;
 <programlisting>
 SHOW ALL;
               name              |                     setting
--------------------------------+---------------------------------------
+--------------------------------+----------------------------------------------
+ add_missing_from               | on
+ archive_command                | unset
  australian_timezones           | off
- authentication_timeout        | 60
- checkpoint_segments           | 3
     .
     .
     .
- wal_debug                     | off
- wal_sync_method               | fdatasync
-(94 rows)
+ work_mem                       | 1024
+ zero_damaged_pages             | off
+(140 rows)
 </programlisting>
   </para>
  </refsect1>
@@ -193,6 +193,7 @@ SHOW ALL;
 
   <simplelist type="inline">
    <member><xref linkend="SQL-SET" endterm="SQL-SET-title"></member>
+   <member><xref linkend="SQL-RESET" endterm="SQL-RESET-title"></member>
   </simplelist>
  </refsect1>
 

doc/src/sgml/ref/update.sgml

 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/update.sgml,v 1.30 2004/08/08 01:48:31 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/update.sgml,v 1.31 2005/01/04 03:58:16 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -150,6 +150,26 @@ UPDATE <replaceable class="parameter">count</replaceable>
   </para>
  </refsect1>
 
+ <refsect1>
+  <title>Notes</title>
+
+  <para>
+   When joining the target table to other tables using a <replaceable
+   class="PARAMETER">fromlist</replaceable>, be careful that the join
+   produces at most one output row for each row to be modified.  In
+   other words, a target row mustn't join to more than one row from
+   the other table(s).  If it does, then only one of the join rows
+   will be used to update the target row, but which one will be used
+   is not readily predictable.
+  </para>
+
+  <para>
+   Because of this indeterminancy, referencing other tables only within
+   sub-selects is safer, though often harder to read and slower than
+   using a join.
+  </para>
+ </refsect1>
+
  <refsect1>
   <title>Examples</title>