Re: When IMMUTABLE is not.

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: "chap(at)anastigmatix(dot)net" <chap(at)anastigmatix(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: When IMMUTABLE is not.
Date: 2023-06-15 14:19:39
Message-ID: CAKFQuwbcsPwm_iiE8p5TYZ=2AEnt4LHpCnjjHYoCRAuZk9tzFw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday, June 15, 2023, <chap(at)anastigmatix(dot)net> wrote:

>
> So one could take a strict view that "no PL/Java function should
> ever be marked IMMUTABLE" because every one depends on fetching
> something (once, at least).
>

The failure to find and execute the function code itself is not a failure
mode that these markers need be concerned with. Assuming one can execute
the function an immutable function will give the same answer for the same
input for all time.

David J.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message chap 2023-06-15 14:25:46 Re: When IMMUTABLE is not.
Previous Message chap 2023-06-15 14:16:12 Re: When IMMUTABLE is not.