Re: glibc updarte 2.31 to 2.38 - Mailing list pgsql-general

From Paul Foerster
Subject Re: glibc updarte 2.31 to 2.38
Date
Msg-id FBFC83A0-55B2-4812-B9F3-38D42D7A9A7C@gmail.com
Whole thread Raw
In response to Re: glibc updarte 2.31 to 2.38  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: glibc updarte 2.31 to 2.38
List pgsql-general
Hi Tom,

> On 19 Sep 2024, at 17:14, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> No, I wouldn't expect that to be necessary.

I was hoping one of the pros would say that. 🤣

> Maybe.  We don't really track glibc changes, so I can't say for sure,
> but it might be advisable to reindex indexes on string columns.

Advisable is a word I undfortunately can't do much with. We have terabytes and terabytes of data in hundreds of
databaseseach having potentially hundreds of columns that are candidates. Just reindexing and taking down applications
duringthat time is not an option in a 24x7 high availability environment. 

Cheer,
Paul




pgsql-general by date:

Previous
From: Paul Foerster
Date:
Subject: Re: glibc updarte 2.31 to 2.38
Next
From: Paul Foerster
Date:
Subject: Re: glibc updarte 2.31 to 2.38