Re: Best practice for 8.1.5 -> 8.2 migration - with big database?

From: Erik Jones <erik(at)myemma(dot)com>
To: Mason Hale <masonhale(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Best practice for 8.1.5 -> 8.2 migration - with big database?
Date: 2007-02-14 19:58:59
Message-ID: 45D36A03.5020809@myemma.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Mason Hale wrote:
>> From what I've read about postgres 8.2, upgrading from any previous
> version requires a full database dump and restore.
>
> I am working with largish database (~70GB) that I would like to
> upgrade to 8.2.
> A full database dump currently takes ~3 hrs, I expect a restore
> require a similar timeframe if not more.
>
> So, I'm fishing to see of there are alternatives to taking our
> production database down for 6+ hours do this upgrade.
Check out <a
href="http://pgfoundry.org/projects/pg-migrator/">pg_migrator</a>.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2007-02-14 20:00:16 Re: Protect PL/PGSQL source
Previous Message Ted Byers 2007-02-14 19:40:18 Re: backup database by cloning itself