Request a Demo
Home   >   mailing lists

Re: Postgres: Queries are too slow after upgrading to PG17 from PG15 - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Date
Msg-id CAH2-WzkkX8_YzdstPeQ4ni2eyyNqtvb6zGv4-qVJfaUn1i77Pw@mail.gmail.com
Whole thread Raw
In response to Re: Postgres: Queries are too slow after upgrading to PG17 from PG15  (Todd Cook <cookt@blackduck.com>)
List pgsql-bugs
Tree view 
On Fri, Sep 26, 2025 at 8:30 AM Todd Cook <cookt@blackduck.com> wrote:
> Thanks for confirming.  We can develop a strategy for working around
> this effect, so from my point of view, we can consider this matter
> resolved.  I'm guessing that you feel the same way, but if not, I'm
> happy to help out in any way I can.

Yes, I do feel the same way.

I'm going to withdraw my proposed patch, at least for now. If there's
another complaint along the same lines at some point in the future,
then I'll certainly need to reconsider my patch.

--
Peter Geoghegan

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19066: postgresql-18.0/src/backend/optimizer/geqo/geqo_ox2.c:86: Array index check in wrong place ?
Next
From: PG Bug reporting form
Date:
Subject: BUG #19067: On master at commit 66cdef4425f3, "psql -c 'select 1' dbname" causes the backend to seg fault