Home > mailing lists

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

From	Geoff Winkless
Subject	Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint
Date	May 20, 2015 12:49:35
Msg-id	CAEzk6fd1VCy_E-N_RgyNRNJctr_Jp=2DOCSPc-gCFkx0xZUtEQ@mail.gmail.com Whole thread Raw
In response to	Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint (Simon Riggs <simon@2ndQuadrant.com>)
Responses	Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint (Simon Riggs <simon@2ndQuadrant.com>)
List	pgsql-hackers

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?

Geoff

From: Etsuro Fujita
Date: 20 May 2015, 12:41:22
Subject: Typo in tablecmds.c

From: Fabrízio de Royes Mello
Date: 20 May 2015, 14:06:35
Subject: Re: Change pg_cancel_*() to ignore current backend