public inbox for [email protected]
help / color / mirror / Atom feedFrom: Andrew Dunstan <[email protected]>
To: [email protected]
Subject: pgsql: Fix the volatility setting of json{b}_strip_nulls
Date: Wed, 18 Feb 2026 15:34:44 +0000
Message-ID: <[email protected]> (raw)
Fix the volatility setting of json{b}_strip_nulls
Commit 4603903d294 unfortunately reset the volatility of these functions
to STABLE whereas they had previously been set to IMMUTABLE. We can't
force a catalog update in the stable release, although a pg_update would
probably do the trick. A simpler fix, though, for affected users is
probably a simple catalog surgery along the lines of:
UPDATE pg_proc SET provolatile = 'i' WHERE oid in (3261,3262);
Applied to 18 only. In master we are planning to get rid of the separate
redeclarations for defaults in system_functions.sql.
Bug: #19409
Reported-By: Lucio Chiessi <[email protected]>
Discussion: https://postgr.es/m/[email protected]
Branch
------
REL_18_STABLE
Details
-------
https://git.postgresql.org/pg/commitdiff/2f6ee7b389c2b570ac55eb25273872b729d397c8
Modified Files
--------------
src/backend/catalog/system_functions.sql | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
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]
Subject: Re: pgsql: Fix the volatility setting of json{b}_strip_nulls
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