From: Tom Lane <tgl@sss.pgh.pa.us>
To: atzedus@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17361: Unique index constraint inconsistence
Date: Mon, 10 Jan 2022 19:08:24 -0500
Message-ID: <2499549.1641859704@sss.pgh.pa.us> (raw)
In-Reply-To: <17361-912697ebdbbf37e9@postgresql.org>
References: <17361-912697ebdbbf37e9@postgresql.org>
PG Bug reporting form <noreply@postgresql.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
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, atzedus@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17361: Unique index constraint inconsistence
In-Reply-To: <2499549.1641859704@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