Oliver Kohll <oliver@xxxxxxxxxx> writes: > 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? Worth trying. According to the CVS logs http://archives.postgresql.org/pgsql-committers/2006-04/msg00341.php the ABI break from .4 to .5 was simply to stop exporting symbols that weren't officially part of the API. So a symlink would work for applications that played by the rules, and if you have any that didn't the failure will be pretty obvious. > 2) extracting a copy of libpq.so.4 from the previous RPM release of > postgres and manually uploading it That would work too. > 3) building a custom compat package - I don't know how to do this > though. If you got the 8.3 package from someplace they should have an 8.1 compat package too. regards, tom lane
