Re: PQnotifies() in 7.3 broken?

From: Lee Kindness <lkindness(at)csl(dot)co(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Lee Kindness <lkindness(at)csl(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PQnotifies() in 7.3 broken?
Date: 2002-12-04 16:50:14
Message-ID: 15854.12870.753888.434010@kelvin.csl.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)xs4all(dot)nl> writes:
> > When receiving a trigger notification under 7.3, the structure returned
> > by PQnotifies() appears to be bogus. In a test I ran, its be_pid was
> > consistently zero and its relname pointed into never-neverland.
> We changed the PQnotifies result structure in 7.3 (to insulate clients
> from the value of 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Manfred Koizar 2002-12-04 16:54:30 Re: nested transactions
Previous Message Rod Taylor 2002-12-04 16:43:21 Re: interesting difference for queries...