Re: WIP: store additional info in GIN index

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: WIP: store additional info in GIN index
Date: 2012-12-04 18:05:44
Message-ID: 20121204180544.GC12055@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2012-12-04 10:04:03 -0800, Josh Berkus wrote:
> On 12/4/12 9:34 AM, Robert Haas wrote:
> > On Sun, Nov 18, 2012 at 4:54 PM, Alexander Korotkov
> > <aekorotkov(at)gmail(dot)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.
>
> Is there a reason not to create this as a new type of index? "GIN2" or
> whatever?

Aren't the obvious maintenance problems enough?

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2012-12-04 18:05:47 Re: json accessors
Previous Message Josh Berkus 2012-12-04 18:04:03 Re: WIP: store additional info in GIN index