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

From: Tiago Babo <tiago(dot)babo(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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:10:13
Message-ID: 509A8E2B-EB71-4AD4-A88D-FCC43210D6A4@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

No, I'm not doing that. The index was just created once.

> On 8 Feb 2017, at 00:04, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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 Tom Lane 2017-02-08 00:16:51 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Previous Message Tom Lane 2017-02-08 00:04:08 Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT