From: Tom Lane <tgl@sss.pgh.pa.us>
To: Lowell Hought <lowell.hought@gmail.com>
cc: Laurenz Albe <laurenz.albe@cybertec.at>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18950: pgsql function that worked in Postgresql 16 does not
 return in Postgresql 17
In-reply-to: 
 <CAJtAGPpURGxCJRWVeFsPbu2fjtaSCwVsBNZ5_QW0wE5N6Z-N=Q@mail.gmail.com>
References: <e9eb5136fb60188fc61c110e9706709fc13638e0.camel@cybertec.at>
 <75D714EA-CD1E-4F80-A2E8-29E378EC2200@gmail.com>
 <81946.1749348479@sss.pgh.pa.us>
 <CAJtAGPpa4yYS6LLO5RHzwe9q7NpHiuuvEX1wVtErpie3EBWZJQ@mail.gmail.com>
 <CAJtAGPrcK_gp8FuEzp4tTbLKD1mqFGY5yDk0FX_1AGDjVJXAuw@mail.gmail.com>
 <CAJtAGPpeqrgKNHdWqr=uPu1_UwN_TAgUvN4cfcWOaRN8U+8zDA@mail.gmail.com>
 <89144.1749352271@sss.pgh.pa.us>
 <CAJtAGPpURGxCJRWVeFsPbu2fjtaSCwVsBNZ5_QW0wE5N6Z-N=Q@mail.gmail.com>
Comments: In-reply-to Lowell Hought <lowell.hought@gmail.com>
	message dated "Sat, 07 Jun 2025 22:16:54 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <90963.1749353175.1@sss.pgh.pa.us>
Date: Sat, 07 Jun 2025 23:26:15 -0400
Message-ID: <90964.1749353175@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/90964.1749353175%40sss.pgh.pa.us>
Precedence: bulk

Lowell Hought <lowell.hought@gmail.com> writes:
> I can try.  I am not sure how to go about that.  I did not see on the bug
> report page where I could upload files, and I am afraid the file size of
> the tables needed might be too large for email.

No, uploading stuff to that webform doesn't work.  But at this point
we're just conversing on the pgsql-bugs mailing list, so anything you
can squeeze into email is fine.  Having said that, nobody likes
multi-gigabyte emails.

> The entire database when
> written to an sql dump file is about 20 GB, so not terribly large.  I could
> attempt to dump the schema definition in one file and then the underlying
> tables in another.  Would that work?  Or would you also need the files for
> the function and any views the query relies upon?

Yeah, we'd need all the moving parts.

Usually people with this kind of problem don't want to expose their
data anyway, for privacy and/or legal reasons.  So what I'd suggest
is trying to create some little script that generates fake data
that's close enough to trigger the problem.  Then you just need to
provide that script and the DDL and function definitions.

			regards, tom lane