Re: Corrupt btree index includes rows that don't match

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To:
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Corrupt btree index includes rows that don't match
Date: 2025-07-04 10:05:32
Message-ID: CANzqJaA752TH8RMNsgpJkz=-18_rpC6j9-L_SZE-HFr7rFb06g@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jul 4, 2025 at 5:50 AM <shammat(at)gmx(dot)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!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message shammat 2025-07-04 10:07:55 Re: Corrupt btree index includes rows that don't match
Previous Message shammat 2025-07-04 09:50:19 Re: Corrupt btree index includes rows that don't match