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:04:08
Message-ID: 31551.1486512248@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:
> I don't really understand how PostgreSQL handles indexes, but would it be
> possible that the INDEX is being used/updated at that moment and so the
> INSERT doesn't know it exists? Can concurrency also be a problem?

Data activity shouldn't matter. If you're dropping and recreating the
whole index, that could matter.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tiago Babo 2017-02-08 00:10:13 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Previous Message Tom Lane 2017-02-07 23:57:20 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT