On Thu, 26 Mar 2026 at 10:25, Matthias van de Meent
<boekewurm+postgres@gmail.com> wrote:
> I'm happy to mark this function as STABLE for now (to prevent its
> inclusion in permanent storage), and/or to adjust the code to adjust
> for subnormal inputs (values with incorrect/inconsistent/unexpected
> sign extensions).
You lost me at this part. How does marking the function as STABLE
prevent users from persisting things on disk based on the return value
of the function? I expected the primary use case for this would be in
trigger functions that make decisions about data that goes into
tables.
David
