| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | postgresql2(at)realityexists(dot)net |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13148: Unexpected deferred EXCLUDE constraint violation on derived table |
| Date: | 2015-05-10 18:28:04 |
| Message-ID: | CAKFQuwZ5EkKy9kwqvsaxkmdcCVZxdyRP4Pzx6PbzgERNHXx5mw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Please don't top-post.
On Sun, May 10, 2015 at 11:19 AM, <postgresql2(at)realityexists(dot)net> wrote:
> That's odd! I just confirmed again that I get the exact same error with
> COMMIT (and no warnings). Are you able to run all the commands before the
> COMMIT successfully and get 1 row back from the SELECT?
>
>
I am. I am not using psql so I may be getting different errors compared
to what psql would eventually emit. I suspect that the actual error is
getting swallowed somewhere and then the processing on the COMMIT happens
without the transaction being open.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2015-05-10 18:40:10 | Re: BUG #13148: Unexpected deferred EXCLUDE constraint violation on derived table |
| Previous Message | postgresql2 | 2015-05-10 18:19:41 | Re: BUG #13148: Unexpected deferred EXCLUDE constraint violation on derived table |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2015-05-10 18:31:52 | Re: multixacts woes |
| Previous Message | postgresql2 | 2015-05-10 18:19:41 | Re: BUG #13148: Unexpected deferred EXCLUDE constraint violation on derived table |