From: | Matthew Wakeling <matthew(at)flymine(dot)org> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: GiST index performance |
Date: | 2009-04-16 16:37:58 |
Message-ID: | alpine.DEB.2.00.0904161736370.4053@aragorn.flymine.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Thu, 16 Apr 2009, Kevin Grittner wrote:
> Matthew Wakeling <matthew(at)flymine(dot)org> wrote:
>> I have been doing some queries that are best answered with GiST
>> indexes
>
> For what definition of "best answered"?
>
> Since an index is only a performance tuning feature (unless declared
> UNIQUE), and should never alter the results (beyond possibly affecting
> row order if that is unspecified), how is an index which performs
> worse than an alternative the best answer?
Don't be misled by my example using integers. I'm doing queries on the
bioseg data type, and the only index type for that is GiST. There isn't a
better alternative.
Matthew
--
"Finger to spiritual emptiness underlying everything."
-- How a foreign C manual referred to a "pointer to void."
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-04-16 16:46:46 | Re: GiST index performance |
Previous Message | Kevin Grittner | 2009-04-16 16:33:21 | Re: GiST index performance |