From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Daniel Verite <daniel(at)manitou-mail(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Create collation reporting the ICU locale display name |
Date: | 2019-09-12 19:03:43 |
Message-ID: | 10557.1568315023@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> I wonder if INFO is better than NOTICE (I think it is).
You're just waving a red flag in front of a bull, you know.
I don't especially like the idea of having this emit a NOTICE;
it's ugly and in-your-face. INFO is right out.
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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-09-12 19:31:11 | Re: psql - add SHOW_ALL_RESULTS option |
Previous Message | Peter Eisentraut | 2019-09-12 18:59:54 | Re: another look at macOS SIP |