From: | Perumal Raj <perucinci(at)gmail(dot)com> |
---|---|
To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
Cc: | "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 22:40:11 |
Message-ID: | CALvqh4qaQCgyMtKDXa_1xfodXwZtV_oYYLLJ+Cay5bq=SQd6Gw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Peter,
I strongly i agree,
I have used pg_upgrade which runs "analyze_new_cluster.sh" as post upgrade
activity across all DB on cluster.
Also, I have executed manual vacuum on all individual tables. However the
behavior is same until i disable the above said parameter.
Regards,
Raj
On Wed, Jan 29, 2020 at 2:33 PM Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
> On 2020-01-29 09:39:03 -0800, Perumal Raj wrote:
> > 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.
>
> How did you upgrade?
>
> If your upgrade involved a dump and restore, you should invoke ANALYZE
> for each database (I think autovacuum will analyze all tables
> eventually, but takes its time).
>
> hp
>
> --
> _ | Peter J. Holzer | Story must make more sense than reality.
> |_|_) | |
> | | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
> __/ | http://www.hjp.at/ | challenge!"
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-01-29 22:54:38 | Re: Performance Issue after upgrade from 9 to 11 |
Previous Message | Peter J. Holzer | 2020-01-29 22:33:38 | Re: Performance Issue after upgrade from 9 to 11 |