Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thom Brown <thom(at)linux(dot)com>, Peter Geoghegan <pg(at)heroku(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Date: 2015-05-20 17:55:00
Message-ID: 4724.1432144500@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-05-20 13:31:57 -0400, Tom Lane wrote:
>> If you can't use an exclusion constraint to support the command,
>> then the error message shouldn't be worded like that.

> But you *can* use a exclusion constraint for DO NOTHING. Just not (yet)
> for DO UPDATE.

Hm. Maybe it would be worth having two different message texts for
the two cases, then?

regards, tom lane

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Peter Geoghegan 2015-05-20 18:24:06 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Previous Message Andres Freund 2015-05-20 17:37:06 Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-05-20 17:59:16 Re: Disabling trust/ident authentication configure option
Previous Message Alvaro Herrera 2015-05-20 17:37:47 Re: Typo patch