Message-ID: <e9eb5136fb60188fc61c110e9706709fc13638e0.camel@cybertec.at>
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does
 not return in Postgresql 17
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: lowell.hought@gmail.com, pgsql-bugs@lists.postgresql.org
Date: Sun, 08 Jun 2025 02:27:31 +0200
In-Reply-To: <18950-010424f049268487@postgresql.org>
References: <18950-010424f049268487@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.2 (3.56.2-1.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/e9eb5136fb60188fc61c110e9706709fc13638e0.camel%40cybertec.at>
Precedence: bulk

On Sat, 2025-06-07 at 16:08 +0000, PG Bug reporting form wrote:
> PostgreSQL version: 17.5
> Operating system:   Red Hat Enterprise Linux release 8.10 (Ootpa)
>=20
> A pgsql function that returns Table is relatively simple.  It accepts two
> arguments; a date and an interval.  It uses these to arguments in a query
> that returns a result set.  This function worked in Postgresql 16.1 and
> Postgresql 16.9.  However, it does not work in versions 17.0 nor in 17.5
>=20
> [function definition]
>=20
> This is the first time I have ever encountered a bug and so I have no
> experience with reporting it.

Your function essentially is running a query.
If you run that query outside of the function, does it finish on time?
If not, you have a simpler problem to tackle.

It need not necessarily be a bug if some queries perform worse in a later
PostgreSQL version.  There are too many factors involved in the execution
of a complicated query.  To give help, we'd need at least the EXPLAIN
output from the query and the EXPLAIN (ANALYZE, BUFFERS) output from the
query on the old version.

Yours,
Laurenz Albe