"Zechman, Derek S" <derek.s.zech...@snapon.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
