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

diff --git a/doc/src/sgml/ref/set.sgml b/doc/src/sgml/ref/set.sgml
index 1c9bd31e1e95b24226c8d11d83dfcb4481ad8143..4ee941be37bf54a30b0f2505a87bb327abba352e 100644 (file)
--- a/doc/src/sgml/ref/set.sgml
+++ b/doc/src/sgml/ref/set.sgml
@@ -1,5 +1,5 @@
 
 
@@ -476,10 +476,10 @@ SELECT CURRENT_TIMESTAMP AS today;
    
 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
    
   
  

diff --git a/doc/src/sgml/ref/vacuum.sgml b/doc/src/sgml/ref/vacuum.sgml
index f45aaf2f13dfcb5d2bb0eb925ff58dbb596c8c65..5f7b76285fbff5391fe5dcb0b9fed170f178d464 100644 (file)
--- a/doc/src/sgml/ref/vacuum.sgml
+++ b/doc/src/sgml/ref/vacuum.sgml
@@ -1,5 +1,5 @@
 
 
@@ -186,7 +186,8 @@ INFO:  Index index: Pages 28;
    Plain VACUUM (without 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.  VACUUM
+   with normal reading and writing of the table, as an exclusive lock
+   is not obtained. VACUUM
    FULL 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