Re: Segmentation Fault PG 14

From: Willian Colognesi <willian_colognesi(at)trimble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 16:40:01
Message-ID: CADAf1kZZmvR2zoa2xF4qWS3ZTf2TPQt5OV0cvZYHqrj=HS9CLQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

I don't think it will cause too much impact in our use case having it
disabled, so, if you need anything else that could help the analyses to
find the bug feel free to let me know and I can grab the logs or whatever
needed.

Thanks y'all

On Mon, Nov 7, 2022 at 8:05 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Willian Colognesi <willian_colognesi(at)trimble(dot)com> writes:
> > There is no llvm installed on ubuntu server, postgresql was installed via
> > apt package `apt install postgresql-14`
>
> If there's no LLVM around, then disabling JIT wouldn't do anything,
> because it depends on LLVM to compile code.
>
> We should perhaps wait awhile to see if that really fixed it.
>
> regards, tom lane
>

--
<http://www.trimble.com/>

*Willian Cezar de O. Colognesi*
Systems Analysis Specialist, Trimble Transportation Brazil
Avenida Santos Dumont, 271 | Londrina, PR | 86039-090

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2022-11-08 17:16:10 Re: Segmentation Fault PG 14
Previous Message Imre Samu 2022-11-08 14:05:34 Re: Information to CVE-2022-42889