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

From Tom Lane
Subject Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47 language tags. Should it?
Date
Msg-id 2893.1505856178@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?  (Andreas Karlsson <andreas@proxel.se>)
Responses Re: [HACKERS] CREATE COLLATION does not sanitize ICU's BCP 47language tags. Should it?
List pgsql-hackers
Andreas Karlsson <andreas@proxel.se> writes:
> Hm, I like the idea but I see some issues.

> Enforcing the BCP47 seems like a good thing to me. I do not see any 
> reason to allow input with syntax errors. The issue though is that we do 
> not want to break people's databases when they upgrade to PostgreSQL 11. 
> What if they have specified the locale in the old non-ICU format or they 
> have a bogus value and we then error out on pg_upgrade or pg_restore?

Well, if PG10 shipped with that restriction in place then it wouldn't
be an issue ;-)
        regards, tom lane


-- 
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: "David G. Johnston"
Date:
Subject: Re: [HACKERS] Re: issue: record or row variable cannot be part ofmultiple-item INTO list
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Show backtrace when tap tests fail