| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PG v12.2 - Setting jit_above_cost is causing the server to crash |
| Date: | 2020-02-24 14:50:53 |
| Message-ID: | 16648.1582555853@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com> writes:
> On Mon, Feb 24, 2020 at 12:46 PM Andres Freund <andres(at)anarazel(dot)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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2020-02-24 16:34:03 | Re: DB running out of memory issues after upgrade |
| Previous Message | dbatoCloud Solution | 2020-02-24 10:12:26 | test |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-02-24 16:03:07 | Re: client-side fsync() error handling |
| Previous Message | Tom Lane | 2020-02-24 14:44:29 | Re: pgsql: Add kqueue(2) support to the WaitEventSet API. |