public inbox for [email protected]  

help / color / mirror / Atom feed

From: [email protected]
To: David G. Johnston <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: Yura Sokolov <[email protected]>
Cc: [email protected]
Subject: Re: When IMMUTABLE is not.
Date: Thu, 15 Jun 2023 10:25:46 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwbcsPwm_iiE8p5TYZ=2AEnt4LHpCnjjHYoCRAuZk9tzFw@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<CAKFQuwbcsPwm_iiE8p5TYZ=2AEnt4LHpCnjjHYoCRAuZk9tzFw@mail.gmail.com>

On 2023-06-15 10:19, David G. Johnston wrote:
> 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.

That was the view I ultimately took, and just made PL/Java suppress that
SPI readonly flag when going to look for the function code.

Until that change, you could run into the not-uncommon situation
where you've just loaded a jar of new functions and try to use them
in the same transaction, and hey presto, the VOLATILE ones all work,
and the IMMUTABLE ones aren't there yet.

Regards,
-Chap

view thread (10+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: When IMMUTABLE is not.
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox