Re: [HACKERS] What users can do with custom ICU collations inPostgres 10 - Mailing list pgsql-hackers

From Craig Ringer
Subject Re: [HACKERS] What users can do with custom ICU collations inPostgres 10
Date
Msg-id CAMsr+YHEr=NFJnu5K+Y1nz4k4MD1R6pnQ0PSnRyb4sUWDgp7xQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] What users can do with custom ICU collations inPostgres 10  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On 15 August 2017 at 10:16, Michael Paquier <michael.paquier@gmail.com> wrote:
On Tue, Aug 15, 2017 at 11:10 AM, Craig Ringer <craig@2ndquadrant.com> wrote:
> Ooh, this finally gives us a path toward case-insensitive default database
> collation via CLDR caseLevel.
>
> http://userguide.icu-project.org/collation
> http://www.unicode.org/reports/tr35/tr35-collation.html#Algorithm_Case
>
> That *definitely* should be documented and exposed by initdb.

The addition of an interface to initdb smells like an item for v11~,
but the documentation for 10 could be improved in this sense?

Yeah, not suggesting changing it for Pg10, way too late.

It's also not enough for case-insensitive DB by its self, since we still do binary compares for equality. There'd need to be deeper surgery to make it work. So I'm getting prematurely excited here.

--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Explicit relation name in VACUUM VERBOSE log
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] SQL/JSON in PostgreSQL