pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feedBUG #18756: Postgres corruption
2+ messages / 2 participants
[nested] [flat]
* BUG #18756: Postgres corruption
@ 2024-12-29 18:49 PG Bug reporting form <noreply@postgresql.org>
0 siblings, 1 reply; 2+ messages in thread
From: PG Bug reporting form @ 2024-12-29 18:49 UTC (permalink / raw)
To: pgsql-bugs@lists.postgresql.org; +Cc: talmoshe24@gmail.com
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.
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: BUG #18756: Postgres corruption
@ 2024-12-29 23:10 Tom Lane <tgl@sss.pgh.pa.us>
parent: PG Bug reporting form <noreply@postgresql.org>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2024-12-29 23:10 UTC (permalink / raw)
To: talmoshe24@gmail.com; +Cc: pgsql-bugs@lists.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
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2024-12-29 23:10 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2024-12-29 18:49 BUG #18756: Postgres corruption PG Bug reporting form <noreply@postgresql.org>
2024-12-29 23:10 ` Tom Lane <tgl@sss.pgh.pa.us>
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