Re: Interesting case of IMMUTABLE significantly hurting performance

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Nico Williams <nico(at)cryptonector(dot)com>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Olleg Samoylov <splarv(at)ya(dot)ru>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Interesting case of IMMUTABLE significantly hurting performance
Date: 2025-04-11 04:13:37
Message-ID: CAKFQuwZ-cd6w5-EqM6m+T-W08TCzkS624=w5+gqeDT751_T+EA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thursday, April 10, 2025, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Merlin Moncure <mmoncure(at)gmail(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2025-04-11 05:15:44 Re: Interesting case of IMMUTABLE significantly hurting performance
Previous Message Daniel Westermann (DWE) 2025-04-11 03:57:03 Re: Meson and Numa: C header not found