Add a note suggesting that users should use the newer version of pg_dump

to perform upgrades, and cleanup some nearby text. Patch from Robert
Treat, editorializing by Neil Conway.

diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index af06249203a19da93aea5d9ea2dddfe47281701d..f2c06c8b2af0cafcfcbf2d3a330687609d89d2a0 100644 (file)
--- a/doc/src/sgml/backup.sgml
+++ b/doc/src/sgml/backup.sgml
@@ -1,5 +1,5 @@
 
 
  Backup and Restore
@@ -950,13 +950,17 @@ restore_command = 'cp /mnt/server/archivedir/%f %p'
    storage formats. For example, releases 7.0.1, 7.1.2, and 7.2 are
    not compatible, whereas 7.1.1 and 7.1.2 are. When you update
    between compatible versions, you can simply replace the executables
-   and reuse the data area on disk. Otherwise you need to
-   back up your data and restore it on the new
-   server, using pg_dump. (There are checks in place
-   that prevent you from doing the wrong thing, so no harm can be done
-   by confusing these things.) The precise installation procedure is
-   not the subject of this section; those details are in 
-   linkend="installation">.
+   and reuse the data area on disk. Otherwise you need to back
+   up your data and restore it on the new server, using
+   pg_dump. There are checks in place that prevent you
+   from using a data area with an incompatible version of
+   PostgreSQL, so no harm can be done by
+   confusing these things. It is recommended that you use the
+   pg_dump program from the newer version of
+   PostgreSQL to take advantage of any enhancements in
+   pg_dump that may have been made. The precise
+   installation procedure is not the subject of this section; those
+   details are in .