Re: Postgres: Queries are too slow after upgrading to PG17 from PG15

From: Todd Cook <cookt(at)blackduck(dot)com>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sajith Prabhakar Shetty <ssajith(at)blackduck(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date: 2025-09-26 12:30:36
Message-ID: BF2F92D9-2208-4CCD-8F4D-8A2F8FBC9F71@blackduck.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 9/25/25, 3:47 PM, "Peter Geoghegan" <pg(at)bowt(dot)ie <mailto:pg(at)bowt(dot)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

In response to

Responses

Browse pgsql-bugs by date

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