Re: Undefined symbol error - psql CLI client

From: "Srimal | PickMe" <srimal(at)pickme(dot)lk>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Undefined symbol error - psql CLI client
Date: 2018-12-19 18:22:15
Message-ID: CAMX-PMwjBUfb8072u4E5UFBdQJG7xE4jFq6kf_0=jhuNkJ2nmQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

Yes, it was using an incorrect libpq version which comes with Pipelinedb
(See the attached screenshot). I have uninstalled Pipelinedb since I'm not
using that anymore. The issue is fixed now.

[image: image.png]

Thank you all for the great support.

On Wed, Dec 19, 2018 at 7:51 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> On 2018-Dec-19, Pavel Stehule wrote:
>
> > st 19. 12. 2018 v 12:33 odesílatel Srimal | PickMe <srimal(at)pickme(dot)lk>
> > napsal:
> >
> > maybe there are broken dependency between releases, or some other
>
>
> > >>>>> /usr/lib/postgresql/11/bin/psql: symbol lookup error:
> > >>>>> /usr/lib/postgresql/11/bin/psql: undefined symbol:
> > >>>>> PQsetErrorContextVisibility
>
> I bet there is another libpq that is being picked up.
> PQsetErrorContextVisibility was added in 9.6. Maybe
> ldd /usr/lib/postgresql/11/bin/psql
> would give a clue.
>
> --
> Álvaro Herrera https://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
>

--
*Regards,*

*Srimal*

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Joshua Muzaaya 2018-12-19 21:15:52 Re: Postgres 11 Insufficient columns in PRIMARY KEY constraint definition
Previous Message Alvaro Herrera 2018-12-19 16:49:17 Re: Postgres 11 Insufficient columns in PRIMARY KEY constraint definition