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

Re: libpq API incompatibility between 7.4 and 8.0

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Martin Pitt <mpitt(at)debian(dot)org>, pgsql-hackers(at)postgresql(dot)org,Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Subject: Re: libpq API incompatibility between 7.4 and 8.0
Date: 2005-02-02 18:04:18
Message-ID: 493.1107367458@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> We can rectify the mistake, but then we need to change the SONAME.  
> That's what it's for.

Well, if you just want to bump libpq's SO_MAJOR_VERSION, I won't object.

This brings up a point that I think has been discussed before: we
operate on the assumption that incrementing SO_MINOR_VERSION is enough
to distinguish different releases of libpq, but in point of fact it
is not.  The Linux conventions for library names, for one, essentially
require us to bump SO_MAJOR_VERSION for every release if we want to have
any hope of letting different versions coexist.  Perhaps our convention
should be to bump SO_MAJOR_VERSION for each of our major releases and
only use SO_MINOR_VERSION when we change a library in a dot-release.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2005-02-02 18:27:49
Subject: Re: libpq API incompatibility between 7.4 and 8.0
Previous:From: Bruce MomjianDate: 2005-02-02 17:56:08
Subject: Re: Connect By for 8.0

pgsql-patches by date

Next:From: Bruce MomjianDate: 2005-02-02 18:27:49
Subject: Re: libpq API incompatibility between 7.4 and 8.0
Previous:From: Peter EisentrautDate: 2005-02-02 17:52:03
Subject: Re: libpq API incompatibility between 7.4 and 8.0

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