| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | talmoshe24(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18756: Postgres corruption |
| Date: | 2024-12-29 23:10:19 |
| Message-ID: | 3724195.1735513819@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Misiewicz | 2024-12-30 00:36:13 | pg_upgrade cannot create btrfs clones on linux kernel 6.8.0 |
| Previous Message | PG Bug reporting form | 2024-12-29 18:49:34 | BUG #18756: Postgres corruption |