public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tom Lane <[email protected]>
To: Zechman, Derek S <[email protected]>
Cc: [email protected] <[email protected]>
Subject: Re: segmentation fault
Date: Wed, 23 Apr 2025 15:23:20 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <PH0PR04MB82948BA63F4311389716E1F0C0BA2@PH0PR04MB8294.namprd04.prod.outlook.com>
References: <PH0PR04MB82948BA63F4311389716E1F0C0BA2@PH0PR04MB8294.namprd04.prod.outlook.com>

"Zechman, Derek S" <[email protected]> writes:
> We are getting a segmentation fault which seems to be specific to pg16 on redhat 8.  Tested on pg14 and pg15 with no problems.  Also tested with pg16 on redhat 9 - no issues.  The developer determined that it is specific to select into a defined variable within a function.  We have a reproducible test case that requires no data.  I determined that 2857 is the maximum number that doesn't crash and anything higher than that causes a segfault.  Can anyone help with this problem?

FWIW, I cannot replicate this problem using this script.  Now I'm
testing v16 branch tip not 16.6, but a quick trawl through the git
history didn't find any plausibly-matching bug fixes since 16.6.

Where did you get your Postgres server executable from exactly,
and what options was it built with?  (The output of the matching
version of pg_config would answer that.)  Can you get a stack
trace from the crash?

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

			regards, tom lane

view thread (2+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: segmentation fault
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox