| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Viktor Holmberg <v(at)viktorh(dot)net> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ISN extension - wrong volatility level for isn_weak() function |
| Date: | 2025-03-14 13:29:55 |
| Message-ID: | 51C655A4-46FB-4A40-BAE5-26A76B31D3EE@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 14 Mar 2025, at 12:49, Viktor Holmberg <v(at)viktorh(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-03-14 13:48:35 | Re: BUG #18846: Incorrect Filtering Behavior with FULL OUTER JOIN and WHERE Condition |
| Previous Message | Viktor Holmberg | 2025-03-14 11:49:06 | ISN extension - wrong volatility level for isn_weak() function |