| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Daniel Verite <daniel(at)manitou-mail(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| Date: | 2017-08-09 21:29:09 |
| Message-ID: | CAH2-Wzm18GG_1by_pYRLg3npoxTBUW2=oxZDtVmaqKteZWaybw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Aug 9, 2017 at 2:26 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Geoghegan <pg(at)bowt(dot)ie> writes:
>> It would help if CREATE COLLATION left new
>> ICU collations with the same useful "Description" as initdb created
>> collations will have; maybe that should be added.
>
> I do not think it is CREATE COLLATION's job to provide a comment;
> no other CREATE command does so.
It's not a comment. It's a description that comes from ICU. Just like
when collations are added by initdb, so that there is some kind of
parity. The user doesn't get a say in what it is.
It helps the user to verify that they're getting what they thought
they were, which seems very valuable, given how loosely the 'locale'
string they provide may be interpreted.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-08-10 00:20:30 | Re: [BUGS] Replication to Postgres 10 on Windows is broken |
| Previous Message | Tom Lane | 2017-08-09 21:26:01 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2017-08-09 22:49:41 | What users can do with custom ICU collations in Postgres 10 |
| Previous Message | Tom Lane | 2017-08-09 21:26:01 | Re: Crash report for some ICU-52 (debian8) COLLATE and work_mem values |