Re: ON CONFLICT with constraint name doesn't work

On 2017-03-16 13:08:53 -0700, Nikolay Samokhvalov wrote:
> On Thu, Mar 16, 2017 at 12:40 PM, Andres Freund <andres(at)anarazel(dot)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(at)test=# insert into constr (msg) values ('hohoho') ;
> INSERT 0 1
>
> [local]:5432 nikolay(at)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".

Seems like a good idea to improve that message. I wouldn't vote for
backpatching it, however. Could you propose a patch for that?

Greetings,

Andres Freund