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

Peter Geoghegan <pg@bowt.ie>

From: Peter Geoghegan <pg@bowt.ie>

To: Sajith Prabhakar Shetty <ssajith@blackduck.com>

Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrei Lepikhov <lepihov@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>, Todd Cook <cookt@blackduck.com>

Date: 2025-08-05T14:47:22Z

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 →

Convert strategies to and from compare types
- c09e5a6a0165 18.0 cited
Enhance nbtree ScalarArrayOp execution.
- 5bf748b86bc6 17.0 cited
Improve planning of btree index scans using ScalarArrayOpExpr quals.
- a4523c5aa534 9.5.0 cited
Fix planning of btree index scans using ScalarArrayOpExpr quals.
- 807a40c551dd 9.3.0 cited

On Tue, Aug 5, 2025 at 1:31 AM Sajith Prabhakar Shetty
<ssajith@blackduck.com> wrote:
> Before proceeding with testing the patch against the original problematic query, I wanted to check with you — should I go ahead and apply the current patch, or would it be better to wait for any revised version based on Tom’s feedback?

I doubt that Tom's feedback will affect the performance profile of the
patch. v1 is very likely to be representative of the final patch in
every way that your testing will consider, so I see no reason to wait.

-- 
Peter Geoghegan