Re: pg_upgrade project status - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_upgrade project status
Date
Msg-id 17116.1233157967@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_upgrade project status  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Responses Re: pg_upgrade project status  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:
> Heikki Linnakangas píše v st 28. 01. 2009 v 09:24 +0200:
>> Right, the dump+initdb+reload approach works quite well in both 
>> pg_upgrade and pg-migrator. I believe the biggest issue with that ATM is 
>> supporting dropped columns, and maybe there's something else, but it's 
>> fairly robust and works across any versions.

> It works but it is not ideal.

Sure, but the other way is just a complete non-starter.  It's enormous
amounts of work even for simple changes, and it's not hard to think of
potentially-desirable catalog rearrangements for which it would be
completely unworkable.

> I have idea how to do it without old PostgreSQL version and with
> bootstrap process extension which should not be invasive and easily
> maintainable. I will send idea latter ... stay tuned ;-)

New ideas welcome of course.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Hot standby, recovery infra
Next
From: Joshua Brindle
Date:
Subject: Re: How to get SE-PostgreSQL acceptable