| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zechman, Derek S" <Derek(dot)S(dot)Zechman(at)snapon(dot)com> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: segmentation fault |
| Date: | 2025-04-23 19:23:20 |
| Message-ID: | 1436822.1745436200@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"Zechman, Derek S" <Derek(dot)S(dot)Zechman(at)snapon(dot)com> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pawel Veselov | 2025-04-23 20:02:25 | Re: Dump version issues |
| Previous Message | Adrian Klaver | 2025-04-23 19:13:32 | Re: Dump version issues |