I'm trying to benchmark some complex sql queries. One query, in
particular, is causing problems -- its cost values can vary from 228
to 907, its Total Runtimes from 60 ms to 5176 ms. The query plans
show that the optimizer is choosing different plans for different
iterations of the same query. Does anyone have any idea what's
going on here or maybe how I can force Postgres to prefer the faster
plan?
The query plans are very long (11 tables joined) but I can include
them if it might help. Thanks for any advice,
Roberto