From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 13 May 2006 16:20:21 +0000 (+0000)
Subject: Mention version portability of pg_dump.
X-Git-Tag: REL8_1_4~15
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=dfc2fc2522209075ad829bcd196e19e5c851bc24;p=thirdparty%2Fpostgresql.git

Mention version portability of pg_dump.
---

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 7ee043d9ef7..f46a115a726 100644
--- a/doc/src/sgml/ref/pg_dump.sgml
+++ b/doc/src/sgml/ref/pg_dump.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.81.2.1 2006/04/15 18:11:48 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.81.2.2 2006/05/13 16:20:21 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -642,6 +642,17 @@ CREATE DATABASE foo WITH TEMPLATE template0;
    ensure good performance.
   </para>
 
+  <para>
+   Because <application>pg_dump</application> is used to tranfer data
+   to newer versions of <productname>PostgreSQL</>, the output of
+   <application>pg_dump</application> can be loaded into
+   newer versions of <productname>PostgreSQL</>.  It also can read older
+   <productname>PostgreSQL</> databases.  However, it usually cannot
+   read newer <productname>PostgreSQL</> databases or produce dump output
+   that can be loaded into older database versions.  To do this, manual
+   editing of the dump file might be required.
+  </para>
+
  </refsect1>
 
  <refsect1 id="pg-dump-examples">