From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: talmoshe24@gmail.com
Subject: BUG #18756: Postgres corruption
Date: Sun, 29 Dec 2024 18:49:34 +0000
Message-ID: <18756-dedadb77ca3668b8@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18756
Logged by: Tal Moshe
Email address: talmoshe24@gmail.com
PostgreSQL version: 14.13
Operating system: centos9
Description:
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.
The index is created using the following statement:
CREATE UNIQUE INDEX npn ON public.files USING btree (SNAPSHOT_ID,
PARENT_GUID_DEVICE, PARENT_GUID_VERSION, NAME) WHERE PARENT_GUID_DEVICE IS
NOT NULL;
In these environments Postgres v14.13 is used.
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, talmoshe24@gmail.com
Subject: Re: BUG #18756: Postgres corruption
In-Reply-To: <18756-dedadb77ca3668b8@postgresql.org>
* 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