| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(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-06 16:31:14 |
| Message-ID: | CAGTBQpYRx+9wtY2jWDNvhw1oy3NhZDwiYEuB-HG9xcbJdYFDJA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 6, 2014 at 1:25 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> CREATE INDEX foo ON t USING crange (cols) -- misspelling of "cringe"?
> CREATE INDEX foo ON t USING comprange (cols)
> CREATE INDEX foo ON t USING compressedrng (cols) -- ugh
> -- or use an identifier with whitespace:
> CREATE INDEX foo ON t USING "compressed range" (cols)
The word you'd use there is not necessarily the one you use on the
framework, since the framework applies to many such techniques, but
the index type there is one specific one.
The create command can still use minmax, or rangemap if you prefer
that, while the framework's code uses summary or summarizing.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-08-06 16:35:17 | Re: Minmax indexes |
| Previous Message | Claudio Freire | 2014-08-06 16:29:07 | Re: Minmax indexes |