From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | Mark Woodward <pgsql(at)mohawksoft(dot)com>, AgentM <agentm(at)themactionfaction(dot)com>, PostgreSQL-development hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Upgrading a database dump/restore |
Date: | 2006-10-06 14:05:01 |
Message-ID: | 4526628D.1030103@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-10-06 14:23:47 | Re: Storing MemoryContext Pointers |
Previous Message | Jonah H. Harris | 2006-10-06 13:39:04 | Re: Another idea for dealing with cmin/cmax |