From ca485d053b22eaf358924306c2af1b57797fd1ac Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Tue, 8 Jun 1999 16:42:10 +0000 Subject: [PATCH] Add mention of new pg_dump feature. --- doc/src/sgml/release.sgml | 17 ++++++++++++----- register.txt | 2 +- 2 files changed, 13 insertions(+), 6 deletions(-) diff --git a/doc/src/sgml/release.sgml b/doc/src/sgml/release.sgml index 44e39358e1..2e7732a089 100644 --- 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 9324cdca10..fc5db79c49 100644 --- 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. -- 2.11.0