Re: Restoring a Full Cluster on a Different Architecture (32 x 64)
От
Jonah H. Harris
Тема
Re: Restoring a Full Cluster on a Different Architecture (32 x 64)
Дата
Msg-id
36e682920603141112j598c85cara40f752a302f1f7b@mail.gmail.com
Ответ на
Список
Дерево обсуждения
Restoring a Full Cluster on a Different Architecture (32 x 64) "Rodrigo Hjort" <rodrigo.hjort@gmail.com>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) Martijn van Oosterhout <kleptog@svana.org>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) "Jonah H. Harris" <jonah.harris@gmail.com>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) "Jim C. Nasby" <jnasby@pervasive.com>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) "Jonah H. Harris" <jonah.harris@gmail.com>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) "Jim C. Nasby" <jnasby@pervasive.com>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) "Rodrigo Hjort" <rodrigo.hjort@gmail.com>
Re: Restoring a Full Cluster on a Different Architecture (32 x 64) Greg Stark <gsstark@mit.edu>
On 3/14/06, Jim C. Nasby <jnasby@pervasive.com> wrote:
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
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 по дате отправления
От: Jim C. Nasby
Дата:
От: Jim C. Nasby
Дата:
