pg_dump / pg_restore with Large Objects from 32-bit to 64-bit

This is a multi-part message in MIME format.

------=_NextPart_000_0004_01CAC03C.8AB32F10
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

When migrating our Postgres databases from 32 to 64-bit systems, including
large binary objects, how well will this work?



32-bit server) pg_dump --format=c --blobs --file=backup.pg mydb



64-bit server) pg_restore -d mydb backup.pg



I'm hoping that PG's compressed custom archive format is not architecture
dependant. Thanks!


------=_NextPart_000_0004_01CAC03C.8AB32F10
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">


charset=3Dus-ascii">

Re: pg_dump / pg_restore with Large Objects from 32-bit to 64-bit

"Matt Janssen" writes:
> When migrating our Postgres databases from 32 to 64-bit systems, including
> large binary objects, how well will this work?

> 32-bit server) pg_dump --format=c --blobs --file=backup.pg mydb
> 64-bit server) pg_restore -d mydb backup.pg

Should be fine; but remember that only gets you the contents of the one
database. You may also want pg_dumpall --globals-only to transfer
role properties and such.

> I'm hoping that PG's compressed custom archive format is not architecture
> dependant. Thanks!

It is not.

regards, tom lane

--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin