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>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Sajith Prabhakar Shetty <ssajith@blackduck.com>, Andrei Lepikhov <lepihov@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-08-07T17:58:08Z
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 8/4/25, 4:12 PM, "Peter Geoghegan" <pg@bowt.ie <mailto:pg@bowt.ie>> wrote:
> Todd, Sajith: it would be helpful if you could test this patch.
> Possibly by using the original problematic query, rather than the
> minimized version that you posted to the list. The patch won't bring
> performance up to parity with Postgres 15, but it should be a great
> deal faster. Note that the patch that I've posted will only apply
> against the current master branch (I'll prepare patches for earlier
> branches once I have some buy-in).

I'm working with our performance testing team to rerun our load tests
with the patch applied.  However, the current infrastructure doesn't
support deploying custom PG builds, so it's unlikely we'll be able to
provide results in time for the upcoming minor releases.

Also, is it significant effort to produce a patch for PG 17?  Running the
load tests against master would make it chancy to compare the results
with the data we already have.

-- todd