On Sat, Sep 23, 2017 at 6:10 PM, Jack Christensen
wrote:
> Just had an issue where a prepared query would occasionally choose a very
> bad plan in production. The same data set in a different environment
> consistently would choose the index scan. As would be expected,
Just had an issue where a prepared query would occasionally choose a
very bad plan in production. The same data set in a different
environment consistently would choose the index scan. As would be
expected, running analyze on that table in production resolved the issue.
However, before I ran