From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: ajinkya.tankhiwale@tcs.com
Subject: BUG #18002: Duplicate entries of row possible even after having primary key
Date: Tue, 27 Jun 2023 11:03:16 +0000
Message-ID: <18002-00f2b6cb2b9c0b02@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18002
Logged by: Ajinkya Tankhiwale
Email address: ajinkya.tankhiwale@tcs.com
PostgreSQL version: 14.7
Operating system: RHEL 8.8
Description:
We migrated from 13.7 to 14.7 recently, in current data setup, we say that
duplicate records are present in table even after primary key. I see that in
the past, same issue was reported and possible solution was to run full
vacuum or re-index. We tried both, but still able to enter duplicate
records.
This is blocker for us and would like to have solution for this as soon as
possible.
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: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, ajinkya.tankhiwale@tcs.com
Subject: Re: BUG #18002: Duplicate entries of row possible even after having primary key
In-Reply-To: <18002-00f2b6cb2b9c0b02@postgresql.org>
* 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