| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> | 
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org | 
| Subject: | Re: How to force PostgreSQL using an index | 
| Date: | 2006-02-15 22:06:56 | 
| Message-ID: | 20060215220656.GF6562@phlogiston.dyndns.org | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-sql | 
On Wed, Feb 15, 2006 at 04:58:54PM -0500, Daniel Caune wrote:
> Hi,
> 
>  
> 
> Is there a way to force PostgreSQL using an index for a SELECT
> statement?  I just want to confirm that the index PostgreSQL decides to
> use is better than the index I supposed PostgreSQL would use (I already
> analyze the table).
Your best bet is to do
set enable_indexscan=false;
and then do the EXPLAIN ANALYSE for your select.
You might also find that fiddling with other settings affects the
planner's idea of what would be a good plan.  The planner is
sensitive to what it thinks it knows about your environment.
A
-- 
Andrew Sullivan  | ajs(at)crankycanuck(dot)ca
If they don't do anything, we don't need their acronym.
		--Josh Hamilton, on the US FEMA
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Caune | 2006-02-15 22:26:57 | Re: How to force PostgreSQL using an index | 
| Previous Message | Owen Jacobson | 2006-02-15 22:06:55 | Re: How to force PostgreSQL using an index |