| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Willian Colognesi <willian_colognesi(at)trimble(dot)com> |
| Cc: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Segmentation Fault PG 14 |
| Date: | 2022-11-08 17:16:10 |
| Message-ID: | 3802316.1667927770@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Willian Colognesi <willian_colognesi(at)trimble(dot)com> writes:
> Looks like we can confirm that the jit disable fixed the problem, because
> since yesterday when I disabled jit, the database did not restarted again,
> and before it the database was restarting at least once per hour.
Hmm. I now recall that we had a previous report of problems with
JIT on aarch64/Focal:
https://www.postgresql.org/message-id/flat/20220303150428.GA26036%40depesz.com
That was LLVM 9 not LLVM 10, but since we never identified the exact
issue, there's no real strong reason to suppose it's been fixed.
Probably keeping JIT off is the best answer for you --- it's hard to
say when we'll be able to make progress with this, given the lack of
reproducible test cases.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bryn Llewellyn | 2022-11-09 00:16:31 | "set role" semantics |
| Previous Message | Willian Colognesi | 2022-11-08 16:40:01 | Re: Segmentation Fault PG 14 |