| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | ajinkya(dot)tankhiwale(at)tcs(dot)com |
| Subject: | BUG #18002: Duplicate entries of row possible even after having primary key |
| Date: | 2023-06-27 11:03:16 |
| Message-ID: | 18002-00f2b6cb2b9c0b02@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 18002
Logged by: Ajinkya Tankhiwale
Email address: ajinkya(dot)tankhiwale(at)tcs(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2023-06-27 17:03:48 | Re: BUG #18000: Access method used by matview can be dropped leaving broken matview |
| Previous Message | Alexander Lakhin | 2023-06-27 11:00:00 | Re: BUG #17997: Assert failed in validatePartitionedIndex() when attaching partition index to child of valid index |