Content-Type: multipart/alternative;
 boundary=Apple-Mail-BAC36265-ED13-4A67-853F-C1FD0DA9A83C
Content-Transfer-Encoding: 7bit
From: Teja Jakkidi <teja.jakkidi05@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Duplicate data even with primary keys enabled
Date: Fri, 28 Oct 2022 11:27:14 -0700
Message-Id: <59B1180A-4A4B-4A1A-B50A-C9D9B41AA67D@gmail.com>
References: 
 <CAAo1mbnEV6QxHwnV6r2EUMXjb_Fz98+8eO6ZRU7eux4FTuF0YA@mail.gmail.com>
Cc: pgsql-admin <pgsql-admin@lists.postgresql.org>
In-Reply-To: 
 <CAAo1mbnEV6QxHwnV6r2EUMXjb_Fz98+8eO6ZRU7eux4FTuF0YA@mail.gmail.com>
To: Samed YILDIRIM <samed@reddoc.net>
Archived-At: 
 <https://www.postgresql.org/message-id/59B1180A-4A4B-4A1A-B50A-C9D9B41AA67D%40gmail.com>
Precedence: bulk


--Apple-Mail-BAC36265-ED13-4A67-853F-C1FD0DA9A83C
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

Hi YILDIRIM,

Thanks for your response.

We have a composite primary key on 3columns. We are noticing multiple rows w=
ith same values in the 3pk columns which should not happen as primary constr=
aint is defined on them.
Also, none of the columns are null.

Regards,
Teja. J.

> On Oct 28, 2022, at 10:59 AM, Samed YILDIRIM <samed@reddoc.net> wrote:
>=20
> =EF=BB=BF
> Hello Teja,
>=20
> Could you please add some example lines? I need to see some examples to sa=
y something more accurate.
>=20
> First of all, null !=3D null in PostgreSQL. So, if any of those three colu=
mns is null, it means it is unique and won't violate unique constraints even=
 if there is another row with the same values.
>=20
> Another thing, if you defined a composite primary key on those 3 columns, i=
t means that it will prevent inserting another row that has exactly the same=
 values on those columns. If you want to keep values unique on each individu=
al columns, you need to create 3 separate unique indexes/constraints.
>=20
> Best regards.
> Samed YILDIRIM
>=20
>> On Fri, 28 Oct 2022, 19:52 Teja Jakkidi, <teja.jakkidi05@gmail.com> wrote=
:
>> Hello Admin team,
>>=20
>> I have an issue where we are seeing duplicate data in one of the tables. T=
he table has primary key constraint defined on 3columns and we are seeing du=
plicate data in these column data.
>> Is there any way to figure out why this could happen? Also is there a way=
 that the primary key constraint can be disabled during  inserts?? If so how=
 can we find who disabled it? (Note that audit is not enabled for the table)=

>> Please suggest.
>>=20
>> Thanks,
>> Teja.
>>=20

--Apple-Mail-BAC36265-ED13-4A67-853F-C1FD0DA9A83C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">Hi YILDIRIM,<div><br></div><div>Thanks for y=
our response.</div><div><br></div><div>We have a composite primary key on 3c=
olumns. We are noticing multiple rows with same values in the 3pk columns wh=
ich should not happen as primary constraint is defined on them.</div><div>Al=
so, none of the columns are null.</div><div><br><div dir=3D"ltr">Regards,</d=
iv><div dir=3D"ltr">Teja. J.</div><div dir=3D"ltr"><br><blockquote type=3D"c=
ite">On Oct 28, 2022, at 10:59 AM, Samed YILDIRIM &lt;samed@reddoc.net&gt; w=
rote:<br><br></blockquote></div><blockquote type=3D"cite"><div dir=3D"ltr">=EF=
=BB=BF<div dir=3D"auto">Hello Teja,<div dir=3D"auto"><br></div><div dir=3D"a=
uto">Could you please add some example lines? I need to see some examples to=
 say something more accurate.</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto">First of all, null !=3D null in PostgreSQL. So, if any of those three c=
olumns is null, it means it is unique and won't violate unique constraints e=
ven if there is another row with the same values.</div><div dir=3D"auto"><br=
></div><div dir=3D"auto">Another thing, if you defined a composite primary k=
ey on those 3 columns, it means that it will prevent inserting another row t=
hat has exactly the same values on those columns. If you want to keep values=
 unique on each individual columns, you need to create 3 separate unique ind=
exes/constraints.</div><div dir=3D"auto"><br><div data-smartmail=3D"gmail_si=
gnature" dir=3D"auto">Best regards.<br>Samed YILDIRIM</div></div></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, 28 O=
ct 2022, 19:52 Teja Jakkidi, &lt;<a href=3D"mailto:teja.jakkidi05@gmail.com"=
>teja.jakkidi05@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Hello Admin team,<br>
<br>
I have an issue where we are seeing duplicate data in one of the tables. The=
 table has primary key constraint defined on 3columns and we are seeing dupl=
icate data in these column data.<br>
Is there any way to figure out why this could happen? Also is there a way th=
at the primary key constraint can be disabled during&nbsp; inserts?? If so h=
ow can we find who disabled it? (Note that audit is not enabled for the tabl=
e)<br>
Please suggest.<br>
<br>
Thanks,<br>
Teja.<br>
<br>
</blockquote></div>
</div></blockquote></div></body></html>=

--Apple-Mail-BAC36265-ED13-4A67-853F-C1FD0DA9A83C--