Re: Shared PostgreSQL libraries and symbol versioning - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Shared PostgreSQL libraries and symbol versioning
Date
Msg-id 18591.1523307873@sss.pgh.pa.us
Whole thread Raw
In response to Re: Shared PostgreSQL libraries and symbol versioning  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Shared PostgreSQL libraries and symbol versioning  (Pavel Raiskup <praiskup@redhat.com>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Peter Eisentraut (peter.eisentraut@2ndquadrant.com) wrote:
>> On 4/5/18 02:04, Pavel Raiskup wrote:
>>> As a followup thought; there are probably two major obstacles ATM
>>> - the DSOs' symbols are not yet versioned, and
>>> - the build-system doesn't seem to know how to -lpq link against
>>> external libpq.so

> I've not looked but neither of those strike me as terribly difficult to
> overcome, assuming they need to be overcome.

I'm not excited about introducing YA cross-platform difference in our
library/linking behavior without fairly strong evidence that it's
necessary.  The available evidence points in the other direction.

As for linking against an external .so, commit dddfc4cb2 just went to
some lengths to make sure that that *wouldn't* happen.  But as long
as all the builds expect libpq.so to end up in the same place after
installation, I doubt it matters much what happens at build time.
You just need to control which build actually installs it.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Mark Dilger
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS
Next
From: Andres Freund
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS