Perhaps the .so name should have been updated for PostgreSQL 7.3? For
example in 7.2 libpq is:
/usr/lib/libpq.so -> libpq.so.2.2 /usr/lib/libpq.so.2 -> libpq.so.2.2 /usr/lib/libpq.so.2.0 -> libpq.so.2
/usr/lib/libpq.so.2.2
and PostgreSQL 7.3:
/usr/lib/libpq.so -> libpq.so.2.2 /usr/lib/libpq.so.2 -> libpq.so.2.2 /usr/lib/libpq.so.2.0 -> libpq.so.2
/usr/lib/libpq.so.2.2
the same. This would seem to imply binary compatibility?
Lee.
Tom Lane writes:> "Jeroen T. Vermeulen" <jtv@xs4all.nl> writes:> > When receiving a trigger notification under 7.3, the
structurereturned> > by PQnotifies() appears to be bogus. In a test I ran, its be_pid was> > consistently zero and its
relnamepointed into never-neverland.> We changed the PQnotifies result structure in 7.3 (to insulate clients> from the
valueof NAMEDATALEN). I think you are compiling your app with> a 7.3 libpq header and then running it with 7.2 libpq
code,or possibly> vice versa.