Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Subject: Re: how to make duplicate finding query faster?
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CALg-PKB92uV1v_R2JTLsr27xUdJaEru-b=Frig_YC=jy9L3X6A@mail.gmail.com>
Date: Wed, 30 Dec 2020 06:28:26 -0700
Cc: Pgsql-admin <pgsql-admin@postgresql.org>,
 krishna@thewebconz.com,
 pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <84F2C1B0-3510-410B-8924-0EB7377684A9@elevated-dev.com>
References: 
 <CALg-PKBPQPBMbNAxf-pF0OLbYs0exC7Vf2Sn3hNPUAJ7Q=mPtA@mail.gmail.com>
 <FEEE2DC4-B506-4B34-80FE-07FCC0ADC61E@elevated-dev.com>
 <CALg-PKB92uV1v_R2JTLsr27xUdJaEru-b=Frig_YC=jy9L3X6A@mail.gmail.com>
To: Sachin Kumar <sachinkumaras@gmail.com>
Precedence: bulk

> On Dec 30, 2020, at 6:24 AM, Sachin Kumar <sachinkumaras@gmail.com> =
wrote:
>=20
> Yes, I am checking one by one because my goal is to fail the whole =
upload if there is any duplicate entry and to inform the user that they =
have a duplicate entry in the file.

That's not what I said, though. If you want to fail the whole copy, then =
you don't have to check one by one, just try the copy--assuming you have =
the correct constraints in place.

Unless you want to tell the user *which* rows are duplicates, in which =
case you can try a variant on my prior suggestion, copy into a temp =
table, use a join to find duplicates...=