| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | 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>, Todd Cook <cookt(at)blackduck(dot)com> |
| Subject: | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
| Date: | 2025-08-02 02:05:08 |
| Message-ID: | 2538941.1754100308@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2025-08-02 03:07:31 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
| Previous Message | Tom Lane | 2025-08-02 01:09:59 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |