Re: Minmax indexes

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: obartunov(at)gmail(dot)com, 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>, Alvaro Herrera <alvherre(at)2ndquadrant(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-08 00:47:43
Message-ID: 53E41E2F.9040705@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 08/07/2014 08:38 AM, Oleg Bartunov wrote:
> +1 for BRIN !
>
> On Thu, Aug 7, 2014 at 6:16 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On 7 August 2014 14:53, Robert Haas <robertmhaas(at)gmail(dot)com> 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.

How about Block Range Dynamic indexes?

Or Range Usage Metadata indexes?

You see what I'm getting at:

BRanDy

RUM

... to keep with our "new indexes" naming scheme ...

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2014-08-08 00:50:09 Re: Reporting the commit LSN at commit time
Previous Message Tom Lane 2014-08-08 00:47:09 Re: Quick doc fix