Re: A serious change in performance between PG 15 and PG 16, 17, 18. - Mailing list pgsql-performance

From Andrei Lepikhov
Subject Re: A serious change in performance between PG 15 and PG 16, 17, 18.
Date
Msg-id d5d5c634-68d5-4cfc-bd55-fd3877322d43@gmail.com
Whole thread Raw
In response to A serious change in performance between PG 15 and PG 16, 17, 18.  (Clive Boughton <clive.boughton@softimp.com.au>)
List pgsql-performance
On 16/2/26 04:49, Clive Boughton wrote:
> For reasons of security I can't provide all the SQL code, but I can (if 
> it is necessary) provide an outline of what the code does.
In principle, you can provide EXPLAIN and schema in a private email so 
we can invent a synthetic example for public discussion based on your 
problem (I wonder if it is related to one of the typical Postgres issues 
like index picking or Subplan transformation).
I already had such an experience with a company from Sydney, and it 
worked well.

-- 
regards, Andrei Lepikhov,
pgEdge



pgsql-performance by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: A serious change in performance between PG 15 and PG 16, 17, 18.
Next
From: Riaan Stander
Date:
Subject: Re: Postgres IO sweet spot