Re: Create collation reporting the ICU locale display name

From: "Daniel Verite" <daniel(at)manitou-mail(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>,"Michael Paquier" <michael(at)paquier(dot)xyz>,"Alvaro Herrera" <alvherre(at)2ndquadrant(dot)com>,"PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Create collation reporting the ICU locale display name
Date: 2019-09-14 13:23:04
Message-ID: 75be1069-c546-4a2f-862e-099bec18992c@manitou-mail.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
Or I'm missing something about why we'd need two functions.

Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: http://www.manitou-mail.org
Twitter: @DanielVerite

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Verite 2019-09-14 13:51:03 Re: Create collation reporting the ICU locale display name
Previous Message Fabien COELHO 2019-09-14 13:05:21 Re: pgbench - allow to create partitioned tables