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-02T01:09:59Z
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.

Peter Geoghegan <pg@bowt.ie> writes:
> My inclination is to pursue the simpler approach, and just accept the
> remaining performance shortfall. This is a rare enough case that I
> think that that'll be acceptable. But input on how to make this
> trade-off would be helpful.

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.

			regards, tom lane