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

From Tom Lane
Subject Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Date
Msg-id 31551.1486512248@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT  (Tiago Babo <tiago.babo@gmail.com>)
Responses Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT  (Tiago Babo <tiago.babo@gmail.com>)
List pgsql-bugs
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: Tiago Babo
Date:
Subject: Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT