Re: Minmax indexes
Thom Brown <thom@linux.com>
From: Thom Brown <thom@linux.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Erik Rijkers <er@xs4all.nl>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2014-01-24T17:54:19Z
Lists: pgsql-hackers
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. Alles klar. Thanks -- Thom
Commits
-
Refactor per-page logic common to all redo routines to a new function.
- f8f4227976a2 9.5.0 cited
-
Reduce use of heavyweight locking inside hash AM.
- 76837c1507cb 9.3.0 cited
-
Scan the buffer pool just once, not once per fork, during relation drop.
- ece01aae4792 9.2.0 cited
-
Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>
- 9e2a87b62db8 7.1.1 cited