public inbox for [email protected]
help / color / mirror / Atom feedFrom: [email protected]
To: [email protected]
Subject: Re: Corrupt btree index includes rows that don't match
Date: Fri, 4 Jul 2025 11:50:19 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAPo1J60Vcu+5G0EvvAZtYgTn6U6ADij3aVJ8WFVz77jP+Bd_Tw@mail.gmail.com>
References: <CAPo1J60Vcu+5G0EvvAZtYgTn6U6ADij3aVJ8WFVz77jP+Bd_Tw@mail.gmail.com>
> 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
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 using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Corrupt btree index includes rows that don't match
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox