From: Tom Lane <tgl@sss.pgh.pa.us>
To: comanicibogdy@yahoo.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17892: Bug primary key
Date: Wed, 12 Apr 2023 08:03:28 -0400
Message-ID: <824558.1681301008@sss.pgh.pa.us> (raw)
In-Reply-To: <17892-ac3a507a8e97a453@postgresql.org>
References: <17892-ac3a507a8e97a453@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> We have a database with over 3 milions apps in it
> Something happend we just found duplicates with same id, but we have
> constraints : PRIMARY KEY on id
With no details it's impossible to do more than speculate.
However, if these are string-type columns then a possible cause
is an OS update having changed collation rules underneath you.
There's more details about that in
https://wiki.postgresql.org/wiki/Locale_data_changes
In any case the path to follow is to manually fix the duplicates
and REINDEX.
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, comanicibogdy@yahoo.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17892: Bug primary key
In-Reply-To: <824558.1681301008@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