Re: [EXTERNAL] Re: Don't clean up LLVM state when exiting in a bad way
Jelte Fennema-Nio <jelte.fennema@microsoft.com>
From: Jelte Fennema <Jelte.Fennema@microsoft.com>
To: Alexander Lakhin <exclusion@gmail.com>, Andres Freund <andres@anarazel.de>, Justin Pryzby <pryzby@telsasoft.com>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2021-09-14T20:36:44Z
Lists: pgsql-hackers
> So I wonder, isn't the fixed usage issue specific to LLVM 7 That's definitely possible. I was unable to reproduce the issue I shared in my original email when postgres was compiled with LLVM 10. That's also why I sent an email to the pgsql-pkg-yum mailing list about options to use a newer version of LLVM on CentOS 7: https://www.postgresql.org/message-id/flat/AM5PR83MB0178475D87EFA290A4D0793DF7FF9%40AM5PR83MB0178.EURPRD83.prod.outlook.com (no response so far though)
Commits
-
jit: Do not try to shut down LLVM state in case of LLVM triggered errors.
- dccffd9a274d 11.14 landed
- c49e6f9d9749 13.5 landed
- 43849b65f333 12.9 landed
- edb4d95ddf89 15.0 landed
- 4e86887e0922 14.0 landed