From: Brian Hirt <bhirt@me.com>
To: Evan D. Hoffman <evandhoffman@gmail.com>
Cc: Postgresql Mailing List <pgsql-general@postgresql.org>
Subject: Re: Copying data files to new hardware?
Date: Wed, 13 Oct 2010 11:07:33 -0600
Message-ID: <B7A2CF0D-37D0-4A2D-BA80-14B1896BBF74@me.com> (raw)
In-Reply-To: <AANLkTimATVkVuvK=VJV3o7FWYg_emapxs=T0FxXHm1DJ@mail.gmail.com>
References: <7dc101b1-6596-4850-b0ce-cb3f01f51f14@n40g2000vbb.googlegroups.com>
<F55203CF-D9A5-4AEB-BAC4-511767133926@me.com>
<AANLkTimATVkVuvK=VJV3o7FWYg_emapxs=T0FxXHm1DJ@mail.gmail.com>
Yes, we've used Slony for migrating 8.2 -> 8.3 -> 8.4 and plan an using it to migrate to 9.0 in the near future. You should be able to skip releases as well like you say 8.2 -> 8.4.
You'll probably want to test out both slony and 8.4 on your development machines first and make sure everything works okay. It takes a little bit to get familiar with slony, it's not a simple program that you install and click a button to set up replication and have everything happen for you. We spent a fair amount of time writing scripts to work with slony to help support our processes.
On Oct 13, 2010, at 10:59 AM, Evan D. Hoffman wrote:
> Thanks, Brian & Jaime. Regarding Slony, would that allow for
> migration to a new version as well - i.e. moving from 8.2 on the old
> machine to 8.4 on the new machine via Slony with minimal downtime?
>
> The Slony method is one I hadn't considered. Since our database is so
> large, even a direct file copy would require some downtime (since we'd
> need to stop the DB before beginning the copy). Slony would probably
> let us cut the downtime from hours to minutes (dump & restore for us
> has historically taken days).
>
> Thanks again,
> Evan
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: bhirt@me.com, evandhoffman@gmail.com, pgsql-general@postgresql.org
Subject: Re: Copying data files to new hardware?
In-Reply-To: <B7A2CF0D-37D0-4A2D-BA80-14B1896BBF74@me.com>
* 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