I usually reduce cpu_index_tuple_cost in postgresql.conf, from 0.001 to 0.000001, this way the optimizer is "more willing" to use indexes.
Of course you should try different values until you find the ones that adjust to your system configuration.
On Thu, 2003-08-14 at 09:00, Dave Cramer wrote:
I have a query which definitely runs faster when sequential scans are
turned off. Which parameters do I tune? and which way?
After quickly perusing the docs, and google, I think it is the
random_page_cost?
Any help would be appreciated.
Dave
