On Wed, Mar 17, 2010 at 5:25 PM, Christian Brink <cbrink(at)r-stream(dot)com>wrote:
>
> -> Index Scan using sales_tranzdate_index on sales s
> (cost=0.01..1825.27 rows=22530 width=12) (actual time=0.072..3.464 rows=225
> loops=1)
>
Have you tried increasing the statistics on that table (and then analyzing)?
The estimates for that index scan are off by a factor of 100, which may
indicate why the planner is trying so hard to avoid a nestloop there.
--
- David T. Wilson
david(dot)t(dot)wilson(at)gmail(dot)com