Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint
Date
Msg-id CANP8+jJO-mgLwuphQNfSzEkAWNS1TAY0B8CMwG83o7P0_O0YSg@mail.gmail.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint  (Geoff Winkless <pgsqladmin@geoff.dj>)
List pgsql-hackers
On 20 May 2015 at 05:49, Geoff Winkless <pgsqladmin@geoff.dj> wrote:
On 19 May 2015 at 21:57, Simon Riggs <simon@2ndquadrant.com> wrote:
It's not clear to me how a single INSERT could cause two or more UPDATEs. 

CREATE TABLE mytable (
  c1 int NOT NULL,
  c2 int NOT NULL,
  PRIMARY KEY (c1),
  UNIQUE (c2)​
 
​);

INSERT INTO mytable (c1, c2) (10, 20);​
INSERT INTO mytable (c1, c2) (11, 21);
​INSERT INTO mytable (c1, c2) (10, 21) ON CONFLICT DO UPDATE .....
Or did you mean from a coding point of view how it would be possible to implement?

I mean "how could that possibly have useful meaning?". 

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint
Next
From: Peter Geoghegan
Date:
Subject: Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint