From: Tom Lane <tgl@sss.pgh.pa.us>
To: oserov@clickup.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17727: A query crashes server process: ... was terminated by
 signal 7: Bus error / Segmentation Fault
In-reply-to: <17727-c9a10259e190c8b1@postgresql.org>
References: <17727-c9a10259e190c8b1@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Wed, 21 Dec 2022 19:06:32 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1583844.1671651848.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Dec 2022 14:44:08 -0500
Message-ID: <1583845.1671651848@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1583845.1671651848%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I have a query that consistently results in server crash and "server pro=
cess
> ... was terminated by signal 7: Bus error" running on any replica or mas=
ter
> of the DB. I also have a more generic query that also crashes other
> masters/replicas in prod environment but with 'Segmentation Fault'. I ca=
n't
> reproduce the same crash in other non-prod environments. I am unable to
> provide repro steps that could reproduce this error on a local machine a=
nd
> looking for more guidance how to debug/mitigate this error. =


If you can provide a stack trace from the crash, that might be enough
to diagnose it.

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_=
backend

However ... the first thing I'd probably try is turning off JIT.
We've heard some reports suggesting that that causes trouble on
ARM machines.

			regards, tom lane