From: Tom Lane <tgl@sss.pgh.pa.us>
To: Prajna Shetty <Prajna.Shetty@mindtree.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Cc: Beenu Sharma <Beenu.Sharma@mindtree.com>
Subject: Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
Date: Mon, 21 Mar 2022 09:59:08 -0400
Message-ID: <1872582.1647871148@sss.pgh.pa.us> (raw)
In-Reply-To: <MAZPR01MB546945FEA4E21EE7C8E532FB92169@MAZPR01MB5469.INDPRD01.PROD.OUTLOOK.COM>
References: <MAZPR01MB546945FEA4E21EE7C8E532FB92169@MAZPR01MB5469.INDPRD01.PROD.OUTLOOK.COM>
Prajna Shetty <Prajna.Shetty@mindtree.com> writes:
> There is change in query plan in 12.4 version and Version 13 resulting in performance slowness post upgrade.
Standard upgrade methods don't transfer statistics from the old version,
so the first question to ask is have you ANALYZE'd the relevant tables
since upgrading?
If you have, then to offer useful help with this we'll need to see all
the details described in
https://wiki.postgresql.org/wiki/Slow_Query_Questions
In any case, this is unlikely to be a bug. The pgsql-performance
list would be a more suitable place to discuss it.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, Prajna.Shetty@mindtree.com, pgsql-bugs@lists.postgresql.org, Beenu.Sharma@mindtree.com
Subject: Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join
In-Reply-To: <1872582.1647871148@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox