Re: Index ot being used

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Madison Kelly <linux(at)alteeve(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org, Bruno Wolff III <bruno(at)wolff(dot)to>
Subject: Re: Index ot being used
Date: 2005-06-13 18:13:23
Message-ID: 22127.1118686403@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Madison Kelly <linux(at)alteeve(dot)com> writes:
> Bruno Wolff III wrote:
>> Please actually try this before changing anything else.

> If I follow then I tried it but still got the sequential scan.

Given the fairly large number of rows being selected, it seems likely
that the planner thinks this is faster than an indexscan. It could
be right, too. Have you tried "set enable_seqscan = off" to see if
the index is used then? If so, is it faster or slower? Comparing
EXPLAIN ANALYZE results with enable_seqscan on and off would be useful.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Madison Kelly 2005-06-13 19:05:00 Re: Index ot being used
Previous Message Madison Kelly 2005-06-13 17:57:31 Re: Index ot being used