set.patch updates an example in ref/set.sgml to have microsecond

precision.

vacuum.patch updates ref/vacuum.sgml to explicitly state that an
exclusive lock is not obtained during normal (non-FULL) vacuum.

  Rod Taylor

doc/src/sgml/ref/set.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.66 2002/10/09 04:59:38 momjian Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/set.sgml,v 1.67 2002/10/09 16:27:48 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -476,10 +476,10 @@ SELECT CURRENT_TIMESTAMP AS today;
    <screen>
 SET TIME ZONE 'Europe/Rome';
 SELECT CURRENT_TIMESTAMP AS today;
-   
-         today
-------------------------
- 1998-03-31 17:41:31+02
+
+             today             
+-------------------------------
+ 2002-10-08 05:39:35.008271+02
    </screen>
   </para>
  </refsect1>

doc/src/sgml/ref/vacuum.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.26 2002/09/21 18:32:54 petere Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/vacuum.sgml,v 1.27 2002/10/09 16:27:48 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -186,7 +186,8 @@ INFO:  Index <replaceable class="PARAMETER">index</replaceable>: Pages 28;
    Plain <command>VACUUM</command> (without <literal>FULL</>) simply reclaims
    space and makes it
    available for re-use.  This form of the command can operate in parallel
-   with normal reading and writing of the table.  <command>VACUUM
+   with normal reading and writing of the table, as an exclusive lock
+   is not obtained. <command>VACUUM
    FULL</command> does more extensive processing, including moving of tuples
    across blocks to try to compact the table to the minimum number of disk
    blocks.  This form is much slower and requires an exclusive lock on each