Re: Minmax indexes
| От | Claudio Freire |
|---|---|
| Тема | Re: Minmax indexes |
| Дата | |
| Msg-id | CAGTBQpbJEa_AkUMQqfbonhzMUE_KYiN06Q_+W+5XJTEmcG1sKw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Minmax indexes (Thom Brown <thom@linux.com>) |
| Ответы |
Re: Minmax indexes
|
| Список | pgsql-hackers |
On Fri, Jan 24, 2014 at 2:54 PM, Thom Brown <thom@linux.com> wrote: > On 24 January 2014 17:53, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: >> Thom Brown wrote: >>> On 8 November 2013 20:11, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: >>> > Erik Rijkers wrote: >>> >> On Thu, September 26, 2013 00:34, Erik Rijkers wrote: >>> >> > On Wed, September 25, 2013 22:34, Alvaro Herrera wrote: >>> >> > >>> >> >> [minmax-5.patch] >>> >> > >>> >> > I have the impression it's not quite working correctly. >>> > >>> > Here's a version 7 of the patch, which fixes these bugs and adds >>> > opclasses for a bunch more types (timestamp, timestamptz, date, time, >>> > timetz), courtesy of Martín Marqués. It's also been rebased to apply >>> > cleanly on top of today's master branch. >>> > >>> > I have also added a selectivity function, but I'm not positive that it's >>> > very useful yet. >>> >>> This patch doesn't appear to have been submitted to any Commitfest. >>> Is this still a feature undergoing research then? >> >> It's still a planned feature, but I didn't have time to continue work >> for 2014-01. What's the status? I believe I have more than a use for minmax indexes, and wouldn't mind lending a hand if it's within my grasp.
В списке pgsql-hackers по дате отправления: