From: Tom Lane <tgl@sss.pgh.pa.us>
To: talmoshe24@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18756: Postgres corruption
Date: Sun, 29 Dec 2024 18:10:19 -0500
Message-ID: <3724195.1735513819@sss.pgh.pa.us> (raw)
In-Reply-To: <18756-dedadb77ca3668b8@postgresql.org>
References: <18756-dedadb77ca3668b8@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> We saw a corruption in 3 different environments in one of the unique indexes
> (named “npn”) in “files” table.
> It seems as if not all the rows (that should be part of this index) in the
> table are indexed, and therefore “duplicated” rows (rows that violates the
> index constraint) are allowed to be inserted to DB.
Are any of the indexed columns of string types (text, varchar, etc)?
And have you upgraded the underlying OS since creating the index?
If so, you've likely been bit by locale changes. See
https://wiki.postgresql.org/wiki/Locale_data_changes
regards, tom lane
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: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, talmoshe24@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18756: Postgres corruption
In-Reply-To: <3724195.1735513819@sss.pgh.pa.us>
* 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