Re: PG v12.2 - Setting jit_above_cost is causing the server to crash

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: PG v12.2 - Setting jit_above_cost is causing the server to crash
Дата
Msg-id CA+OCxoz0bWi+R2WpocfkD20Lgrg69z1jQ_SZd-zmdzHW0zt+bg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: PG v12.2 - Setting jit_above_cost is causing the server to crash  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: PG v12.2 - Setting jit_above_cost is causing the server to crash  (Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>)
Список pgsql-hackers
Hi

On Thu, Feb 27, 2020 at 12:41 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Aditya Toshniwal <aditya.toshniwal@enterprisedb.com> writes:
> On Mon, Feb 24, 2020 at 12:46 PM Andres Freund <andres@anarazel.de> wrote:
>> This isn't reproducible here. Are you sure that you're running on a
>> clean installation?

> Yes I did a fresh installation using installer provided here -
> https://www.enterprisedb.com/downloads/postgresql

There is apparently something wrong with the JIT stuff in EDB's 12.2
build for macOS.  At least, that's the conclusion I came to after
off-list discussion with the submitter of bug #16264, which has pretty
much exactly this symptom (especially if you're seeing "signal 9"
reports in the postmaster log).  For him, either disabling JIT or
reverting to 12.1 made it go away.

We've been looking into this;

Apple started a notarisation process some time ago, designed to mark their applications as conforming to various security requirements, but prior to Catalina it was essentially optional. When Catalina was released, they made notarisation for distributed software a requirement, but had the process issue warnings for non-compliance. As-of the end of January, those warnings became hard errors, so now our packages must be notarised, and for that to happen, must be hardened by linking with a special runtime and having securely time stamped signatures on every binary before being checked and notarised as such by Apple. Without that, users would have to disable security features on their systems before they could run our software.

Our packages are being successfully notarised at the moment, because that's essentially done through a static analysis. We can (and have) added what Apple call an entitlement in test builds which essentially puts a flag in the notarisation for the product that declares that it will do JIT operations, however, it seems that this alone is not enough and that in addition to the entitlement, we also need to include the MAP_JIT flag in mmap() calls. See https://developer.apple.com/documentation/security/hardened_runtime and https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_cs_allow-jit

We're working on trying to test a patch for that at the moment.
 
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Dave Cramer
Дата:
Сообщение: Re: Error on failed COMMIT
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [Proposal] Level4 Warnings show many shadow vars