Arturas Mazeika wrote:
> On 11/10/2010 05:32 AM, Tom Lane wrote:
> > Bruce Momjian<br...@momjian.us> writes:
> >
> >>> On 10/30/2010 7:33 PM, Dave Page wrote:
> >>>
> >>>> upgrade from a 32bit 8.3 server to a 64 bit 9.0 server, which isn't
> >>>> going to work without a dump/restore. With pg_upgrade, the two builds
> >>>> need to be from the same platform, same word size, and have the same
> >>>> configuration for certain settings like integer_datetimes.
> >>>>
> >> Can anyone suggest a way pg_upgrade could detect an upgrade from a
> >> 32-bit to 64-bit cpu and throw an error?
> >>
> > Surely it does that already, as a result of comparing pg_control
> > contents.
> >
>
> The HTML manual might need an update or a small clarification too.
> Currently, it does not seem that the manual explicitly states that
> ``pg_upgrade is not applicable in upgrading 32bit systems to 64bit
> ones''. A good place to write such a sentence would be at the beginning
> of [1], at the intro of F.32. pg_upgrade. Maybe the documentation
> already implicitly states that in F.32.4. Limitations in Migrating from
> PostgreSQL 8.3 section of [1] by this description:
>
> ``For Windows users, note that due to different integer datetimes
> settings used by the one-click installer and the MSI installer, it is
> only possible to upgrade from version 8.3 of the one-click distribution
> to version 8.4 or later of the one-click distribution. It is not
> possible to upgrade from the MSI installer to the one-click installer.''
>
> Unfortunately, I could not understand in full detail the above.
>
> Thanks,
> arturas
>
> [1] http://www.postgresql.org/docs/9.0/static/pgupgrade.html
I have added a mention about 32/64-bit isssues to the pg_upgrade manual
page, attached.
--
Bruce Momjian <br...@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
commit 8f742d1cdab987ba4624ad0c6aa008ced15cd87c
Author: Bruce Momjian <br...@momjian.us>
Date: Wed Nov 10 14:08:30 2010 +0000
Mention that pg_upgrade requires compatible 32/64-bit binaries.
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index 6d2cdaa..9081cc9 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>
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
