> > To answer your question, there are no pending changes in libpq that
> > would mandate a major version bump (ie, nothing binary-incompatible,
> > AFAIK). We could ship it with the exact same version number, but then
> > how are people to tell whether they have a 7.0 or 7.1 libpq?
>
> If there isn't any changes, why bump it?
This is huge software. There are changes to every library in every
major release, major for us meaning, i.e., 7.0->7.1. That is why I bump
the numbers.
The interesting issue is that the version number changes for .so do
_not_ mean they only talk with servers of the same release. They will
talk to future servers of higher release numbers. This is done because
there is a backend protocol number that is passed from client to server
which determines how the server should behave with that client.
We can't always have new clients talking to older servers because the
old servers may not know the newer protocol. We could get fancy and
trade version numbers and try to get it working, but it has not been a
priority, and few have asked for it. Having old clients talking to new
databases has been enough for most users.
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill,
Pennsylvania19026
