RE: Big performance slowdown from 11.2 to 13.3

From: "ldh(at)laurent-hasson(dot)com" <ldh(at)laurent-hasson(dot)com>
To: Michael Lewis <mlewis(at)entrata(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: RE: Big performance slowdown from 11.2 to 13.3
Date: 2021-07-21 23:31:06
Message-ID: MN2PR15MB2560D93B7142E19BE9CA70C985E39@MN2PR15MB2560.namprd15.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


From: Michael Lewis <mlewis(at)entrata(dot)com>
Sent: Wednesday, July 21, 2021 18:12
To: ldh(at)laurent-hasson(dot)com
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Big performance slowdown from 11.2 to 13.3

I'm not seeing the valueof the CTE. Why not access assessmenticcqa_raw directly in the main query and only do GROUP BY once? Do you have many values in iccqar_ques_code which are not used in this query?

Yes, there are close to 600 different values, and we are picking up only a small amount. And by the way, this is a classic case where the query could be folder as a sub-select in a join clause, and I tried this as well, with the same results.

Thank you,
Laurent.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Peter Geoghegan 2021-07-21 23:33:33 Re: Big performance slowdown from 11.2 to 13.3
Previous Message ldh@laurent-hasson.com 2021-07-21 23:19:04 RE: Big performance slowdown from 11.2 to 13.3