Re: Corrupt btree index includes rows that don't match - Mailing list pgsql-general

From Ron Johnson
Subject Re: Corrupt btree index includes rows that don't match
Date
Msg-id CANzqJaA752TH8RMNsgpJkz=-18_rpC6j9-L_SZE-HFr7rFb06g@mail.gmail.com
Whole thread Raw
In response to Re: Corrupt btree index includes rows that don't match  (shammat@gmx.net)
List pgsql-general
On Fri, Jul 4, 2025 at 5:50 AM <shammat@gmx.net> wrote:
> One coincidence is that we started seeing the first symptoms of this
> around the same time as libicu was updated with a security patch.
> However, postgres hasn’t been restarted and doesn’t reference the
> new version in its process maps. Plus state groups are integers
> anyway. We also use the C locale, not ICU.
Sounds as if you are hit by locale changes:

https://wiki.postgresql.org/wiki/Locale_data_changes


I think you will need to upgrade to prevent future problems like that:

Postgres 15 introduced some mechanisms to track and validate version discrepancies after an OS update.

Postgres 17 added a "built-in" collation provider which is independent of glibc

Why?  Locale only cares about strings, and "Plus state groups are integers anyway."

Besides, "We also use the C locale, not ICU."

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

pgsql-general by date:

Previous
From: shammat@gmx.net
Date:
Subject: Re: Corrupt btree index includes rows that don't match
Next
From: shammat@gmx.net
Date:
Subject: Re: Corrupt btree index includes rows that don't match