On 1/29/20 9:39 AM, Perumal Raj wrote:
Hi All,
We have recently upgraded postgres from 9.2 to 11.6 and started seeing
performance issue immediately and able to fix the performance issue
after disabling parameter: enable_seqscan.
Question :
Should i keep the above parameter always disabled ? If not why the
behavior changed in Higher version ?
Without an explain analyze of a representative query it would be hard to
say.
Also the schema of the the tables involved would be helpful.
Note:
Table ANALYZE completed as part of Upgrade activity.
Was this on a single table or all tables?
Thanks
Raj
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
