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

From David G. Johnston
Subject Re: A serious change in performance between PG 15 and PG 16, 17, 18.
Date
Msg-id CAKFQuwYPyO+S+Hrb03pPctKP3y6LRoM1OvXBwiB3N32UUy5pzQ@mail.gmail.com
Whole thread
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 Sunday, February 15, 2026, Clive Boughton <clive.boughton@softimp.com.au> 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.

If you cannot provide at least explain analyze, before and after, the odds of making progress on this is greatly diminished.  A minimal reproducer you can verify and share is exponentially better though.

It’s probably worth ensuring JIT is disabled even going off this minimal information.

David J.

pgsql-performance by date:

Previous
From: David Rowley
Date:
Subject: Re: A serious change in performance between PG 15 and PG 16, 17, 18.
Next
From: Andrei Lepikhov
Date:
Subject: Re: A serious change in performance between PG 15 and PG 16, 17, 18.