Request a Demo
Home   >   mailing lists

Re: Planner join order regression from PG 15 to PG 16+: 70ms -> 1440ms (self-contained reproducer included) - Mailing list pgsql-performance

From Andrei Lepikhov
Subject Re: Planner join order regression from PG 15 to PG 16+: 70ms -> 1440ms (self-contained reproducer included)
Date
Msg-id a026f7c2-6439-4a7e-b9fb-e88fc0ccd2fd@gmail.com
Whole thread Raw
In response to Re: Planner join order regression from PG 15 to PG 16+: 70ms -> 1440ms (self-contained reproducer included)  (Mauro Gatti <mauro.gt70@gmail.com>)
List pgsql-performance
Tree view 
On 6/3/26 09:24, Mauro Gatti wrote:
> In any case, I don’t think there are other workable solutions without 
> changing the code.
The gist of the issue is hidden [anti]correlations between columns.
I like the idea of grouping columns into a custom type when an object in 
the data model is defined by several properties. This approach could 
help reduce the number of clauses, hide correlations within an object, 
and enable the use of histogram statistics.

I'm not sure if this idea is ready to use yet, or if Postgres has 
everything needed to make it work well - just note.

-- 
regards, Andrei Lepikhov,
pgEdge

pgsql-performance by date:

Previous
From: Mauro Gatti
Date:
Subject: Re: Planner join order regression from PG 15 to PG 16+: 70ms -> 1440ms (self-contained reproducer included)