From: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
---|---|
To: | "Oliver Kohll *EXTERN*" <oliver(at)gtwm(dot)co(dot)uk>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: libpq.so.4 |
Date: | 2008-06-08 19:46:49 |
Message-ID: | D960CB61B694CF459DCFB4B0128514C2023099CA@exadv11.host.magwien.gv.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2008-06-08 20:27:10 | Re: libpq.so.4 |
Previous Message | Alvaro Herrera | 2008-06-08 18:18:05 | Re: temporarily deactivate an index |