From: Tom Lane <tgl@sss.pgh.pa.us>
To: gmirocha@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18364: psql execution error: Segmentation fault
In-reply-to: <18364-d795323ccf002b99@postgresql.org>
References: <18364-d795323ccf002b99@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Mon, 26 Feb 2024 12:03:11 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1799637.1708961917.1@sss.pgh.pa.us>
Date: Mon, 26 Feb 2024 10:38:37 -0500
Message-ID: <1799638.1708961917@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1799638.1708961917%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> After upgrade Postgresql from 16.1 to 16.2 in both CENTOS 7 and RHEL 8 I'm
> getting the segmentation fault error when I try to execute any "\" command
> on psql. I have got this error in different hosts, plataforms, etc.

Given the location of the error, it seems like you might have a
problem with inconsistent ABI for "flex".  I'm not quite sure
how you'd get there, because that's usually pretty self-contained.
(Once there was a "libfl.a" that could possibly cause this sort of
problem, but I don't think that exists in modern flex versions.)
Anyway, I'd check that you have a consistent installation of flex
and then rebuild Postgres from source.

			regards, tom lane