Re: Create collation reporting the ICU locale display name - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Create collation reporting the ICU locale display name
Date
Msg-id 23501.1568349077@sss.pgh.pa.us
Whole thread Raw
In response to Re: Create collation reporting the ICU locale display name  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Michael Paquier <michael@paquier.xyz> writes:
> On Thu, Sep 12, 2019 at 03:03:43PM -0400, Tom Lane wrote:
>> The idea of having CREATE COLLATION automatically create a comment
>> is sort of interesting, although it seems pretty orthogonal to
>> normal command behavior.  I wonder whether the seeming need for
>> this indicates that we should add a descriptive field to pg_collation
>> proper, and not usurp the user-oriented comment feature for that.
>> 
>> The difficulty with localization is that whatever we put into
>> template1 has got to be ASCII-only, so that the template DB
>> can be copied to other encodings.  I suppose we could consider
>> having CREATE COLLATION act differently during initdb than
>> later, but that seems ugly too.

> Or could it make sense to provide a system function which returns a
> collation description for at least an ICU-provided one?  We could make
> use of that in psql for example.

Oh, that seems like a good way to tackle it.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: refactoring - share str2*int64 functions
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [PATCH] pageinspect function to decode infomasks