Re: Why dump/restore to upgrade? - Mailing list pgsql-hackers

From teg@redhat.com (Trond Eivind Glomsrød)
Subject Re: Why dump/restore to upgrade?
Date
Msg-id xuyadukdjr8.fsf@halden.devel.redhat.com
Whole thread Raw
In response to Re: Why dump/restore to upgrade?  (Lamar Owen <lamar.owen@wgcr.org>)
List pgsql-hackers
Lamar Owen <lamar.owen@wgcr.org> writes:

> On Friday 08 February 2002 12:44 am, Tom Lane wrote:
> > mlw <markw@mohawksoft.com> writes:
> > > but I'd like to make a general call to arms that this (or 7.3) should be
> > > the last release to require this.
> 
> > We will never make such a commitment, at least not in the foreseeable
> > future.
> 
> Why?
> 
> > But to bind
> > ourselves forever to the current on-disk format is sheer folly.
> 
> Certainly true.  But upgradability!=bound-to-the-same-format.
> 
> > And if you have to convert the datafile format then you might as
> > well dump and reload.
> 
> No.  Dump - reload is folly.  And it doesn't always work.  And that's the 
> problem.

Add some unicode into it for even more fun. Bah.

-- 
Trond Eivind Glomsrød
Red Hat, Inc.


pgsql-hackers by date:

Previous
From: Jean-Michel POURE
Date:
Subject: Database abstration layers
Next
From: Peter Eisentraut
Date:
Subject: Re: PostgreSQL 7.2 on SlashDot