pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Alexey Shishkin <alexey.shishkin@enterprisedb.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: OS system version upgrade (glibc / libicu version change)
Date: Wed, 28 Oct 2026 22:02:14 +0100
Message-ID: <b12f6d6c2c6ff9bb6a7f75a53a5d0f3adb68de67.camel@cybertec.at> (raw)
In-Reply-To: <CALVdoE5ne1EEvU29Y9_=rbiYb+M5xRbVuQ=PEZs33b6ze1+m8A@mail.gmail.com>
References: <177002326159.803.1983703962002247846@wrigleys.postgresql.org>
	<CALVdoE78O7Ksm+1ySLCv=Bs_-O5hHyQfXHEMaNC3dPP1t2WSQw@mail.gmail.com>
	<CALVdoE6syAWYPKCWJ7o4Vfaapw5Q316qjSx32QLmuyA+yrXEMw@mail.gmail.com>
	<225d52b51ed9a911ced2f8e6c00e089a1ce50f19.camel@cybertec.at>
	<CALVdoE5ne1EEvU29Y9_=rbiYb+M5xRbVuQ=PEZs33b6ze1+m8A@mail.gmail.com>

On Wed, 2026-10-28 at 14:32 +0100, Alexey Shishkin wrote:
> On the other hand it should not be only for PG20, but rather for all previous PG versions too.

Yes, perhaps.

> About the structure:
> - first, we should refer to Locale Providers chapter
> - then mention that icu/libc locale providers are backed by libicu/glibc libraries which
>   versions might change from time to time (even within the lifecycle of the same major version of OS)
> - libicu/glibc version changes might lead to changes of SQL-queries which use affected indexes, so
>   it's important to keep an eye on such changes

Simpler said, an index can become corrupted, leading to bad query results
and in due course to violated unique constraints.

> - the next item should describe what to do in case of libicu/glibc version changes - mainly about
>   rebuilding the indexes, but not only
> - finally, we should provide the list of commands to identify affected indexes, to rebuild them
>   online/offline, concurrently etc.

There are several strategies to deal with the problem:

- rebuild all indexes (simple, slow)
- identify all indexes that involve strings (a bit more complicated, faster)
- check all indexes with amcheck and rebuild only those with a problem
  (leaves a window where users couls get bad query results
- perform a test upgrade and find the affected indexes ahead of time

Yours,
Laurenz Albe






view thread (8+ messages)  latest in thread

Message-ID: <b12f6d6c2c6ff9bb6a7f75a53a5d0f3adb68de67.camel@cybertec.at>
Permalink:  ../b12f6d6c2c6ff9bb6a7f75a53a5d0f3adb68de67.camel@cybertec.at/
Also on:    postgresql.org/message-id/b12f6d6c2c6ff9bb6a7f75a53a5d0f3adb68de67.camel@cybertec.at

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: laurenz.albe@cybertec.at, alexey.shishkin@enterprisedb.com
  Subject: Re: OS system version upgrade (glibc / libicu version change)
  In-Reply-To: <b12f6d6c2c6ff9bb6a7f75a53a5d0f3adb68de67.camel@cybertec.at>
  References: <177002326159.803.1983703962002247846@wrigleys.postgresql.org> <CALVdoE78O7Ksm+1ySLCv=Bs_-O5hHyQfXHEMaNC3dPP1t2WSQw@mail.gmail.com> <CALVdoE6syAWYPKCWJ7o4Vfaapw5Q316qjSx32QLmuyA+yrXEMw@mail.gmail.com> <225d52b51ed9a911ced2f8e6c00e089a1ce50f19.camel@cybertec.at> <CALVdoE5ne1EEvU29Y9_=rbiYb+M5xRbVuQ=PEZs33b6ze1+m8A@mail.gmail.com> <b12f6d6c2c6ff9bb6a7f75a53a5d0f3adb68de67.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox