| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Minmax indexes |
| Date: | 2014-07-09 22:45:20 |
| Message-ID: | 53BDC600.7070704@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 07/09/2014 02:16 PM, Alvaro Herrera wrote:
> The way it works now, each opclass needs to have three support
> procedures; I've called them getOpers, maybeUpdateValues, and compare.
> (I realize these names are pretty bad, and will be changing them.)
I kind of like "maybeUpdateValues". Very ... NoSQL-ish. "Maybe update
the values, maybe not." ;-)
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2014-07-09 22:54:05 | Re: Minmax indexes |
| Previous Message | Peter Geoghegan | 2014-07-09 22:19:04 | Re: Doing better at HINTing an appropriate column within errorMissingColumn() |