Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join

On Tue, Mar 22, 2022 at 12:57:10PM +, Prajna Shetty wrote: > 1. We have performed Vacuum/Analyze/Reindex post Upgrade. > 2. Tweaked work_mem so it does not spill to Disk. We can Disk Usage But > it is still using Hash Aggregate and came down from 5 minutes to 20 seconds. > (Expected

Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join

++ pgsql-performa...@postgresql.org Hello Team, There is change in query plan in 12.4 version and Version 13 resulting in performance slowness post upgrade. * In 12.4 version, Sort Operation Group Aggregate is selected which results to

Re: Using system tables directly takes many hours, using temp tables with no indexes takes a few seconds for geometry_columns view.

From: Justin Pryzby Sent: Wednesday, March 23, 2022 2:19 PM >On Wed, Mar 23, 2022 at 09:44:09AM +, Lars Aksel Opsahl wrote: >> Why is temp tables with no indexes much faster system tables with indexes ? > >I think the "temp table" way is accidentally faster du