From: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_upgrade project status |
Date: | 2008-11-11 16:19:05 |
Message-ID: | 4919B079.4090708@sun.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian napsal(a):
> Zdenek Kotala wrote:
>> Bruce Momjian napsal(a):
>>> Zdenek Kotala wrote:
<snip>
>>>> 1) Data does not fit on the new page. It will be solve by pre-upgrade check
>>>> which reserve space on each page, before upgrade.
>>> Rather than specifying free space as an amount, I was thinking of having
>>> a boolean like 'ready_for_upgrade' and the system internally would know
>>> how much free space for each page and tuple.
>> You need booth, flag which shows you that the relation/database is ready for
>> upgrade and free space reservation configuration for each column. System cannot
>> know it because PostgreSQL is not oracle :-). It does not know what will happend
>> during next version development :-). It have to be setup by pre-upgrade script.
>
> So every Postgres version will allow space reservation based on the
> table and page, and the pre-upgrade script will set those values based
> on the table's columns --- makes sense, and avoids the need for a minor
> update to Postgres to add new code --- good idea.
yes, exactly.
Zdenek
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-11-11 16:28:35 | Re: RAM-only temporary tables |
Previous Message | Hitoshi Harada | 2008-11-11 16:09:02 | Re: Windowing Function Patch Review -> NTH_VALUE |