Re: posting tree compression (WAS: Proposal: fix range queries in btree_gin)

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: posting tree compression (WAS: Proposal: fix range queries in btree_gin)
Date: 2014-03-31 21:21:35
Message-ID: CA+TgmoZwmhoZhJVm3BZSeLkpr0rg9EMit0bgXAzK1kXNPbGRRw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Mar 28, 2014 at 11:30 AM, Alexander Korotkov
<aekorotkov(at)gmail(dot)com> wrote:
> after reading Heikki Linnakangas presentation about GIN from Nordic PGDay, I
> figure out that btree_gin became much more attractive.
> http://hlinnaka.iki.fi/presentations/NordicPGDay2014-GIN.pdf

This is a mighty interesting presentation. Could the posting tree
compression described on the "posting tree page format" slides (pp.
16-17, I think) be used for btree also? Would we get similar
benefits? How much more expensive are updates with the new system?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Claudio Freire 2014-03-31 21:29:06 Re: posting tree compression (WAS: Proposal: fix range queries in btree_gin)
Previous Message Robert Haas 2014-03-31 21:09:51 Re: Archive recovery won't be completed on some situation.