Re: pgsql: Allow tailoring of ICU locales with custom rules - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: pgsql: Allow tailoring of ICU locales with custom rules
Date
Msg-id CAA4eK1JLBx18GJyAQ8nv-bnEDqEgmpgSVQtadV_wcSfbQZOs5Q@mail.gmail.com
Whole thread Raw
In response to Re: pgsql: Allow tailoring of ICU locales with custom rules  (Peter Eisentraut <peter.eisentraut@enterprisedb.com>)
Responses Re: pgsql: Allow tailoring of ICU locales with custom rules
List pgsql-hackers
On Fri, Mar 10, 2023 at 3:24 PM Peter Eisentraut
<peter.eisentraut@enterprisedb.com> wrote:
>
> On 08.03.23 21:57, Jeff Davis wrote:
>
> > * It appears rules IS NULL behaves differently from rules=''. Is that
> > desired? For instance:
> >    create collation c1(provider=icu,
> >      locale='und-u-ka-shifted-ks-level1',
> >      deterministic=false);
> >    create collation c2(provider=icu,
> >      locale='und-u-ka-shifted-ks-level1',
> >      rules='',
> >      deterministic=false);
> >    select 'a b' collate c1 = 'ab' collate c1; -- true
> >    select 'a b' collate c2 = 'ab' collate c2; -- false
>
> I'm puzzled by this.  The general behavior is, extract the rules of the
> original locale, append the custom rules, use that.  If the custom rules
> are the empty string, that should match using the original rules
> untouched.  Needs further investigation.
>
> > * Can you document the interaction between locale keywords
> > ("@colStrength=primary") and a rule like '[strength 2]'?
>
> I'll look into that.
>

This thread is listed on PostgreSQL 16 Open Items list. This is a
gentle reminder to see if there is a plan to move forward with respect
to open points.

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Richard Guo
Date:
Subject: Re: postgres_fdw: wrong results with self join + enable_nestloop off
Next
From: Richard Guo
Date:
Subject: Re: Assert failure on bms_equal(child_joinrel->relids, child_joinrelids)