Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it? - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?
Date
Msg-id ad8510ba-3350-d574-91e5-b2aa55faab47@proxel.se
Whole thread Raw
In response to Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?
List pgsql-hackers
On 09/19/2017 11:32 PM, Peter Geoghegan wrote:
> On Tue, Sep 19, 2017 at 2:22 PM, Tom Lane <tgl@sss.pgh.pa.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


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: [HACKERS] SCRAM in the PG 10 release notes
Next
From: Jacob Champion
Date:
Subject: Re: [HACKERS] [PATCH] Assert that the correct locks are held whencalling PageGetLSN()