Horton

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

David G. Johnston <david.g.johnston@gmail.com>

View thread View on postgr.es
From: "David G. Johnston" <david.g.johnston@gmail.com>
To: Clive Boughton <clive.boughton@softimp.com.au>
Cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Date: 2026-02-16T04:04:35Z
Lists: 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.