Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 - Mailing list pgsql-bugs

From Todd Cook
Subject Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date
Msg-id BF2F92D9-2208-4CCD-8F4D-8A2F8FBC9F71@blackduck.com
Whole thread Raw
In response to Re: Postgres: Queries are too slow after upgrading to PG17 from PG15  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
List pgsql-bugs
On 9/25/25, 3:47 PM, "Peter Geoghegan" <pg@bowt.ie <mailto:pg@bowt.ie>> wrote:
> Should be noted that the regression itself is definitely "a small
> effect that is multiplied by repetition". This makes the problem
> rather perverse (though it's not exactly unusual for a complaint about
> a planner regression to be perverse, in one way or another).

Thanks for confirming.  We can develop a strategy for working around
this effect, so from my point of view, we can consider this matter
resolved.  I'm guessing that you feel the same way, but if not, I'm
happy to help out in any way I can.

In any case, I do appreciate your efforts and the time you took to
write out the very helpful explanations you provided. __

-- todd


pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ?
Next
From: "David G. Johnston"
Date:
Subject: Re: BUG #19064: Trigger allows creation with invalid column references but fails at runtime