diff options
| author | Bruce Momjian <bruce@momjian.us> | 2010-11-10 14:33:37 +0000 |
|---|---|---|
| committer | Bruce Momjian <bruce@momjian.us> | 2010-11-10 14:33:37 +0000 |
| commit | ad2a292dc39cf160e54bcf5088d2106a15950771 (patch) | |
| tree | 3c8483afdb8d13c9623cbc3de0df556b12472652 | |
| parent | 244cc39d854a10b782840473678a2d40fd42cc06 (diff) | |
Mention that pg_upgrade requires compatible 32/64-bit binaries.
| -rw-r--r-- | doc/src/sgml/pgupgrade.sgml | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index 0d51ae48321..9f6f5db5d0b 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> |