| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Tiago Babo <tiago(dot)babo(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |
| Date: | 2017-02-07 23:36:30 |
| Message-ID: | CAH2-WznTcRCcKPNTEduQXz4KLfoWCzAFg3dUBgKQ91LpwxekAQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Feb 7, 2017 at 3:21 PM, Tiago Babo <tiago(dot)babo(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tiago Babo | 2017-02-07 23:46:49 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |
| Previous Message | Tiago Babo | 2017-02-07 23:21:39 | Re: BUG #14526: no unique or exclusion constraint matching the ON CONFLICT |