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

From Tiago Babo
Subject Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Date
Msg-id 509A8E2B-EB71-4AD4-A88D-FCC43210D6A4@gmail.com
Whole thread Raw
In response to Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
No, I'm not doing that. The index was just created once. 

> On 8 Feb 2017, at 00:04, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 
> Tiago Babo <tiago.babo@gmail.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


-- 
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: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Next
From: Tom Lane
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT