From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Prototype: In-place upgrade v02 |
Date: | 2008-09-08 12:57:20 |
Message-ID: | 48C52130.5000203@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas napsal(a):
> Zdenek Kotala wrote:
>> Tom Lane napsal(a):
>>> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>>>> In fact, I don't think there's any low-level data format changes yet
>>>> between 8.3 and 8.4, so this would be a comparatively easy release
>>>> to implement upgrade-in-place. There's just the catalog changes, but
>>>> AFAICS nothing that would require scanning through relations.
>>>
>>> After a quick scan of the catversion.h changelog (which hopefully covers
>>> any such changes): we changed sequences incompatibly, we changed hash
>>> indexes incompatibly (even without the pending patch that would change
>>> their contents beyond recognition), and Teodor did some stuff to GIN
>>> indexes that might or might not represent an on-disk format change,
>>> you'd have to ask him. We also whacked around the sort order of
>>> bpchar_pattern_ops btree indexes.
>>
>> Hmm, It seems that reindex is only good answer on all these changes.
>
> Isn't that exactly what we want to avoid with upgrade-in-place? As long
> as the conversion can be done page-at-a-time, without consulting other
> pages, we can do it when the page is read in.
Yes, but I meant what we can do for 8.4.
Zdenek
From | Date | Subject | |
---|---|---|---|
Next Message | Zdenek Kotala | 2008-09-08 13:01:00 | Re: Prototype: In-place upgrade v02 |
Previous Message | Gregory Stark | 2008-09-08 12:54:48 | Re: [PATCH] Cleanup of GUC units code |