Re: GIN improvements part 1: additional information
| От | Alexander Korotkov |
|---|---|
| Тема | Re: GIN improvements part 1: additional information |
| Дата | |
| Msg-id | CAPpHfds6BeB_woqrXWHE65y51GKURN-6mPv4jT68YHn0Do-bkg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: GIN improvements part 1: additional information (Heikki Linnakangas <hlinnakangas@vmware.com>) |
| Ответы |
Re: GIN improvements part 1: additional information
|
| Список | pgsql-hackers |
On Fri, Oct 4, 2013 at 12:41 AM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
------
With best regards,
Alexander Korotkov.
On 03.10.2013 23:37, Alexander Korotkov wrote:Hmm. All you need is some code to read the old format, and a function to convert a page to new format before updating. It doesn't seem *that* kludgey. It's a fair amount of work, for sure, but not insurmountable.2) Insert kluges into GIN to support both old and new formats. So, kluges
are kluges :) I don't see elegant way to do it for now, because formats are
very different.
My notice was not as much about amount of work as about result.
ItemPointers compression reduce occupied space in all normal cases. It's not very realistic, but it could increase space in worst case. That would lead to page split after conversion. Are we going to support such case?
------
With best regards,
Alexander Korotkov.
В списке pgsql-hackers по дате отправления: