| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Perumal Raj <perucinci(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Performance Issue after upgrade from 9 to 11 |
| Date: | 2020-01-29 18:20:36 |
| Message-ID: | eeeba437-9696-00e7-d574-b486e8eec186@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-01-29 18:22:31 | Re: Performance Issue after upgrade from 9 to 11 |
| Previous Message | Perumal Raj | 2020-01-29 17:39:03 | Performance Issue after upgrade from 9 to 11 |