Re: Need a better name for MinMax indexes
От | robert7390@comcast.net |
---|---|
Тема | Re: Need a better name for MinMax indexes |
Дата | |
Msg-id | 20140618020821.5955729.59707.2463@comcast.net обсуждение исходный текст |
Ответ на | Re: Need a better name for MinMax indexes (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Need a better name for MinMax indexes
|
Список | pgsql-advocacy |
If this is going to be the start of a new type of index then maybe that's how you market it ie. part of a suite, or class,of optimized indexes. Robert Bernier Sent from my BlackBerry 10 smartphone. Original Message From: Josh Berkus Sent: Tuesday, June 17, 2014 6:17 PM To: Jonathan S. Katz Cc: PostgreSQL Advocacy Subject: Re: [pgsql-advocacy] Need a better name for MinMax indexes On 06/17/2014 02:43 PM, Jonathan S. Katz wrote: > On Jun 17, 2014, at 5:36 PM, Josh Berkus <josh@agliodbs.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 wantto 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 -- Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-advocacy
В списке pgsql-advocacy по дате отправления: