Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: Supporting non-deterministic collations with tailoring rules.
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Peter Eisentraut" <peter@eisentraut.org>
Cc: pgsql-hackers@lists.postgresql.org
In-Reply-To: <bbe2d768-d82b-4145-b5e4-a20c26a5b47c@eisentraut.org>
Date: Wed, 18 Mar 2026 19:21:52 +0100
Message-Id: <ee874a36-2e7f-459f-a3ee-11a3a739ab00@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/ee874a36-2e7f-459f-a3ee-11a3a739ab00%40manitou-mail.org>
Precedence: bulk

	Peter Eisentraut wrote:

> Ok, committed.
>=20
> Thoughts on backpatching?  Seems like a straightforward bug fix.

Thanks for pushing the patch!
I thought it was not a candidate for backpatching because it's
a collation change.
Now, to have a problem with that change in a minor release,
a user would need to have an ICU collation with a rule containing
"[strength N]", where N<>3, even though it was ineffective (so
either the user did not notice or they did but kept it
nonetheless). Users who reported the problem hoped for a backpatch,
but we cannot say there is zero risk with that change in a minor
release. Personally I'm +0.


Best regards,
--=20
Daniel V=E9rit=E9=20
https://postgresql.verite.pro/