| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com> |
| Cc: | PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org> |
| Subject: | Re: Need a better name for MinMax indexes |
| Date: | 2014-06-18 01:17:32 |
| Message-ID: | 53A0E8AC.9080700@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
On 06/17/2014 02:43 PM, Jonathan S. Katz wrote:
> On Jun 17, 2014, at 5:36 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>
>> One of the features for 9.5 will likely be "minmax" indexes, which are
>> indexes which index only the upper and lower bounds of each data page,
>> making for a very compact index ... like 100MB for a 100GB table.
>>
>> The working name for these are "minmax" indexes which is not very
>> compelling and unlikely to reach users for how cool and useful they are.
>> Suggestions on an alternate name?
>
> At the risk of sounding trite and clichéd: "big data index" or "big table index" - after all, it is an index that you want to use on a big table.
Except that these likely aren't going to be the only "big data indexes"
we ever have.
Maybe "Compressed Range Indexes"? Pretty wordy, though.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | robert7390 | 2014-06-18 02:08:21 | Re: Need a better name for MinMax indexes |
| Previous Message | Jonathan S. Katz | 2014-06-17 21:43:28 | Re: Need a better name for MinMax indexes |