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 AD7A39D2-1A49-4A73-A28B-1720134E013D@blackduck.com
Whole thread Raw
In response to Re: Postgres: Queries are too slow after upgrading to PG17 from PG15  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
List pgsql-bugs
On 8/4/25, 4:12 PM, "Peter Geoghegan" <pg@bowt.ie <mailto:pg@bowt.ie>> wrote:
> Todd, Sajith: it would be helpful if you could test this patch.
> Possibly by using the original problematic query, rather than the
> minimized version that you posted to the list. The patch won't bring
> performance up to parity with Postgres 15, but it should be a great
> deal faster. Note that the patch that I've posted will only apply
> against the current master branch (I'll prepare patches for earlier
> branches once I have some buy-in).

I'm working with our performance testing team to rerun our load tests
with the patch applied.  However, the current infrastructure doesn't
support deploying custom PG builds, so it's unlikely we'll be able to
provide results in time for the upcoming minor releases.

Also, is it significant effort to produce a patch for PG 17?  Running the
load tests against master would make it chancy to compare the results
with the data we already have.

-- todd




pgsql-bugs by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Next
From: Peter Praxmarer
Date:
Subject: BUG: IS NOT NULL on RECORD variable fails in 17.5-dev