Re: PG 14.1 psql: symbol lookup error: psql: undefined symbol: PQmblenBounded

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Lembark, Steven" <Steven(dot)Lembark(at)broadridge(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: PG 14.1 psql: symbol lookup error: psql: undefined symbol: PQmblenBounded
Date: 2021-11-22 17:05:43
Message-ID: 3766309.1637600743@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Lembark, Steven" <Steven(dot)Lembark(at)broadridge(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message marrow.yung 2021-11-22 17:29:42 RE: BUG #17286: Installing open source edition of PostgreSQL 11.14 will fail
Previous Message Ronan Dunklau 2021-11-22 16:14:27 Re: table unreadable after altering related table embedded via a view