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

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 03:07:31
Message-ID: CAH2-WzmZE3=uyuBkVUvQoe_Ug=yKxayxQQOqCGcyzYbD0yXC6w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Aug 1, 2025 at 9:10 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 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.

I agree. I always thought that it was unlikely that anybody would
seriously argue in favor of the more ambitious approach I laid out. I
nevertheless felt obligated to present it as an option.

I find it natural to approach fixing this regression (and any other
regression with a fairly crisp problem statement) by starting from the
premise that the query should be at least as fast as it was on a
previous release, and working backwards from there. Actually meeting
that standard might not be practically achievable, for whatever
reason. But even then there is still value in understanding and
clearly communicating why it is that we fell short of that standard.

--
Peter Geoghegan

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Kapila 2025-08-02 03:27:10 Re: Use-after-free in reorderbuffer.c for INSERT ON CONFLICT
Previous Message Tom Lane 2025-08-02 02:05:08 Re: Postgres: Queries are too slow after upgrading to PG17 from PG15