Re: Upgrading a database dump/restore - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Upgrading a database dump/restore
Date
Msg-id 20061005205319.GC2482@svana.org
Whole thread Raw
In response to Re: Upgrading a database dump/restore  ("Mark Woodward" <pgsql@mohawksoft.com>)
Responses Re: Upgrading a database dump/restore  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
List pgsql-hackers
On Thu, Oct 05, 2006 at 04:39:22PM -0400, Mark Woodward wrote:
> >
> > Indeed. The main issue for me is that the dumping and replication
> > setups require at least 2x the space of one db. That's 2x the
> > hardware which equals 2x $$$. If there were some tool which modified
> > the storage while postgres is down, that would save lots of people
> > lots of money.
>
> Its time and money. Stoping a database and staring with new software is a
> lot faster than dumping the data out (disallowing updates or inserts) and
> restoring the data can take hours or days *and* twice the hardware.

In that case there should be people willing to fund the development.
There have been a few people (even in the last few weeks) who say
they're looking into it, perhaps they need a "helping hand"?

Someone got as far as handling catalog updates I beleive,

Have a nice day,
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

pgsql-hackers by date:

Previous
From: "Mark Woodward"
Date:
Subject: Re: Upgrading a database dump/restore
Next
From: Tom Lane
Date:
Subject: broken dead code in pg_lzcompress.h