| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, 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:35:17 |
| Message-ID: | 20140806163517.GN13302@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 6, 2014 at 01:31:14PM -0300, Claudio Freire wrote:
> 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.
"Block filter" indexes?
> The create command can still use minmax, or rangemap if you prefer
> that, while the framework's code uses summary or summarizing.
"Summary" sounds like materialized views to me.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Claudio Freire | 2014-08-06 16:42:15 | Re: Minmax indexes |
| Previous Message | Claudio Freire | 2014-08-06 16:31:14 | Re: Minmax indexes |