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

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Clive Boughton <clive(dot)boughton(at)softimp(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org
Subject: Re: A serious change in performance between PG 15 and PG 16, 17, 18.
Date: 2026-02-16 09:05:35
Message-ID: d5d5c634-68d5-4cfc-bd55-fd3877322d43@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Riaan Stander 2026-02-16 14:57:14 Re: Postgres IO sweet spot
Previous Message David G. Johnston 2026-02-16 04:04:35 Re: A serious change in performance between PG 15 and PG 16, 17, 18.