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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tiago Babo <tiago(dot)babo(at)gmail(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Date: 2017-02-08 00:16:51
Message-ID: 32010.1486513011@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tiago Babo <tiago(dot)babo(at)gmail(dot)com> writes:
> No, I'm not doing that. The index was just created once.

Whole thing is as weird as can be. Maybe you could work on creating
a reproducible test case?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2017-02-08 01:41:31 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Previous Message Tiago Babo 2017-02-08 00:10:13 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT