Shared PostgreSQL libraries and symbol versioning

Поиск
Список
Период
Сортировка
От Pavel Raiskup
Тема Shared PostgreSQL libraries and symbol versioning
Дата
Msg-id 5261375.z5KIV9Ssac@nb.usersys.redhat.com
обсуждение исходный текст
Ответы Re: Shared PostgreSQL libraries and symbol versioning  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Список pgsql-hackers
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?  Seems like pg.org [1]
packaging for Debian is doing that already.

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

. but technically this this is fixable; so would it be acceptable to
talk about having those two points fixed?

[1] https://www.postgresql.org/download/linux/debian/

Thanks,
Pavel





В списке pgsql-hackers по дате отправления:

Предыдущее
От: Etsuro Fujita
Дата:
Сообщение: Re: [HACKERS] Add support for tuple routing to foreign partitions
Следующее
От: Amit Kapila
Дата:
Сообщение: Re: [HACKERS] Restrict concurrent update/delete with UPDATE ofpartition key