Re: Conflicting function name in dynamically-loaded shared library - Mailing list pgsql-general

From Adam Mackler
Subject Re: Conflicting function name in dynamically-loaded shared library
Date
Msg-id 20150129222701.GB43952@scruffle.mackler.org
Whole thread Raw
In response to Re: Conflicting function name in dynamically-loaded shared library  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-general
On Wed, Jan 28, 2015 at 11:23:15AM +0000, Albe Laurenz wrote:

> If you are on Linux, you could try the following patch:
>
> http://www.postgresql.org/message-id/CA+CSw_tPDYgnzCYW0S4oU0mTUoUhZ9pc7MRBPXVD-3Zbiwni9w@mail.gmail.com
>
> ...
> Renaming one of the functions seems like the best thing to do.

I am using FreeBSD, so RTLD_DEEPBIND is not supported by my dlopen().

However, your suggestion to rename the function seems at least as
good.  Patching PostgreSQL would just mean trading difficulties when
upgrading the third-party library for difficulties when upgrading
PostgreSQL.

Thank you for the response and insight.

--
Adam Mackler


pgsql-general by date:

Previous
From: Michael Heaney
Date:
Subject: Re: Server statistics monitoring?
Next
From: Alex Hunsaker
Date:
Subject: Re: segmentation fault postgres 9.3.5 core dump perlu related ?