Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From: "Daniel Verite" <daniel@manitou-mail.org>
Subject: Re: BUG #19425: Parametric settings in collation not working in rule
 syntax
To: dorian.752@live.fr,pgsql-bugs@lists.postgresql.org
In-Reply-To: <19425-58915e19dacd4f40@postgresql.org>
Date: Thu, 05 Mar 2026 12:34:32 +0100
Message-Id: <0cf43ecb-90d0-4eb2-8dd7-f5d60ba2b009@manitou-mail.org>
Archived-At: <https://www.postgresql.org/message-id/0cf43ecb-90d0-4eb2-8dd7-f5d60ba2b009%40manitou-mail.org>
Precedence: bulk

	PG Bug reporting form wrote:

> But, I also want to add a tailoring rule. For the simplicity we will say
> that I want to add 'p < q'
> CREATE COLLATION IF NOT EXISTS und_ci_ai2(
>     provider =3D icu,
>     locale =3D 'und-u-ka-shifted-kc-false-ks-level1',
>     deterministic =3D false,
>     rules =3D $$
>         & 'p' < 'q'
>     $$
> );
>=20
> But, and this is my problem, the previous request doesn't seem to work
> anymore. It doesn't return '1' :

This looks the same as bug #18771 discussed at
https://www.postgresql.org/message-id/flat/18771-98bb23e455b0f367%40postgre=
sql.org
and
https://www.postgresql.org/message-id/spHSrzQa0K_-Sqq9rNK-d6kelbfJG-z4XP6vn=
8tliiCHmjNYy45g2QOD92mrsNYqBpvj8Fi-qw4kXZhZmKjSVevzRSOvh6XzcNZBIV5wA3E=3D@p=
rotonmail.com

There's a simple fix available at
https://commitfest.postgresql.org/patch/6084/

Hopefully it will make it into the next major release, but so far it has be=
en
lacking
reviews.
If you're able to compile Postgres, you may test the fix with your case and
report on
the results.


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