From: | Erik Jones <erik(at)myemma(dot)com> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | wu_zhong_min(at)vrane(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: perpetual dump/restore problem |
Date: | 2007-07-05 16:05:03 |
Message-ID: | 1294D07C-41A2-4F97-9BFF-89E309241879@myemma.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Jul 5, 2007, at 2:49 AM, Richard Huxton wrote:
> wu_zhong_min(at)vrane(dot)com wrote:
>> Dear List,
>> As many of you know every time one wants to upgrade to a major server
>> version, as I want to do now, there is a need for pg_dumpall and
>> restore. This is a huge undertaking and requires lots of testing and
>> planning. I do hope that in the future this requirement will be
>> dropped.
>
> There is currently some discussion about an upgrade tool, but there
> has been discussion before. It's not a simple problem, and it won't
> reduce the need for testing, just the dump/restore.
One shot at that would be the pg_migrator tool that Enterprise DB has
put up on pgfoundry (http://pgfoundry.org/frs/?
group_id=1000235&release_id=763). It does have it's caveats,
though, so make sure to carefully read the documentation in the
download.
Erik Jones
Software Developer | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2007-07-05 17:20:44 | Re: [pgsql-general] In memory tables/databases |
Previous Message | wu_zhong_min | 2007-07-05 15:10:01 | Re: [general] [general] perpetual dump/restore problem |