| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, 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 02:30:46 |
| Message-ID: | 20190914023046.GA15406@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 13, 2019 at 11:09:52AM -0400, 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.
Perhaps. Having a default description for the collations imported by
initdb is nice to have, but because of the gap with collations defined
after initialization it seems to me that there is an argument to
switch to that function for psql instead of grepping the default
description added to pg_description. Enforcing a comment for a
collation manually created based on what libicu tells us does not
feel right either, as we don't enforce a comment for the creation of
other objects.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-09-14 02:45:47 | Re: [HACKERS] CLUSTER command progress monitor |
| Previous Message | Andres Freund | 2019-09-14 01:38:31 | Re: refactoring - share str2*int64 functions |