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 23477.1568473993@sss.pgh.pa.us
Whole thread Raw
In response to Re: Create collation reporting the ICU locale display name  ("Daniel Verite" <daniel@manitou-mail.org>)
Responses Re: Create collation reporting the ICU locale display name
List pgsql-hackers
"Daniel Verite" <daniel@manitou-mail.org> writes:
>     Tom Lane wrote:
>> I think that's a useful function, but it's a different function from
>> the one first proposed, which was to tell you the properties of a
>> collation you already installed (which might not be ICU, even).
>> Perhaps we should have both.

> The pre-create use case would look  like:
>  SELECT * FROM describe_collation(locale_string text, collprovider "char")

> Post-creation, one could do:
>  SELECT * FROM describe_collation(collcollate, collprovider)
>    FROM pg_catalog.pg_collation WHERE oid = :OID;

> Possibly it could exists as SELECT * FROM describe_collation(oid)
> but that's essentially the same function.

The advantage of describe_collation(oid) is that we would not be
building knowledge into the callers about which columns of pg_collation
matter for this purpose.  I'm not even convinced that the two you posit
here are sufficient --- the encoding seems relevant, for instance.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Improve performance of NOTIFY over many databases (v2)
Next
From: Jeff Davis
Date:
Subject: Re: Add "password_protocol" connection parameter to libpq