Horton

Re: BRIN range operator class

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Stefan Keller <sfkeller@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>, emre@hasegeli.com, Andreas Karlsson <andreas@proxel.se>, Paul Ramsey <pramsey@cleverelephant.ca>, "Obe, Regina" <robe.dnd@cityofboston.gov>
Date: 2015-05-05T02:24:33Z
Lists: pgsql-hackers 
Stefan Keller wrote:
> Hi,
> 
> 2015-05-05 2:51 GMT+02:00 Andreas Karlsson <andreas@proxel.se>:
> > From my point of view as a reviewer this patch set is very close to being
> > committable.
> 
> I'd like to thank already now to all committers and reviewers and hope
> BRIN makes it into PG 9.5.
> As a database instructor, conference organisator and geospatial
> specialist I'm looking forward for this clever new index.

Appreciated.  The base BRIN code is already in 9.5, so barring
significant issues you should see it in the next major release.
Support for geometry types and the like is still pending, but I hope to
get to it shortly.

> I'm keen to see if a PostGIS specialist jumps in and adds PostGIS
> geometry support.

Did you test the patch proposed here already?  It could be a very good
contribution.

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

Commits

  1. Refactor per-page logic common to all redo routines to a new function.

  2. Reduce use of heavyweight locking inside hash AM.

  3. Scan the buffer pool just once, not once per fork, during relation drop.

  4. Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>