Add mention of new pg_dump feature.

diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml
index 44e39358e11c7beb7671107573f1a0151f9e099d..2e7732a08999b5764a1377fdb8cee6097ca8d473 100644 (file)
--- a/doc/src/sgml/release.sgml
+++ b/doc/src/sgml/release.sgml
@@ -11,7 +11,7 @@
 Momjian
 
 
-1998-06-01
+1998-06-09
 
 -->
 
@@ -42,8 +42,12 @@
    system.  This is all performed without having to allocate a lock for
    every row like traditional database systems.  So, basically, we no
    longer are restricted by simple table-level locking;
-   we have something better than row-level
-   locking.
+   we have something better than row-level locking.
+       
+       
+   Another big benefit of MVCC is that pg_dump
+   can now generate consistent backups of live, active databases, without
+   blocking active transactions.
        
       
      
@@ -154,10 +158,12 @@
     Migration to v6.5
 
     
-     A dump/restore using pg_dump 
-     or pg_dumpall
+     A dump/restore using pg_dump
      is required for those wishing to migrate data from any
      previous release of Postgres.
+     pg_upgrade can not
+     be used to upgrade to this release because the on-disk structure
+     of the tables has changed compared to previous releases.
     
 
     
@@ -365,6 +371,7 @@ fix for large object memory leakage, fix for pg_dumping(Tom)
 INET type now respects netmask for comparisons
 Make VACUUM ANALYZE only use a readlock(Vadim)
 Allow VIEWs on UNIONS(Jan)
+pg_dump now can generate consistent snapshots on active databases(Vadim)
 
 Source Tree Changes
 -------------------

diff --git a/register.txt b/register.txt
index 9324cdca108ddd5ba64b4ccdd03ecc751cf43e40..fc5db79c49f227c17e138ce3daf247534349fb54 100644 (file)
--- a/register.txt
+++ b/register.txt
@@ -1,6 +1,6 @@
 
 
-(1999-05-01)
+(1999-06-09)
 PostgreSQL has a Web site at http://www.postgresql.org/ which carries details
 on the latest release, upcoming features, and other information to make your
 work or play with PostgreSQL more productive.