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>
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-22 08:50:01
Message-ID: 10f5700f-0483-deb0-ba9a-c61c2d259425@proxel.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09/21/2017 10:55 PM, Peter Geoghegan wrote:
> I agree, but the bigger issue is that we're *half way* between
> supporting only one format, and supporting two formats. AFAICT, there
> is no reason that we can't simply support one format on all ICU
> versions, and keep what ends up within pg_collation at initdb time
> essentially the same across ICU versions (except for those that are
> due to cultural/political developments).

I think we are in agreement then, but I do not have the time to get this
done before the release of 10 so would be happy if you implemented it.
Peter E, what do you say in this?

Andreas

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Moser 2017-09-22 08:51:12 Re: [PROPOSAL] Temporal query processing with range types
Previous Message Ashutosh Bapat 2017-09-22 08:33:14 Re: Partition-wise join for join between (declaratively) partitioned tables