Re: Restoring a Full Cluster on a Different Architecture (32 x 64) - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: Restoring a Full Cluster on a Different Architecture (32 x 64)
Date
Msg-id 36e682920603141112j598c85cara40f752a302f1f7b@mail.gmail.com
Whole thread Raw
In response to Re: Restoring a Full Cluster on a Different Architecture (32 x 64)  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: Restoring a Full Cluster on a Different Architecture (32 x 64)  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
On 3/14/06, Jim C. Nasby <jnasby@pervasive.com> wrote:
Setting up Slony might be another option; you'd essentially be following
the procedure used to speed up a PostgreSQL upgrade that would normally
require a dump/reload.

If you need to do this on a continuing basis, Slony is the best way to go.  If it's a one-time shot, I'd just pipe pg_dump to a psql that's connected to PostgreSQL on your 32-bit system.

--
Jonah H. Harris, Database Internals Architect
EnterpriseDB Corporation
732.331.1324

pgsql-hackers by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Restoring a Full Cluster on a Different Architecture (32 x 64)
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Restoring a Full Cluster on a Different Architecture (32 x 64)