Re: CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it?

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it?
Date: 2017-09-29 23:38:00
Message-ID: CAH2-Wz=REBtBRLDXeFYuZW=84Or5H2jmRBwd_ve1Wijy308HfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 25, 2017 at 11:40 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> Reading over this code again, it is admittedly not quite clear why this
> "canonicalization" is in there right now. I think it had something to
> do with how we built the keyword variants at one point. It might not
> make sense. I'd be glad to take that out and use the result straight
> from uloc_getAvailable() for collcollate. That is, after all, the
> "canonical" version that ICU chooses to report to us.

Is anything going to happen here ahead of shipping v10? This remains
an open item.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-09-29 23:42:02 64-bit queryId?
Previous Message Peter Geoghegan 2017-09-29 23:36:55 Re: Parallel tuplesort (for parallel B-Tree index creation)