Re: BUG #18002: Duplicate entries of row possible even after having primary key - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #18002: Duplicate entries of row possible even after having primary key
Date
Msg-id 20230627203640.fkh66zps3p2jpxvd@awork3.anarazel.de
Whole thread Raw
In response to BUG #18002: Duplicate entries of row possible even after having primary key  (PG Bug reporting form <noreply@postgresql.org>)
Responses RE: BUG #18002: Duplicate entries of row possible even after having primary key  (Ajinkya Tankhiwale <ajinkya.tankhiwale@tcs.com>)
List pgsql-bugs
Hi,

On 2023-06-27 11:03:16 +0000, PG Bug reporting form wrote:
> 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.

You haven't provided information that'd allow us to debug the issue. At the
very least we'd need table + index definition and the inserts that are allowed
to happen despite being duplicates.  Even better would be a way to reproduce
the issue.

You said that you migrated from 13.7 to 14.7 recently - did you also change
your OS version?

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook
Next
From: Joe Conway
Date:
Subject: Re: BUG #18003: FATAL: cannot request additional shared memory outside shmem_request_hook