From 4b7b1df8a65fc4cf3aef1c3d61f5051537107f1b Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Sat, 13 May 2006 16:19:54 +0000
Subject: [PATCH] Mention version portability of pg_dump.

---
 doc/src/sgml/ref/pg_dump.sgml | 13 ++++++++++++-
 1 file changed, 12 insertions(+), 1 deletion(-)

diff --git a/doc/src/sgml/ref/pg_dump.sgml b/doc/src/sgml/ref/pg_dump.sgml
index 9e076a4308..22540a12ae 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.84 2006/05/06 23:25:37 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dump.sgml,v 1.85 2006/05/13 16:19:54 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -645,6 +645,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">