Perumal Raj writes:
> I have used pg_upgrade which runs "analyze_new_cluster.sh" as post upgrade
> activity across all DB on cluster.
pg_upgrade itself won't run that script, it only creates it for you
to run.
> Also, I have executed manual vacuum on all individual tables. However the
> behavior
On 1/29/20 1:58 PM, Perumal Raj wrote:
Hi Tom /Adrian,
Issue is not specific to a table or particular Query. Also there is no
change in DB parameter after upgrade.
You obviously are seeing some difference, so pick a query and do an
EXPLAIN ANALYZE on it. Without some actual performance data
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,
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 re
Hi Tom /Adrian,
Issue is not specific to a table or particular Query. Also there is no
change in DB parameter after upgrade.
That the only way i can make it most of the the query to run as like before
upgrade.
Note:
Some web reference says , Engine will take some time to adjust until it
runs aut
Perumal Raj writes:
> 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 behavio
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 ?
