| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org> |
| Cc: | Pgsql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow tailoring of ICU locales with custom rules |
| Date: | 2023-03-08 10:38:00 |
| Message-ID: | e861ac4fdae9f9f5ce2a938a37bcb5e083f0f489.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2023-03-07 at 22:06 -0800, Jeff Davis wrote:
> On Fri, 2023-03-03 at 13:45 +0100, Peter Eisentraut wrote:
> > You can mess with people by setting up your databases like this:
> >
> > initdb -D data --locale-provider=icu --icu-rules='&a < c < b < e < d'
> >
> > ;-)
>
> Would we be the first major database to support custom collation rules?
> This sounds useful for testing, experimentation, hacking, etc.
>
> What are some of the use cases? Is it helpful to comply with unusual or
> outdated standards or formats? Maybe there are people using special
> delimiters/terminators and they need them to be treated a certain way
> during comparisons?
I regularly see complaints about the sort order; recently this one:
https://postgr.es/m/CAFCRh--xt-J8awOavhB216kom6TQnaP35TTVEQQS5bHH7gMemQ@mail.gmail.com
So being able to influence the sort order is useful.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-03-08 10:53:13 | Re: Add pg_walinspect function with block info columns |
| Previous Message | Aleksander Alekseev | 2023-03-08 10:35:40 | Re: HOT chain validation in verify_heapam() |