From 1817706fbabde7ab0369564f054527e29e9be2b8 Mon Sep 17 00:00:00 2001 From: Neil Conway Date: Thu, 30 Sep 2004 10:30:10 +0000 Subject: [PATCH] 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. --- doc/src/sgml/backup.sgml | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index af06249203..f2c06c8b2a 100644 --- 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 . + 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 . -- 2.40.0