Re: ICU Collations and Collation Updates
От | Paul Foerster |
---|---|
Тема | Re: ICU Collations and Collation Updates |
Дата | |
Msg-id | 23A7395F-6134-4D9E-8489-8F3BCE49E156@gmail.com обсуждение исходный текст |
Ответ на | Re: ICU Collations and Collation Updates (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: ICU Collations and Collation Updates
|
Список | pgsql-general |
Hi Tom, hi Laurenz > On 14 Apr 2025, at 16:36, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > 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 theSLES 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 tonever change it again (beside from recompiling of course), even when building new PostgreSQL versions, I'd very much appreciateif if you could let me know how I would do that. The necessity for reindex is a huge problem for us. Cheers, Paul
В списке pgsql-general по дате отправления: