aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2010-11-10 14:08:30 +0000
committerBruce Momjian <bruce@momjian.us>2010-11-10 14:08:43 +0000
commit8f742d1cdab987ba4624ad0c6aa008ced15cd87c (patch)
tree414cbc794996f7cf221add0dc783f65349c2e60e
parent7ba6e4f0e08bd7bdf4d12974ac1e37fb0459c97c (diff)
downloadpostgresql-8f742d1cdab987ba4624ad0c6aa008ced15cd87c.tar.gz
postgresql-8f742d1cdab987ba4624ad0c6aa008ced15cd87c.zip
Mention that pg_upgrade requires compatible 32/64-bit binaries.
-rw-r--r--doc/src/sgml/pgupgrade.sgml3
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 6d2cdaa335a..9081cc916ae 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -21,7 +21,8 @@
regularly added to PostgreSQL major releases, the internal data storage
format rarely changes. <application>pg_upgrade</> does its best to
make sure the old and new clusters are binary-compatible, e.g. by
- checking for compatible compile-time settings. It is important that
+ checking for compatible compile-time settings, including 32/64-bit
+ binaries. It is important that
any external modules are also binary compatible, though this cannot
be checked by <application>pg_upgrade</>.
</para>