Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: lucio(dot)chiessi(at)trustly(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Florents Tselai <florents(dot)tselai(at)gmail(dot)com>
Subject: Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
Date: 2026-02-17 21:25:19
Message-ID: f4b67569-086e-4c22-a756-aab635fa01a7@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


On 2026-02-16 Mo 3:19 PM, Andrew Dunstan wrote:
>
>
> On 2026-02-16 Mo 11:48 AM, Tom Lane wrote:
>> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>>> In penance for this I have worked up a mechanism to generate
>>> default-setting statements from pg_proc.dat that I will post separately
>>> about in -hackers. In the meantime, I guess we should fix it in release
>>> 18 and master, with a release note that people might need to do a manual
>>> update if affected, along the lines of
>>>    update pg_proc set provolatile = 'i' where oid in (3261,3262);
>> Yeah, the $64 question is what to do in REL_18_STABLE. In master
>> we can commit this with a catversion bump, but we can't change
>> v18's catversion. I think I agree that we should just change v18's
>> system_functions.sql anyway. That will at least solve it for people
>> upgrading in future.
>
>
> OK, barring objections I will make that happen in a day or two.
>
>
>

In view of later discussions, fixing master seems pointless, as that
code is going away. When it does we should do a catversion bump.

So I'm just planning to patch v18 now.

cheers

andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2026-02-17 21:55:04 Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable.
Previous Message Matt Carter 2026-02-17 20:54:35 RE: BUG #19411: libpq 16.x exhibits a memory leak when connections are repeatedly created and destroyed