Feedback-ID: i7c334307:Fastmail
Content-Type: multipart/signed;
	boundary="Apple-Mail=_912F3FCE-7FEE-48A8-8D74-944C56CC8A3A";
	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: <4904EA5B-C6CA-42BD-BF08-C89325240C9D@gmail.com>
Date: Thu, 10 Jul 2025 14:13:13 -0400
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 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: <84727E10-62B7-4FE4-B487-E7044C7C0A1F@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>
 <D57D3B5E-AF55-4F7F-9E55-FE06EE8ED811@justatheory.com>
 <40912112-7FFE-400F-A38F-368827C4BDF1@gmail.com>
 <D201EEF7-8681-458E-B287-7B8F058DC712@justatheory.com>
 <176C517D-2DEB-4CAB-9AE4-261079D313B9@justatheory.com>
 <8FD5F4CF-9059-40C1-9F0A-C3CBA8DFE17A@justatheory.com>
 <C54B0664-34F5-46E2-9094-5798E68A2A3F@justatheory.com>
 <696ECBBC-3CBF-4522-AE66-E48225688E93@gmail.com>
 <59C63857-406D-4704-A1EB-9BF3AA639C86@justatheory.com>
 <06FA8975-2E21-46A5-B510-028B3B967EB2@justatheory.com>
 <2F58E05D-D319-4CD3-8805-E1A8A2482A1A@justatheory.com>
 <4A96ACDB-78A1-4434-8C25-7C9716A7D421@justatheory.com>
 <A7D78196-E287-4716-8507-BE09C6DE3C82@justatheory.com>
 <4904EA5B-C6CA-42BD-BF08-C89325240C9D@gmail.com>
To: Florents Tselai <florents.tselai@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/84727E10-62B7-4FE4-B487-E7044C7C0A1F%40justatheory.com>
Precedence: bulk


--Apple-Mail=_912F3FCE-7FEE-48A8-8D74-944C56CC8A3A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jul 10, 2025, at 13:41, Florents Tselai <florents.tselai@gmail.com> =
wrote:

> The basic problem I see with these latest revisions/refactorings is =
that they fail for pg_upgrade afaict.
> Probably this means that some of the rearrangements on the =
parser/scanner are not that flexible.

Oh, is that what=E2=80=99s happening? What needs to happen to properly =
support pg_upgrade?

Best,

David


--Apple-Mail=_912F3FCE-7FEE-48A8-8D74-944C56CC8A3A
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+KfmbOQis6ZycGGkt9idPjIgfEFAmhwArkACgkQkt9idPjI
gfGUOxAAjIDaksqD80Jid2tWVpRu/pCk+7R1oL7dnqoG6MsuuS7McPd879kHmHsM
l75ssmCW9FASPyIp2cCKba+mwk7YwyzgTeEj5uGwglFNs/NdEbY2qfNGBKVxNLsO
XISPfYWxI7cATY5/ynWn0fvXl7LXjRQ3MzWPJUnhCDkJtSOdWExhJDQCBKbdg9x+
kqF0xGZoQWOL0w4h38MTHDi/Xwe3aUV+otS5FgUAhT85dcEaV1fJAaZhISlGzWeG
N3v7jlcVYc46IdEl7YRMCRrJm8tawumvTA4MTbwAY/kNRxG+PIQKZLvXKZ9Njpnq
JXP4BW4b99p5+xJObOO+Pa1AArvihRc/EfHRwj+RrR2Q2TuGtT/iJnVc409B5lYu
4BrmDEz4PCJOt/yTLhJe++xD2y/pqrRzcdr8rZjE0GZJx+5M5Xi0ES/nOwaHmdV5
WcLrRXaFZJZLF063e75v3bHk/FXkWgEIRgRqU4nLIdEFYLa+CrTYmYScRuPm9XoS
gLj7C07B3zi+5c536sVdf1tHpb5pLMNhBWVYy//KwWK/gHIsQwuP1XzSPiMnXYdl
13KJgodyisrVImuiH93mh4BLNPUJ2xzfaTu9mohZ+YunAmp3JtxfcRYiqa6Klv2y
vvshWhHqeVLDn/XwmwMcFfYFRY6Q3ioRPLYAThqhxDcGp+DYfuY=
=NAyD
-----END PGP SIGNATURE-----

--Apple-Mail=_912F3FCE-7FEE-48A8-8D74-944C56CC8A3A--