"George Pavlov" <gpavlov@xxxxxxxxxxxxxx> writes: >> From: Joshua D. Drake [mailto:jd@xxxxxxxxxxxxxxxxx] >> In those rare cases wouldn't it make more sense to just set >> enable_seqscan to off; run query; set enable_seqscan to on; > 1. these cases are not that rare (to me); It strikes me that you probably need to adjust the planner cost parameters to reflect reality on your system. Usually dropping random_page_cost is the way to bias the thing more in favor of index scans. regards, tom lane