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

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Peter Geoghegan <pg(at)bowt(dot)ie>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, 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-19 22:23:10
Message-ID: ad8510ba-3350-d574-91e5-b2aa55faab47@proxel.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/19/2017 11:32 PM, Peter Geoghegan wrote:
> On Tue, Sep 19, 2017 at 2:22 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Well, if PG10 shipped with that restriction in place then it wouldn't
>> be an issue ;-)
>
> I was proposing that this be treated as an open item for v10; sorry if
> I was unclear on that. Much like the "ICU locales vs. ICU collations
> within pg_collation" issue, this seems like the kind of thing that we
> ought to go out of our way to get right in the *first* version.

If people think it is possible to get this done in time for PostgreSQL
10 and it does not break anything on older version of ICU (or the
migration from older versions) I am all for it.

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2017-09-19 22:29:14 Re: [PATCH] Assert that the correct locks are held when calling PageGetLSN()
Previous Message Jeff Janes 2017-09-19 21:55:52 Re: SCRAM in the PG 10 release notes