From: Guillaume Lelarge <guillaume@lelarge.info>
To: Greg Spiegelberg <gspiegelberg@gmail.com>
Cc: [ADMIN] <pgsql-admin@postgresql.org>
Subject: Re: 32-bit to 64-bit migration options
Date: Fri, 10 Feb 2012 16:14:06 +0100
Message-ID: <1328886846.2155.39.camel@localhost.localdomain> (raw)
In-Reply-To: <CAEtnbpXugYOAOAup6LxPz3PCPKM=r+jWKSrmXCxN5ELFHNth0Q@mail.gmail.com>
References: <CAEtnbpXugYOAOAup6LxPz3PCPKM=r+jWKSrmXCxN5ELFHNth0Q@mail.gmail.com>
On Fri, 2012-02-10 at 07:45 -0700, Greg Spiegelberg wrote:
> All,
>
> I'm planning a migration for a customer with a PostgreSQL 8.4 database
> cluster running CentOS 4.8 32-bit. The target platform is CentOS 6.2
> 64-bit and will be running PostgreSQL 8.4 (our application delivers and
> supports 8.4, don't bother bringing up 9.x). If this were a small database
> cluster I wouldn't worry about it however the 8.4 database cluster is about
> 900 GB right now. The documented and proper way to move this data is via a
> dump-restore however I'm not sure my customer wants days or potentially
> weeks of downtime so I'm searching for options.
>
> Option 1: dump-restore
> I've performed a handful of these for other customers and even the 100 GB
> database cluster using the network transfer method "pg_dumpall | ssh target
> -c 'cat - | psql postgres'" can be slow as in 8+ hours.
>
Right.
> Option 2: Slony-I
> Is Slony-I an alternative when moving data from 32-bit to 64-bit?
>
Yes, absolutely.
> Option 3: pg_upgrade
> Is this an option? Remember, I'm going from 8.4 32-bit to 8.4 64-bit.
>
No because of the 32/64 bit change.
> Option 4: PITR
> I believe this is not a possibility because of the bit-ness change but I'm
> listing anyways in case I'm mistaken.
>
No because of the 32/64 bit change.
> Did I miss anything?
>
Well, you can also use Londiste, and probably Bucardo to do this. But I
guess they are your only options with Slony.
--
Guillaume
http://blog.guillaume.lelarge.infohttp://www.dalibo.com
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: guillaume@lelarge.info, gspiegelberg@gmail.com
Subject: Re: 32-bit to 64-bit migration options
In-Reply-To: <1328886846.2155.39.camel@localhost.localdomain>
* 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