| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: JIT compiling with LLVM v12.2 |
| Date: | 2018-03-21 21:45:38 |
| Message-ID: | 20180321214538.ig76omipfsk2iwod@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-03-22 09:31:12 +1300, Thomas Munro wrote:
> Aside from whatever problem is causing this, we can see that there is
> no top-level handling of exceptions. That's probably fine if we are
> in a no throw scenario (unless there is something seriously corrupted,
> as is probably the case here), and it seems that we must be because
> we're accessing this code via its C API.
Yea, it should only happen in abort() type situations. Notably LLVM
doesn't even default to enabling exceptions...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-03-21 21:48:35 | Re: [PoC PATCH] Parallel dump to /dev/null |
| Previous Message | Thomas Munro | 2018-03-21 21:45:37 | Re: JIT compiling with LLVM v12.2 |