Re: WIP: store additional info in GIN index

Поиск
Список
Период
Сортировка
От Alexander Korotkov
Тема Re: WIP: store additional info in GIN index
Дата
Msg-id CAPpHfdu-2wt1qjMOMVvY+EtMf=k6u_P5CvyewEYH043ohstv4g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: WIP: store additional info in GIN index  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: WIP: store additional info in GIN index
Список pgsql-hackers
On Tue, Dec 4, 2012 at 9:34 PM, Robert Haas <robertmhaas@gmail.com> wrote:
On Sun, Nov 18, 2012 at 4:54 PM, Alexander Korotkov
<aekorotkov@gmail.com> wrote:
> Patch completely changes storage in posting lists and leaf pages of posting
> trees. It uses varbyte encoding for BlockNumber and OffsetNumber.
> BlockNumber are stored incremental in page. Additionally one bit of
> OffsetNumber is reserved for additional information NULL flag. To be able to
> find position in leaf data page quickly patch introduces small index in the
> end of page.

This sounds like it means that this would break pg_upgrade, about
which I'm not too keen.  Ideally, we'd like to have a situation where
new indexes have additional capabilities, but old indexes are still
usable for things that they could do before.  I am not sure whether
that's a realistic goal.

This means to have two versions of code which deals with posting trees and lists. For me it seems unlikely we have resources for maintenance of this.

------
With best regards,
Alexander Korotkov.

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

Предыдущее
От: Alexander Korotkov
Дата:
Сообщение: Re: Patch for removng unused targets
Следующее
От: Simon Riggs
Дата:
Сообщение: Review of Row Level Security