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

From Zdenek Kotala
Subject Re: Upgrading a database dump/restore
Date
Msg-id 4526628D.1030103@sun.com
Whole thread Raw
In response to Re: Upgrading a database dump/restore  (Martijn van Oosterhout <kleptog@svana.org>)
List pgsql-hackers
Martijn van Oosterhout napsal(a):
> 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"?

There are still people who are working on it :-). I'm working on catalog 
conversion prototype -> it will generate helping request early ;-).
    Zdenek



pgsql-hackers by date:

Previous
From: "Jonah H. Harris"
Date:
Subject: Re: Another idea for dealing with cmin/cmax
Next
From: Tom Lane
Date:
Subject: Re: Storing MemoryContext Pointers