| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | atzedus(at)gmail(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17361: Unique index constraint inconsistence |
| Date: | 2022-01-11 00:08:24 |
| Message-ID: | 2499549.1641859704@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:
> Indexes:
> "parts_stock_stat_pkey" PRIMARY KEY, btree (id)
> "parts_stock_stat_lower_stock_type_id_idx" UNIQUE, btree (lower(name),
> stock_type_id)
> Following reindex command failed:
> db=# reindex table parts_stock_stat;
> ERROR: could not create unique index
> "parts_stock_stat_lower_stock_type_id_idx"
> DETAIL: Key (lower(name), stock_type_id)=(ha_hr/50, 4) is duplicated.
How long have you had this database? If it's older than your last
OS upgrade, it's possible that the index has become corrupt as a
result of OS-level collation changes. See
https://wiki.postgresql.org/wiki/Locale_data_changes
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Роман Григорович | 2022-01-11 06:44:23 | Re: BUG #17361: Unique index constraint inconsistence |
| Previous Message | PG Bug reporting form | 2022-01-10 22:29:06 | BUG #17361: Unique index constraint inconsistence |