From: Paul Smith <paul@pscs.co.uk>
To: pgsql-admin@lists.postgresql.org
Subject: Using pg_upgrade to change from 32 to 64 bit.
Date: Thu, 11 Mar 2021 10:34:42 +0000
Message-ID: <33cc9b29-b14e-583e-88eb-32bc4006cc9d@pscs.co.uk> (raw)
Hi, we've been using 32 bit PostgreSQL 9.5 on Windows and are seeing how
we could upgrade to v13 64 bit.
As far as I can see from the documentation and other discussion on the
Internet, the only way to do this is to do a pg_dump and pg_restore,
which could take a while with a large database.
Just "for kicks" I decided to try to use pg_upgrade to do it (on a test
database). The documentation seems to suggest that it won't work
"pg_upgradedoes its best to make sure the old and new clusters are
binary-compatible, e.g., by checking for compatible compile-time
settings, *including 32/64-bit binaries*."
To my surprise, it seemed to work absolutely fine. I can start the new
64 bit cluster, and a quick check shows everything working OK.
Is this to be expected? Was it a fluke? I'd expect it to refuse to work
rather than claim to work and give me a broken database.
--
Paul
Paul Smith Computer Services
support@pscs.co.uk - 01484 855800
--
Paul Smith Computer Services
Tel: 01484 855800
Vat No: GB 685 6987 53
Sign up for news & updates at http://www.pscs.co.uk/go/subscribe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: paul@pscs.co.uk, pgsql-admin@lists.postgresql.org
Subject: Re: Using pg_upgrade to change from 32 to 64 bit.
In-Reply-To: <33cc9b29-b14e-583e-88eb-32bc4006cc9d@pscs.co.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox