Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Tiago Babo <tiago(dot)babo(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Date: 2017-02-07 22:17:21
Message-ID: CAH2-WznXVG2DYXADcr7wXGO+E+YWUrofm4qYat2a-2kbwoD5Xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Feb 7, 2017 at 2:15 PM, Tiago Babo <tiago(dot)babo(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tiago Babo 2017-02-07 23:21:39 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Previous Message Tiago Babo 2017-02-07 22:15:20 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT