Re: Planner incorrectly choosing seq scan over index scan - Mailing list pgsql-performance

From Tobias Brox
Subject Re: Planner incorrectly choosing seq scan over index scan
Date
Msg-id 20050801223708.GE17649@tobias.lan
Whole thread Raw
In response to Planner incorrectly choosing seq scan over index scan  (Meetesh Karia <meetesh.karia@gmail.com>)
Responses Re: Planner incorrectly choosing seq scan over index scan  (Meetesh Karia <meetesh.karia@gmail.com>)
List pgsql-performance
[Meetesh Karia - Tue at 12:19:27AM +0200]
> We're using 8.0.3 and we're seeing a problem where the planner is choosing a
> seq scan and hash join over an index scan. If I set enable_hashjoin to off,
> then I get the plan I'm expecting and the query runs a lot faster. I've also
> tried lowering the random page cost (even to 1) but the planner still
> chooses to use the hash join.

Have you tried increasing the statistics collection?

--
Tobias Brox, +47-91700050
Nordicbet, IT dept

pgsql-performance by date:

Previous
From: Meetesh Karia
Date:
Subject: Planner incorrectly choosing seq scan over index scan
Next
From: John Arbash Meinel
Date:
Subject: Re: Planner incorrectly choosing seq scan over index scan