Re: PG_PAGE_LAYOUT_VERSION 5 - time for change

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: PG_PAGE_LAYOUT_VERSION 5 - time for change
Дата
Msg-id 87ej1xbzyx.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на PG_PAGE_LAYOUT_VERSION 5 - time for change  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Ответы Re: PG_PAGE_LAYOUT_VERSION 5 - time for change  (Zdenek Kotala <Zdenek.Kotala@Sun.COM>)
Список pgsql-hackers
Zdenek Kotala <Zdenek.Kotala@Sun.COM> writes:

> 3) TOAST modification
>   a) TOAST table per attribute
>   b) replace chunk id with offset+variable chunk size
>   c) add column identification into first chunk
>
> Thats all. I think infomask/infomask2 shuffle flag should be done. TOAST
> modification complicates in-place upgrade.

I don't think TOAST table per attribute is feasible You would end up with
thousands of toast tables. It might be interesting as an option if you plan to
drop the column but I don't see it as terribly interesting.

What seemed to make sense to me for solving your problem was including the
type oid in the toast chunks. I suppose attribute number might be just as good
-- it would let you save upgrading chunks for dropped columns at the expense
of having to look up the column info first.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's Slony Replication
support!


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: User defined I/O conversion casts
Следующее
От: Bernd Helmle
Дата:
Сообщение: WIP: Automatic view update rules