Re: Interesting case of IMMUTABLE significantly hurting performance - Mailing list pgsql-general

From David G. Johnston
Subject Re: Interesting case of IMMUTABLE significantly hurting performance
Date
Msg-id CAKFQuwZ-cd6w5-EqM6m+T-W08TCzkS624=w5+gqeDT751_T+EA@mail.gmail.com
Whole thread Raw
In response to Re: Interesting case of IMMUTABLE significantly hurting performance  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Thursday, April 10, 2025, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Merlin Moncure <mmoncure@gmail.com> writes:
> I guess the real problems here are lack of feedback on a number of fronts:
> *) the server knows the function is not immutable but lets you create it
> anyway, even though it can have negative downstream consequences

That's debatable I think.  If you know what you're doing, you're going
to be annoyed by warnings telling you that you don't.

So long as you use atomic SQL functions I suspect it is possible to use the dependency data to get the volatility of the used functions and compare them to the volatility of the UDF.

David J.

pgsql-general by date:

Previous
From: "Daniel Westermann (DWE)"
Date:
Subject: Re: Meson and Numa: C header not found
Next
From: Laurenz Albe
Date:
Subject: Re: Interesting case of IMMUTABLE significantly hurting performance