Re: Upgrading a database dump/restore

From: "Mark Woodward" <pgsql(at)mohawksoft(dot)com>
To: "AgentM" <agentm(at)themactionfaction(dot)com>
Cc: "PostgreSQL-development hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Upgrading a database dump/restore
Date: 2006-10-05 20:39:22
Message-ID: 18402.24.91.171.78.1160080762.squirrel@mail.mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> 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 response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-10-05 20:53:19 Re: Upgrading a database dump/restore
Previous Message AgentM 2006-10-05 20:21:47 Re: Upgrading a database dump/restore