| 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 01:09:59 |
| Message-ID: | 2532876.1754096999@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Peter Geoghegan <pg(at)bowt(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-08-02 02:05:08 | Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 |
| Previous Message | Nathan Bossart | 2025-08-01 22:01:47 | Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist |