public inbox for [email protected]
help / color / mirror / Atom feedRe: ICU Collations and Collation Updates
2+ messages / 2 participants
[nested] [flat]
* Re: ICU Collations and Collation Updates
@ 2025-04-14 17:24 Paul Foerster <[email protected]>
0 siblings, 1 reply; 2+ messages in thread
From: Paul Foerster @ 2025-04-14 17:24 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: Cybertec Schönig & Schönig GmbH <[email protected]>; Thomas Michael Engelke <[email protected]>; [email protected]
Hi Tom, hi Laurenz
> On 14 Apr 2025, at 16:36, Tom Lane <[email protected]> wrote:
>
> Laurenz Albe <[email protected]> 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
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: ICU Collations and Collation Updates
@ 2025-04-14 17:36 Laurenz Albe <[email protected]>
parent: Paul Foerster <[email protected]>
0 siblings, 0 replies; 2+ messages in thread
From: Laurenz Albe @ 2025-04-14 17:36 UTC (permalink / raw)
To: Paul Foerster <[email protected]>; Tom Lane <[email protected]>; +Cc: Thomas Michael Engelke <[email protected]>; [email protected]
On Mon, 2025-04-14 at 19:24 +0200, Paul Foerster wrote:
> Hi Tom, hi Laurenz
> > On 14 Apr 2025, at 16:36, Tom Lane <[email protected]> wrote:
> >
> > Laurenz Albe <[email protected]> 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.
You cannot "bake in into" PostgreSQL, but you can grab the ICU source,
install it in /usr/local or similar and build PostgreSQL against that.
You will have to fiddle with CFLAGS and LDFLAGS so that the build process
uses the C headers and libraries from your build of the ICU library.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2025-04-14 17:36 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-04-14 17:24 Re: ICU Collations and Collation Updates Paul Foerster <[email protected]>
2025-04-14 17:36 ` Laurenz Albe <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox