Re: libpq.so.4 - Mailing list pgsql-general

From Albe Laurenz
Subject Re: libpq.so.4
Date
Msg-id D960CB61B694CF459DCFB4B0128514C2023099CA@exadv11.host.magwien.gv.at
Whole thread Raw
In response to libpq.so.4  (Oliver Kohll <oliver@gtwm.co.uk>)
Responses Re: libpq.so.4  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-general
Oliver Kohll wrote:
> I have the same issue as this poster with libpq.so.4:
> http://www.nabble.com/8.3.0-upgrade-td16093803.html
>
> In short, I've upgraded to 8.3.1 from 8.1 on RHEL 4 (with
> some CentOS packages). I have apps with dependencies of
> libpq.so.4 but this is no longer available. 8.3.1 provides
> libpq.so.5 and the compat-libs provide libpq.so.3.

Strange; does anybody know why?

> At the moment maintaining package management integrity is not
> a must - getting back to 100% package-controlled files can
> wait until the machine is replaced. Upgrading the dependent
> software is not an option.
> With that in mind, any suggestions on options?
>
> What I've thought of trying so far is
> 1) creating a symlink called libpq.so.4 towards libpq.so.5 -
> slightly dangerous due to possible API changes?

Don't even think about it.

> 2) extracting a copy of libpq.so.4 from the previous RPM
> release of postgres and manually uploading it

You can do that if all else fails.

> 3) building a custom compat package - I don't know how to do
> this though.

Then that's probably not an option for you...

Yours,
Laurenz Albe

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: temporarily deactivate an index
Next
From: Peter Eisentraut
Date:
Subject: Re: libpq.so.4