From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: GIN improvements part 1: additional information |
Date: | 2013-09-15 09:14:45 |
Message-ID: | CAPpHfdutJEC9+6vWX579afZKzdHKCT2wzDkAEom1XmiXEwF3pw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Jun 29, 2013 at 12:56 PM, Heikki Linnakangas <
hlinnakangas(at)vmware(dot)com> wrote:
> There's a few open questions:
>
> 1. How are we going to handle pg_upgrade? It would be nice to be able to
> read the old page format, or convert on-the-fly. OTOH, if it gets too
> complicated, might not be worth it. The indexes are much smaller with the
> patch, so anyone using GIN probably wants to rebuild them anyway, sooner or
> later. Still, I'd like to give it a shot.
>
> 2. The patch introduces a small fixed 32-entry index into the packed
> items. Is that an optimal number?
>
> 3. I'd like to see some performance testing of insertions, deletions, and
> vacuum. I suspect that maintaining the 32-entry index might be fairly
> expensive, as it's rewritten on every update to a leaf page.
It appears that maintaining 32-entry index is really expensive because it
required re-decoding whole page. This issue is fixed in attached version of
patch by introducing incremental updating of that index. Benchmarks will be
posted later today.
------
With best regards,
Alexander Korotkov.
Attachment | Content-Type | Size |
---|---|---|
gin-packed-postinglists-3.patch.gz | application/x-gzip | 19.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Geoghegan | 2013-09-15 09:19:41 | Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE |
Previous Message | Amit Kapila | 2013-09-15 09:01:35 | Re: Minor inheritance/check bug: Inconsistent behavior |