On Mon, Aug 15, 2016 at 11:45 PM, Peter Eisentraut <peter.eisentr...@2ndquadrant.com> wrote: > If we instead installed > > libpq.so.5 (actual file) > libpq.so -> libpq.so.5 > > nothing would effectively change.
It would make it impossible to have multiple versions installed. One doesn't normally have multiple versions with the same soname installed since the linker will only be actually using one of them anyways but it makes it a lot easier to manage transitions and debugging. I don't think it would be very standard to not have a minor version at all. Also, the above is only true for Linux. Other operating systems may set things up differently. IIRC NetBSD did do something a lot more sophisticated where it linked to the correct minor version or gave a warning and linked with a newer minor version but refused to link to older minor versions even if it was the right major version -- or something like that. But I think Tom was not proposing dropping the minor version at all, just setting the minor version equal to the release. So the our soname would be libpq.so.5.10 then libpq.so.5.11 and so on until we make an incompatible change and then it would become libpq.so.6.12 for example. I think it would be a bit confusing to see both the minor and major version bump and to see a major version start at a high number. But sonames are pretty technical internal goo and it's not too bad. I think it would be a reasonable idea. It does rule out the possibility of having a minor bump in the soname for a point-release, which as you point out wouldn't do much on Linux but on other operating systems might be a useful thing. -- greg -- Sent via pgsql-hackers mailing list (email@example.com) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers