Re: Conflicting function name in dynamically-loaded shared library

From: Adam Mackler <pgsql-general(at)mackler(dot)org>
To: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Conflicting function name in dynamically-loaded shared library
Date: 2015-01-29 22:27:01
Message-ID: 20150129222701.GB43952@scruffle.mackler.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Alex Hunsaker 2015-01-29 23:09:33 Re: segmentation fault postgres 9.3.5 core dump perlu related ?
Previous Message Michael Heaney 2015-01-29 22:20:44 Re: Server statistics monitoring?