Skip site navigation (1) Skip section navigation (2)

soname of libpq

From: Federico Di Gregorio <fog(at)initd(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: soname of libpq
Date: 2004-05-18 08:32:36
Message-ID: 1084869156.2914.14.camel@localhost (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
Hi *,

I don't know if this is really a bug but surely is something that is
giving a lot of problems to psycopg (pyhton/postgresql adapter). psycopg
1.1.11+ checks for libpq version at runtime and, if available uses the
new protocol api (mainly to extract non-localized error codes after
errors). now, the problem is that a *lot* of users have two different
libpq versions of their systems and usually psycopg gets compiled
against 7.4 and runtime-linked against 7.3, resulting in an error
(symbols not found).

the question is: there is any special reason to change the api of a
library and *not* change the soname? having changed the soname of the
library would have avoided this kind of problems.

thank you in advance for your time,

Federico Di Gregorio               
Debian GNU/Linux Developer                                fog(at)debian(dot)org
INIT.D Developer                                           fog(at)initd(dot)org
  We are all dust, Saqi, so play the lute
                    We are all wind, Saqi, so bring wine. -- Omar Khayam

pgsql-bugs by date

Next:From: Adam KempaDate: 2004-05-18 13:52:28
Subject: postgres crashes
Previous:From: Fabien COELHODate: 2004-05-18 07:10:30
Subject: Re: BUG #1145: silent REVOKE failures

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group