From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: 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
Date: Tue, 14 Mar 2023 08:25:55 +0100
Message-ID: <4006636a-134c-e096-2954-c8669d444b64@enterprisedb.com> (raw)
In-Reply-To: <2453427.1678753577@sss.pgh.pa.us>
References: <ea927ede4e8a8f3ba515b15a083577a68e9f9201.camel@j-davis.com>
<2453427.1678753577@sss.pgh.pa.us>
On 14.03.23 01:26, Tom Lane wrote:
>> 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?
If I'm getting the dates right, the 10-year support of RHEL 7 will
expire in June 2024. So if we follow past practices, we could drop
support for RHEL 7 in PG17. This would allow us to drop support for old
libicu, and also old openssl, zlib, maybe more.
So if we don't feel like we need to do an emergency change here, there
is a path to do this in a principled way in the near future.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@enterprisedb.com, tgl@sss.pgh.pa.us, pgsql@j-davis.com
Subject: Re: ICU 54 and earlier are too dangerous
In-Reply-To: <4006636a-134c-e096-2954-c8669d444b64@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox