Daniel Schuchardt <[EMAIL PROTECTED]> writes: > i have a query plan who is bad with standard cpu_tuple_costs and good if > I raise cpu_tuple_costs. Is it is a good practice to raise them if i > want to force postgres to use indexes more often?
Reducing random_page_cost is usually the best way to get the planner to
favor indexscans more.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
