Re: Minmax indexes - Mailing list pgsql-hackers

From Erik Rijkers
Subject Re: Minmax indexes
Date
Msg-id 595f598acb288b69f6096b3bf8cd94aa.squirrel@webmail.xs4all.nl
Whole thread Raw
In response to Re: Minmax indexes  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Minmax indexes  ("Erik Rijkers" <er@xs4all.nl>)
Re: Minmax indexes  (Jeff Janes <jeff.janes@gmail.com>)
Re: Minmax indexes (timings)  ("Erik Rijkers" <er@xs4all.nl>)
List pgsql-hackers
On Fri, November 8, 2013 21:11, Alvaro Herrera wrote:
>
> 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.
>
> [minmax-7.patch]

The earlier errors are indeed fixed; now, I've been trying with the attached test case but I'm unable to find a query
that
improves with minmax index use.  (it gets used sometimes but speedup is negligable).

That probably means I'm doing something wrong; could you (or anyone) give some hints about use-case would be expected?

(Or is it just the unfinished selectivity function?)


Thanks,

Erikjan Rijkers




Attachment

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Race condition in b-tree page deletion
Next
From: "Colin 't Hart"
Date:
Subject: TABLE not synonymous with SELECT * FROM?