| From: | Paul Foerster <paul(dot)foerster(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | glibc updarte 2.31 to 2.38 |
| Date: | 2024-09-19 14:37:41 |
| Message-ID: | B927CE6F-0A36-4237-BD4D-75CD609F3E89@gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
we have SLES 15.5 which has glibc 2.31. Our admin told us that he's about 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 we have some special requirements which the packages cannot fulfill. So I have questions:
1) Do I have to build it again on 15.6?
2) Does the glibc update have any impact? I recall having to have everything reindexed when the 2.28 update came due to major locale changes, but I didn't have to do it since then.
3) Where and how can I find out if it is necessary to reindex? And how can I find out what indexes would be affected.
I'd really appreciate your comments. Thanks very much in advance.
Paul
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-09-19 15:00:52 | Re: glibc updarte 2.31 to 2.38 |
| Previous Message | Lok P | 2024-09-19 13:12:45 | Re: How batch processing works |