Horton

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

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: Sajith Prabhakar Shetty <ssajith@blackduck.com>, Andrei Lepikhov <lepihov@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, Todd Cook <cookt@blackduck.com>
Date: 2025-08-02T02:05: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.

I wrote:
> My thought here is that there is not a lot you can do in v17: it's
> been out for a year and we dare not destabilize it.  Take the easy
> near-guaranteed win and be happy.  Additional improvements can be
> pursued at our leisure in the master branch.

Also, the calendar is a factor here: we are only a week away from
release freeze for the August releases.  Even if you're feeling
optimistic about what we could risk in v17 with some development
effort, I'd counsel first working on a minimal patch that would
be safe to apply on short notice, so we can get the easy win
in this release cycle.

			regards, tom lane