Horton

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

Todd Cook <cookt@blackduck.com>

View thread
From: Todd Cook <cookt@blackduck.com>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Merlin Moncure <mmoncure@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Sajith Prabhakar Shetty <ssajith@blackduck.com>, Andrei Lepikhov <lepihov@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-09-26T12:30:36Z
Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Convert strategies to and from compare types

  2. Enhance nbtree ScalarArrayOp execution.

  3. Improve planning of btree index scans using ScalarArrayOpExpr quals.

  4. Fix planning of btree index scans using ScalarArrayOpExpr quals.

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