Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 - Mailing list pgsql-bugs

From Todd Cook
Subject Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date
Msg-id 53859E8F-67E7-4A25-AEE1-C7E472262F47@blackduck.com
Whole thread Raw
In response to Re: Postgres: Queries are too slow after upgrading to PG17 from PG15  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-bugs
On 8/8/25, 6:04 PM, "Merlin Moncure" <mmoncure@gmail.com <mailto:mmoncure@gmail.com>> wrote:
> I think it is very likely going to address your issue, but
> confirmation helps, and will make it more likely for this patch to be
> pushed. After that, you will have to decide to downgrade to 15 or
> suffer the status. quo until 18 releases. Running a custom patched 17
> is possible if a patch could be made to appear, but I do not recommend
> it given where you are at in the release calendar.

We're still working on providing confirmation.  Our load testing environment depends on
third-party PG providers, so there's a significant amount of ongoing work to set up a
configuration where we can use a custom PG build.  This is a high priority for us, so it will
get done, though maybe not for a couple more weeks yet.

-- todd


pgsql-bugs by date:

Previous
From: Thadeus Anand
Date:
Subject: Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine
Next
From: PG Bug reporting form
Date:
Subject: BUG #19031: pg_trgm infinite loop on certain cases