Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT - Mailing list pgsql-bugs

From Peter Geoghegan
Subject Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT
Date
Msg-id CAH2-WznXVG2DYXADcr7wXGO+E+YWUrofm4qYat2a-2kbwoD5Xg@mail.gmail.com
Whole thread Raw
In response to [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT  (tiago.babo@gmail.com)
Responses Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT  (Tiago Babo <tiago.babo@gmail.com>)
List pgsql-bugs
On Tue, Feb 7, 2017 at 2:15 PM, Tiago Babo <tiago.babo@gmail.com> wrote:
> Here is an example where it gives the error (I excluded the created_at and
> updated_at columns in the last e-mail, but they do exist in the table):
>
> INSERT INTO accounts (type, person_id) VALUES ('PersonAccount', 69559,
> '2017-02-03 12:09:27.259', '2017-02-03 12:09:27.259') ON CONFLICT (type,
> person_id) WHERE type = 'PersonAccount' DO UPDATE SET updated_at =
> EXCLUDED.updated_at RETURNING *

Can you give an example of where it does actually work? Is there any
discernible pattern to what each case looks like?


-- 
Peter Geoghegan


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Tiago Babo
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT
Next
From: Tiago Babo
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT