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
Date: Wed, 21 Aug 2024 17:31:37 -0400
Message-ID: <1888240.1724275897@sss.pgh.pa.us> (raw)
In-Reply-To: <CAKeJUPB1E16fGBrXTO3JKuPv3VW0wywCDHd3Ece2h2uHwtJSkA@mail.gmail.com>
References: <CAKeJUPB1E16fGBrXTO3JKuPv3VW0wywCDHd3Ece2h2uHwtJSkA@mail.gmail.com>
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 resource
> 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 = 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, wbraga@implentio.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Postgres v16.4 crashes on segfault when memory >= 16gb
In-Reply-To: <1888240.1724275897@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox