Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 - Mailing list pgsql-hackers

From Thom Brown
Subject Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Date
Msg-id CAA-aLv6gJ0Ur4rsrv4gfban9w6B16FN5K6tozxUgcNMCBdV00g@mail.gmail.com
Whole thread Raw
In response to Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0  (Andres Freund <andres@anarazel.de>)
Responses Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 8 May 2015 at 16:03, Andres Freund <andres@anarazel.de> wrote:
> So I've committed the patch yesterday evening. I'm pretty sure there'll
> be some more minor things to change. But overall I feel good about the
> current state.
>
> It'd be quite helpful if others could read the docs, specifically for
> insert, and comment whether they're understandable. I've spent a fair
> amount of time trying to make them somewhat simpler, but I do think I
> only succeeded partially.  And there's also my own brand of english to
> consider ;)

The docs say "Note that exclusion constraints are not supported with
ON CONFLICT DO UPDATE."

But I get the following error message text:

"ERROR:  there is no unique or exclusion constraint matching the ON
CONFLICT specification"

This implies that an exclusion constraint is valid in the statement,
which contradicts the docs.  Which one is correct?

-- 
Thom



pgsql-hackers by date:

Previous
From: Jon Nelson
Date:
Subject: Re: Change pg_cancel_*() to ignore current backend
Next
From: Robert Haas
Date:
Subject: Re: Problems with question marks in operators (JDBC, ECPG, ...)