I have created the attached patch which rewords the mention of
pg_upgrade in the docs. I think it is clearer and more concise. Should
we mention that people should have a recent pg_dump? If so, that should
be in the pg_upgrade man page, not here.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml
index c14ae43..123e769 100644
*** a/doc/src/sgml/backup.sgml
--- b/doc/src/sgml/backup.sgml
*************** psql -f backup postgres
*** 1565,1578 ****
<title>Other data migration methods</title>
<para>
! The <filename>contrib</> program
! <link linkend="pgupgrade"><application>pg_upgrade</application></link>
! allows an installation to be migrated in-place from one major
! <productname>PostgreSQL</> version to the next. Keep in mind that this
! method does not provide any scope for running old and new versions
! concurrently. Also, <application>pg_upgrade</application> is much less
! battle-tested than <application>pg_dump</application>, so having an
! up-to-date backup is strongly recommended in case something goes wrong.
</para>
<para>
--- 1565,1575 ----
<title>Other data migration methods</title>
<para>
! The <link linkend="pgupgrade">pg_upgrade</link> module allows an
! installation to be migrated in-place from one major
! <productname>PostgreSQL</> version to the next. Upgrades can be
! performed in minutes, though the server cannot be accessed during
! the upgrade.
</para>
<para>
--
Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
