Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT
От | Peter Geoghegan |
---|---|
Тема | Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT |
Дата | |
Msg-id | CAH2-WznTcRCcKPNTEduQXz4KLfoWCzAFg3dUBgKQ91LpwxekAQ@mail.gmail.com обсуждение исходный текст |
Ответ на | [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT (tiago.babo@gmail.com) |
Ответы |
Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT
Re: [BUGS] BUG #14526: no unique or exclusion constraint matching theON CONFLICT Re: [BUGS] BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |
Список | pgsql-bugs |
On Tue, Feb 7, 2017 at 3:21 PM, Tiago Babo <tiago.babo@gmail.com> wrote: > The only difference (so it seems), is that when it crashes, the person was created in the seconds before creating the account.When it previously exists in the persons table, it never gives the error. It crashes? Anyway, it's very hard to see how that could be, since the error in question is thrown from within the planner. I don't recall the exact details of how inference will do offhand, but I am suspicious of the cast that appears in the partial index predicate. -- Peter Geoghegan -- 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 по дате отправления: