On Fri, 18 Jul 2003, Fabian Kreitner wrote:

> Adjusting the cpu_tuple_cost to 0.042 got the planner to choose the index.

Doesn't sound very good and it will most likely make other queries slower.
You could always turn off sequential scan before that query and turn it on

> Anything I need to consider when raising it to such "high" values?

You could fill the table with more data and it will probably come to a 
point where it will stop using the seq. scan.

You could of course also change pg itself so it calculates a better


---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Reply via email to