Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vs1lt-001Q3F-1O for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Feb 2026 16:48:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vs1lq-0043dg-2z for pgsql-bugs@arkaria.postgresql.org; Mon, 16 Feb 2026 16:48:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vs1lq-0043dS-2B for pgsql-bugs@lists.postgresql.org; Mon, 16 Feb 2026 16:48:26 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vs1lm-00000000v8X-23iP for pgsql-bugs@lists.postgresql.org; Mon, 16 Feb 2026 16:48:24 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 61GGmJbB1133170; Mon, 16 Feb 2026 11:48:19 -0500 From: Tom Lane To: Andrew Dunstan cc: lucio.chiessi@trustly.com, pgsql-bugs@lists.postgresql.org, Florents Tselai Subject: Re: BUG #19409: Function jsonb_strip_nulls() changed from immutable to stable. In-reply-to: References: <19409-e16cd2605e59a4af@postgresql.org> <562481.1771013899@sss.pgh.pa.us> Comments: In-reply-to Andrew Dunstan message dated "Mon, 16 Feb 2026 11:18:28 -0500" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1133168.1771260499.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 16 Feb 2026 11:48:19 -0500 Message-ID: <1133169.1771260499@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrew Dunstan 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. regards, tom lane