Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3826.500.181.1.5\))
Subject: Re: ICU Collations and Collation Updates
From: Paul Foerster <paul.foerster@gmail.com>
In-Reply-To: <1257278.1744641400@sss.pgh.pa.us>
Date: Mon, 14 Apr 2025 19:24:29 +0200
Cc: =?utf-8?Q?Cybertec_Sch=C3=B6nig_=26_Sch=C3=B6nig_GmbH?= <laurenz.albe@cybertec.at>,
 Thomas Michael Engelke <thomas.engelke@posteo.de>,
 pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <23A7395F-6134-4D9E-8489-8F3BCE49E156@gmail.com>
References: <8ed41c50ba6c5322296b869e497c1b5573853b54.camel@posteo.de>
 <d477c1faf35bad99fe550c8c4c1954ffa076ccfd.camel@cybertec.at>
 <1257278.1744641400@sss.pgh.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/23A7395F-6134-4D9E-8489-8F3BCE49E156%40gmail.com>
Precedence: bulk

Hi Tom, hi Laurenz

> On 14 Apr 2025, at 16:36, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>=20
> Laurenz Albe <laurenz.albe@cybertec.at> writes:
>> You would have to build PostgreSQL yourself with a fixed version of =
ICU
>> that you never upgrade if you want to avoid the problem.
[...]
> 2. It's at least *possible* to use your own fixed-version ICU
> library if you're desperate enough.  I don't think that would work
> too well for libc; you're stuck with what the platform provides.

That topic is interesting because I have a huge problem finding a =
downtime window for our applications to rebuild after the SLES upgrades. =
I am in the process of slowly changing everything to ICU. But limiting =
downtime is essential for me.

We always build the PostgreSQL software from source, so if there's a way =
to bake the libicu directly into the software to never change it again =
(beside from recompiling of course), even when building new PostgreSQL =
versions, I'd very much appreciate if if you could let me know how I =
would do that.

The necessity for reindex is a huge problem for us.

Cheers,
Paul=