Feedback-ID: i7c334307:Fastmail
Content-Type: multipart/signed;
	boundary="Apple-Mail=_2D51C93B-29B3-42D3-89B1-CBA5791EED8C";
	protocol="application/pgp-signature";
	micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.600.51.1.1\))
Subject: Re: PATCH: jsonpath string methods: lower, upper, initcap, l/r/btrim,
 replace, split_part
From: "David E. Wheeler" <david@justatheory.com>
In-Reply-To: <2568904.1748022721@sss.pgh.pa.us>
Date: Sat, 24 May 2025 12:08:18 -0400
Cc: Florents Tselai <florents.tselai@gmail.com>,
 Peter Eisentraut <peter@eisentraut.org>,
 Robert Haas <robertmhaas@gmail.com>,
 Alexander Korotkov <aekorotkov@gmail.com>,
 pgsql-hackers <pgsql-hackers@lists.postgresql.org>,
 Andrew Dunstan <andrew@dunslane.net>
Message-Id: <D57D3B5E-AF55-4F7F-9E55-FE06EE8ED811@justatheory.com>
References: 
 <CA+v5N40sJF39m0v7h=QN86zGp0CUf9F1WKasnZy9nNVj_VhCZQ@mail.gmail.com>
 <145894.1727298237@sss.pgh.pa.us>
 <CAPpHfdtGhn_5jfLoepOScyqT+FXYB9QtV-OEprychDcMJco7mw@mail.gmail.com>
 <CA+v5N42PVJH3HbwLE1yC75XR6E5zGnCCdtSUXfgFwtGyPP8XYg@mail.gmail.com>
 <CA+Tgmob03B6h1SMsi7vs9uOX+vrqg_tyhh--mKC3BaTJ08qKYA@mail.gmail.com>
 <7e9debe6-4e96-4b0d-a801-b531e962ef43@eisentraut.org>
 <01DC1C38-0692-461B-AA63-5394330356BE@gmail.com>
 <2568904.1748022721@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/D57D3B5E-AF55-4F7F-9E55-FE06EE8ED811%40justatheory.com>
Precedence: bulk


--Apple-Mail=_2D51C93B-29B3-42D3-89B1-CBA5791EED8C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On May 23, 2025, at 13:52, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>> I assume you mean that they=E2=80=99re set at initdb time, so =
there=E2=80=99s no mutability concern?=20
>=20
> Yeah, I think Peter's right and I'm wrong.  Obviously this ties into
> our philosophical debate about how immutable is immutable.  But as
> long as the functions only depend on locale settings that are fixed
> at database creation, I think it's okay to consider them immutable.
>=20
> If you were, say, depending on LC_NUMERIC, it would clearly be unsafe
> to consider that immutable, so I'm not quite sure if this is the end
> of the discussion.  But for what's mentioned in the thread title,
> I think we only care about LC_CTYPE.

Oh, so maybe all this is moot, and Florents can go ahead and add support =
for the functions to the non-_tz functions?

Should there be some sort of inventory of what functions can be used in =
what contexts?

D


--Apple-Mail=_2D51C93B-29B3-42D3-89B1-CBA5791EED8C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEd+KfmbOQis6ZycGGkt9idPjIgfEFAmgx7vIACgkQkt9idPjI
gfFkLg//Q95RuWjqneyFR41SQTY/QK0T8rg5k8/m3A3q60iQytjb1RmJOjsJbBiB
FfQUof8Yvwo/I4n3uhfAPjHjJ7Kn+eRQ05EF8WFjLooi0SIOddGxs/JKacYjhMOo
dGG9R0zvi7/QdsDaRWsgBJD3ARe0iM5SM/ZlSDey5oc2J3j9ksfgqXyIGr6+fmcD
/Y8NCaqYbhhzJBy8oYJY6oaG6GU4rTIOCebU5epaycJikQ2xxAKMIM9JAGwCEB3z
jI4yuDWMb0oiNrlekyGrmsegdaddDsGjdxKk9V3iqnI9Ia7jwIQ4LCzgwGz7iexf
piXr+fWsm6OXuUkv2QokQujdpj9iZPWj9+5TWST6uLDMK1GxXAj7jZaZU4LQvAax
YJZY6eGfQ6fkKqzYOukdUa3pjW57SU0bJug3w6I8gHyxAamfgNo4Y+9PfbEu92oe
qwdvbUcC1YKtzMGscqAm+UL3yvh6qhRuMkDlOnE8Yos+XkHkPbORaojD5pbk6oHL
nSK7yZLWwjCoJ30Eo/Vsq9eigx3iaxOSQ/BFEbo9Q0uA+rj9NZf7qxCKcnb+NiLS
51CAaKJXvgYsEOeZ1fu8d2aDGWKrMLFCj9OVbPDKYfeOsjlYxCTyNF9+a6qxfV2C
J+5+FEKCY8wAH2srETqtUCItgctlYnLNcZxhdFtMGfwcw2e1SMk=
=bbV/
-----END PGP SIGNATURE-----

--Apple-Mail=_2D51C93B-29B3-42D3-89B1-CBA5791EED8C--