Having been in a situation where Postgres suddenly decides to use a much slower query plan on a hot query in production, I'd agree.