Postgres Pro
Downloads
Home   >   mailing lists

Re: ISN extension - wrong volatility level for isn_weak() function - Mailing list pgsql-bugs

From Viktor Holmberg
Subject Re: ISN extension - wrong volatility level for isn_weak() function
Date
Msg-id c8b28acd-2d6e-4653-a03b-7041cf5e0be3@Spark
Whole thread Raw
In response to Re: ISN extension - wrong volatility level for isn_weak() function  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-bugs
Tree view
Yes, you’re right Daniel. I ended up settling on the following workaround:

ALTER FUNCTION isn_weak() VOLATILE;
ALTER FUNCTION public.isn_weak(boolean) VOLATILE;

/Viktor Holmberg
On 14 Mar 2025 at 13:30 +0000, Daniel Gustafsson <daniel@yesql.se>, wrote:
On 14 Mar 2025, at 12:49, Viktor Holmberg <v@viktorh.net> wrote:

Hello. Apologies if this is not the right place to bug report extensions

For an extension bundled in postgres contrib it's absolutely the right place.

The isn_weak function in the isn extension reports the wrong value if you look at it inside a transaction:

I can manually fix this by changing it to STABLE:

ALTER FUNCTION isn_weak() STABLE;

Am I missing something or isn’t this quite weird? Would it at least be possible to change the documentation to explain this?

I wonder if this should really be marked VOLATILE instead as it has a side
effect.

--
Daniel Gustafsson

pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: BUG #18847: Different Query Results with and without a Primary Key Constraint
Next
From: Tom Lane
Date:
Subject: Re: BUG #18845: DEREF_OF_NULL.RET guc_malloc possibly returns NULL