| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Pavel Raiskup <praiskup(at)redhat(dot)com>, pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Shared PostgreSQL libraries and symbol versioning |
| Date: | 2018-04-09 20:15:54 |
| Message-ID: | 873d8c93-d8c0-93b1-9f8a-5f5dc6880add@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/5/18 02:04, Pavel Raiskup wrote:
> Hello, for the support of multiple versions of PostgreSQL RPM packages on
> one system, we are thinking about having only one libpq.so.5
> (libecpg.so.6, libpgtype.so.3 respectively) supported and about building
> (linking) all the PostgreSQL package versions against that. The pattern
> would mean that we'd have to update the system-wide libraries before
> adding support for new PostgreSQL major version and that the older
> packages (say version =< 9.6) would be run against libs from newer PG
> package (say libpq.so.5 from v10).
>
> Do you think it is a good idea in general?
yes
> 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
It's not clear to me why you would need these, given that Debian has
been doing this for many years without this.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-04-09 20:23:44 | Re: Shared PostgreSQL libraries and symbol versioning |
| Previous Message | Andres Freund | 2018-04-09 20:04:20 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |