From: Tom Lane <tgl@sss.pgh.pa.us>
To: Paul Foerster <paul.foerster@gmail.com>
cc: pgsql-general list <pgsql-general@lists.postgresql.org>
Subject: Re: glibc updarte 2.31 to 2.38
In-reply-to: <B927CE6F-0A36-4237-BD4D-75CD609F3E89@gmail.com>
References: <B927CE6F-0A36-4237-BD4D-75CD609F3E89@gmail.com>
Comments: In-reply-to Paul Foerster <paul.foerster@gmail.com>
	message dated "Thu, 19 Sep 2024 16:37:41 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1991351.1726758874.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 19 Sep 2024 11:14:34 -0400
Message-ID: <1991352.1726758874@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/1991352.1726758874%40sss.pgh.pa.us>
Precedence: bulk

Paul Foerster <paul.foerster@gmail.com> writes:
> we have SLES 15.5 which has glibc 2.31. Our admin told us that he's abou=
t to install the SLES 15.6 update which contains glibc 2.38.
> I have built our PostgreSQL software from source on SLES 15.5, because w=
e have some special requirements which the packages cannot fulfill. So I h=
ave questions:

> 1) Do I have to build it again on 15.6?

No, I wouldn't expect that to be necessary.

> 2) Does the glibc update have any impact?

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.

			regards, tom lane