From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Lembark, Steven" <Steven.Lembark@broadridge.com>
cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Subject: Re: PG 14.1 psql: symbol lookup error: psql: undefined symbol:
 PQmblenBounded
In-reply-to: 
 <BN0PR20MB3912AA107FA6E90FB6B0A034FD9F9@BN0PR20MB3912.namprd20.prod.outlook.com>
References: 
 <BN0PR20MB3912AA107FA6E90FB6B0A034FD9F9@BN0PR20MB3912.namprd20.prod.outlook.com>
Comments: In-reply-to "Lembark, Steven" <Steven.Lembark@broadridge.com>
	message dated "Mon, 22 Nov 2021 16:09:44 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3766308.1637600743.1@sss.pgh.pa.us>
Date: Mon, 22 Nov 2021 12:05:43 -0500
Message-ID: <3766309.1637600743@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3766309.1637600743%40sss.pgh.pa.us>
Precedence: bulk

"Lembark, Steven" <Steven.Lembark@broadridge.com> writes:
> New installation of PG-14.1 from tarball on RH 8.3 built with gcc-11
> using CFLAGS='-O2 -march=native -pipe' (didn't seem particularly 
> exotic). Sample session is shown below, error appears to happen 
> more-or-less randomly: using "\l+" or "\db+" has caused it a few 
> times. Restarting the psql session and re-issuing the same commands
> does not cause a repeatable error. 

Hmph.  PQmblenBounded is exported by recent versions of libpq.so,
so this would seem to be telling us that psql is sometimes binding
to an older libpq.so.  Most likely the older one is in /usr/lib64
or some other standard place while you dropped the newer one someplace
else.  That's not a usage that Linux is terribly friendly to; you
have to be sure that the executable includes an rpath option pointing
to "someplace else", or that you consistently set the LD_LIBRARY_PATH
environment variable.  The fact that the failure is inconsistent
seems odd, so I'm not sure quite which way it's going wrong for you.

			regards, tom lane