| From: | abbas alizadeh <ramkly(at)yahoo(dot)com> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com>, Teju Jakkidi vlogs <teja(dot)jakkidi05(at)gmail(dot)com>, Holger Jakobs <holger(at)jakobs(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Duplicate data even with primary keys enabled |
| Date: | 2022-10-29 11:20:58 |
| Message-ID: | C254B8F9-9779-4F8F-BDAB-C55E7088FA7C@yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hi all.
I faced the same issue last week.
We had duplicated records on primary key.
Postgresql version is 14.4
Sent from my iPhone
> On 29 Oct 2022, at 4:18 AM, Erik Wienhold <ewie(at)ewie(dot)name> wrote:
>
>
>>
>> On 28/10/2022 22:50 CEST Scott Ribe <scott_ribe(at)elevated-dev(dot)com> wrote:
>>
>> A corrupted index could allow that to happen by failing to catch the duplicate
>> insert. I suppose it might also be able to cause the same row to be returned
>> multiple times--although I have personally only ever seen corrupted indexes
>> cause rows to not be found.
>
> I think it should be possible to tell those two cases apart by looking at system
> column ctid. The ctid should be the same for duplicate rows if the same row is
> found multiple times in the index. Different ctid if the corrupted index
> allowed INSERT with duplicates.
>
> --
> Erik
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2022-10-29 12:16:01 | Re: Duplicate data even with primary keys enabled |
| Previous Message | Jwiencek3 | 2022-10-29 02:53:30 | Re: Duplicate data even with primary keys enabled |