Re: [BUGS] ON CONFLICT with constraint name doesn't work - Mailing list pgsql-bugs

From Nikolay Samokhvalov
Subject Re: [BUGS] ON CONFLICT with constraint name doesn't work
Date
Msg-id CANNMO++J-0XC74LdQvX83VfR+b_QV0VhAtz56E7atbydxrNRgg@mail.gmail.com
Whole thread Raw
In response to Re: [BUGS] ON CONFLICT with constraint name doesn't work  (Andres Freund <andres@anarazel.de>)
Responses Re: [BUGS] ON CONFLICT with constraint name doesn't work
List pgsql-bugs
On Thu, Mar 16, 2017 at 12:40 PM, Andres Freund <andres@anarazel.de> wrote:
A unique index isn't exactly the same as a unique constraint - you
really need to create a constraint.

Then we probably need to fix this message?

[local]:5432 nikolay@test=# insert into constr (msg) values ('hohoho') ;
INSERT 0 1

[local]:5432 nikolay@test=# insert into constr (msg) values ('hohoho') ;
ERROR:  duplicate key value violates unique constraint "i_constr_msg"
DETAIL:  Key (md5(msg))=(8b0dc2e34844337434b8475108a490ab) already exists.

-- it tells us explicitly, that we have a *constraint* named "i_constr_msg".

pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [BUGS] ON CONFLICT with constraint name doesn't work
Next
From: Andres Freund
Date:
Subject: Re: [BUGS] ON CONFLICT with constraint name doesn't work