Re: BUG #19425: Parametric settings in collation not working in rule syntax

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: dorian(dot)752(at)live(dot)fr,pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19425: Parametric settings in collation not working in rule syntax
Date: 2026-03-05 11:34:32
Message-ID: 0cf43ecb-90d0-4eb2-8dd7-f5d60ba2b009@manitou-mail.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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 = icu,
> locale = 'und-u-ka-shifted-kc-false-ks-level1',
> deterministic = false,
> rules = $$
> & 'p' < 'q'
> $$
> );
>
> 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%40postgresql.org
and
https://www.postgresql.org/message-id/spHSrzQa0K_-Sqq9rNK-d6kelbfJG-z4XP6vn8tliiCHmjNYy45g2QOD92mrsNYqBpvj8Fi-qw4kXZhZmKjSVevzRSOvh6XzcNZBIV5wA3E=@protonmail.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 been
lacking
reviews.
If you're able to compile Postgres, you may test the fix with your case and
report on
the results.

Best regards,
--
Daniel Vérité
https://postgresql.verite.pro/

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Nathan Bossart 2026-03-06 22:01:50 Re: Revoke Connect Privilege from Database not working
Previous Message Rafia Sabih 2026-03-05 01:01:34 Re: Two issues with REFRESH MATERIALIZED VIEW CONCURRENTLY