Re: select distinct, index not used

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sam Mason <sam(at)samason(dot)me(dot)uk>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: select distinct, index not used
Date: 2009-04-16 16:48:43
Message-ID: 20152.1239900523@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
> On Thu, Apr 16, 2009 at 11:29:25AM -0400, Tom Lane wrote:
>> , a full table indexscan isn't going to be particularly fast in
>> any case; it's often the case that seqscan-and-sort is the right
>> decision.

> Is PG capable of "skipping" over duplicate values using an index?

No, not at present. It's on the TODO list.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Gustavo Rosso 2009-04-16 17:10:12 triggers
Previous Message Sam Mason 2009-04-16 16:42:48 Re: select distinct, index not used