From: Tom Lane <tgl@sss.pgh.pa.us>
To: Weslley Braga <wbraga@implentio.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Postgres v16.4 crashes on segfault when memory >= 16gb
In-reply-to: 
 <CAKeJUPB1E16fGBrXTO3JKuPv3VW0wywCDHd3Ece2h2uHwtJSkA@mail.gmail.com>
References: 
 <CAKeJUPB1E16fGBrXTO3JKuPv3VW0wywCDHd3Ece2h2uHwtJSkA@mail.gmail.com>
Comments: In-reply-to Weslley Braga <wbraga@implentio.com>
	message dated "Wed, 21 Aug 2024 14:53:00 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1888239.1724275897.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Aug 2024 17:31:37 -0400
Message-ID: <1888240.1724275897@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1888240.1724275897%40sss.pgh.pa.us>
Precedence: bulk

Weslley Braga <wbraga@implentio.com> writes:
> I've been observing for the past month. I'm running PostgreSQL in
> Kubernetes through the CloudNativePG project. When I bump the pods resou=
rce
> configuration to anything above 16gb I notice that complex queries such =
as
> the one shared below cause the runtime to fail with a segfault see logs =
for
> details. The same query with a configuration < 16gb memory works ok.

Hmm, does turning jit =3D off affect it?

> I'm glad to share more information to further help identify the issue. I=
've
> also extracted core dumps from the error.

The core dumps will be useless to anyone on any other platform or with
an even slightly different build of Postgres.  If you could extract
stack traces from them, that might be helpful:

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

			regards, tom lane