From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff Davis <pgsql@j-davis.com>
cc: pgsql-hackers@postgresql.org
Subject: Re: ICU 54 and earlier are too dangerous
In-reply-to: <ea927ede4e8a8f3ba515b15a083577a68e9f9201.camel@j-davis.com>
References: <ea927ede4e8a8f3ba515b15a083577a68e9f9201.camel@j-davis.com>
Comments: In-reply-to Jeff Davis <pgsql@j-davis.com>
	message dated "Mon, 13 Mar 2023 16:39:04 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2453426.1678753577.1@sss.pgh.pa.us>
Date: Mon, 13 Mar 2023 20:26:17 -0400
Message-ID: <2453427.1678753577@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2453427.1678753577%40sss.pgh.pa.us>
Precedence: bulk

Jeff Davis <pgsql@j-davis.com> writes:
> In ICU 54 and earlier, if ucol_open() is unable to find a matching
> locale, it will fall back to the *environment*.

That's not great, but ...

> Unless someone has a better idea, I think we need to bump the minimum
> required ICU version to 55. That would solve the issue in v16 and
> later, but those using old versions of ICU and old versions of postgres
> would still be vulnerable to these kinds of typos.

... that seems like an overreaction.  We know from the buildfarm
that there's still a lot of old ICU out there.  Is it really improving
anybody's life to try to forbid them from using such a version?

			regards, tom lane