Re: Upgrading a database dump/restore

From: "Mark Woodward" <pgsql(at)mohawksoft(dot)com>
To: "Andrew Dunstan" <andrew(at)dunslane(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Upgrading a database dump/restore
Date: 2006-10-05 20:08:37
Message-ID: 17994.24.91.171.78.1160078917.squirrel@mail.mohawksoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> Mark Woodward wrote:
>> I am currently building a project that will have a huge number of
>> records,
>> 1/2tb of data. I can't see how I would ever be able to upgrade
>> PostgreSQL
>> on this system.
>>
>>
>
> Slony will help you upgrade (and downgrade, for that matter) with no
> downtime at all, pretty much. Of course, you do need double the
> resources ....
>
> You other suggestion of setting the on disk format in high viscosity
> jello, if not in concrete, seems doomed to failure. Cool features that
> you and other people want occasionally rely on format changes.

I disagree with the "all or nothing" attitude, I'm generally a pragmatist.
It is unreasonable to expect that things will never change, by the same
token, never attempting to standardize or enforce some level of stability
is equally unreasonable.

From an enterprise DB perspective, a d/r of a database is a HUGE process
and one that isn't taken lightly.

I just think that an amount of restraint in this area would pay off well.

>
> Of course, you don't have to upgrade every release. Many people
> (including me) don't.
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message AgentM 2006-10-05 20:21:47 Re: Upgrading a database dump/restore
Previous Message Mark Wong 2006-10-05 19:58:45 continuing daily testing of dbt2 against postgresql