| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade project status |
| Date: | 2009-01-28 15:52:47 |
| Message-ID: | 17116.1233157967@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> Heikki Linnakangas pe 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Brindle | 2009-01-28 15:56:18 | Re: How to get SE-PostgreSQL acceptable |
| Previous Message | Heikki Linnakangas | 2009-01-28 15:38:40 | Re: Hot standby, recovery infra |