| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Ron Clarke <rclarkeai(at)gmail(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: More than one UNIQUE key when matching items.. |
| Date: | 2021-03-20 20:00:13 |
| Message-ID: | 7d1d877d122bc59dceddd687f37fb674175078dd.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 2021-03-20 at 15:51 +0000, Ron Clarke wrote:
> In SQL Server this is easy, we insert the records into a temporary table with separate Unique
> indexes on the id for set a and the ids for set b and put the 'ignore_dup_key' on which tells
> SQL Server to ignore duplicate rows and carry on.
>
> The nearest to this at first appears to be the ON CONFLICT ON CONSTRAINT IGNORE in Postgres.
> But this only works with a single constraint, at a time i.e. we can't set the ON CONFLICT ON
> CONSTRAINT IGNORE to work with multiple UNIQUE indexes.
You can try this:
INSERT ... ON CONFLICT DO NOTHING;
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrus | 2021-03-20 21:38:59 | Re: SV: Log files polluted with permission denied error messages after every 10 seconds |
| Previous Message | Jan Wieck | 2021-03-20 19:13:09 | Re: Unkillable processes creating millions of tiny temp files |