Re: Minmax indexes

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Minmax indexes
Date: 2014-08-07 22:39:21
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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

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
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
minmax-14.patch text/x-diff 193.6 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2014-08-07 23:30:18 Hokey wrong versions of libpq in
Previous Message Jerry Sievers 2014-08-07 22:10:40 Re: Append to a GUC parameter ?