| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Prajna Shetty <Prajna(dot)Shetty(at)mindtree(dot)com> |
| Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Beenu Sharma <Beenu(dot)Sharma(at)mindtree(dot)com> |
| Subject: | Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join |
| Date: | 2022-03-21 13:59:08 |
| Message-ID: | 1872582.1647871148@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-performance |
Prajna Shetty <Prajna(dot)Shetty(at)mindtree(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2022-03-21 14:18:20 | Re: Logical replication stops dropping used initial-sync replication slots |
| Previous Message | PG Bug reporting form | 2022-03-21 13:08:44 | BUG #17444: ERROR: found xmin 215633 from before relfrozenxid 1280585 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prajna Shetty | 2022-03-22 12:57:10 | Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join |
| Previous Message | Prajna Shetty | 2022-03-21 11:45:05 | Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join |