Re: Restoring a Full Cluster on a Different Architecture (32 x 64)

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: "Rodrigo Hjort" <rodrigo(dot)hjort(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Restoring a Full Cluster on a Different Architecture (32 x 64)
Date: 2006-03-14 19:12:39
Message-ID: 36e682920603141112j598c85cara40f752a302f1f7b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/14/06, Jim C. Nasby <jnasby(at)pervasive(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-03-14 19:13:23 Re: log_duration and log_statement
Previous Message Jim C. Nasby 2006-03-14 18:58:22 Re: Restoring a Full Cluster on a Different Architecture (32 x 64)