From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Zdenek Kotala <Zdenek(dot)Kotala(at)sun(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 07:24:06 |
Message-ID: | 49800816.9050504@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> That implies a fairly robust and configurable system for adding to and
>> rewriting system catalogs, which today we haven't got.
>
> And we won't ever have, because it's unnecessary and would be impossibly
> complex. We know how to do the catalog update: basically, dump, initdb,
> reload, then move the data in. There are some corner case issues like
> how to preserve toast table OIDs, but the idea that we are going to
> invent a special process for each catalog change is just not reasonable.
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.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Timo Savola | 2009-01-28 08:49:55 | Re: log_duration_sample config option patch |
Previous Message | Fujii Masao | 2009-01-28 07:14:14 | New version of Synch Rep patch |