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
Msg-id CAEzk6ff1W0rmKuo1DOvX+5en8xZyZRQhwhOGY6pUKdO2sUkEfQ@mail.gmail.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT DO UPDATE with _any_ constraint  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
<p dir="ltr"><br /> On 21 May 2015 21:15, "Simon Riggs" <<a
href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>>wrote:<br /> > I would like to see this happen now
beforewe get hit with usage questions similar to OP's. If both requests cannot happen now, if we can at least agree a
pathfor future enhancement we can refer people to what will happen in later releases when they ask.<p dir="ltr">FWIW as
theOP I was merely asking for clarification as to why it was required for UPDATE and not DO NOTHING. <p dir="ltr">The
discussionhas been enough to clarify for me: putting something along the lines of what was discussed in this thread in
thedocumentation alongside the requirement would, IMO, be sufficient.<p dir="ltr">I'm not trying to suggest that I
representeveryone and that the discussion is over, but as you pointed at the OP I thought I should put in where I am
withthis now.<p dir="ltr">Ta<p dir="ltr">Geoff<br /> 

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: GiST KNN Crasher
Next
From: Piotr Stefaniak
Date:
Subject: Re: Fix misaligned access of ItemPointerData on ARM