| From: | Todd Cook <cookt(at)blackduck(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Sajith Prabhakar Shetty <ssajith(at)blackduck(dot)com>, Andrei Lepikhov <lepihov(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
| Date: | 2025-08-25 12:30:37 |
| Message-ID: | 53859E8F-67E7-4A25-AEE1-C7E472262F47@blackduck.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 8/8/25, 6:04 PM, "Merlin Moncure" <mmoncure(at)gmail(dot)com <mailto:mmoncure(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2025-08-25 21:27:04 | BUG #19031: pg_trgm infinite loop on certain cases |
| Previous Message | Thadeus Anand | 2025-08-25 11:35:30 | Re: [CAUTION: SUSPECT SENDER] RE: [CAUTION: SUSPECT SENDER] RE: BUG #19029: Replication Slot size keeps increasing while logical subscription works fine |