Re: Minmax indexes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Minmax indexes
Date
Msg-id 20140807223921.GD7101@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Minmax indexes  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Minmax indexes
Re: Minmax indexes
List pgsql-hackers
Simon Riggs wrote:

> A better description would be "block range index" since we are
> indexing a range of blocks (not just one block). Perhaps a better one
> would be simply "range index", which we could abbreviate to RIN or
> BRIN.

Seems a lot of people liked BRIN.  I will be adopting that by renaming
files and directories soon.

Here's v14.  I fixed a few bugs; most notably, queries with IS NULL and
IS NOT NULL now work correctly.  Also I made the pageinspect extension
be able to display existing index tuples (I had disabled that when
generalizing the opclass stuff).  It only works with minmax opclasses
for now; it should be easy to fix if/when we add more stuff though.

I also added some docs.  These are not finished by any means.  They
talk about the index using the BRIN term.

All existing opclasses were renamed to "<type>_minmax_ops".

--
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: Jerry Sievers
Date:
Subject: Re: Append to a GUC parameter ?
Next
From: "Joshua D. Drake"
Date:
Subject: Hokey wrong versions of libpq in apt.postgresql.org