| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Reduce function call costs on ELF platforms |
| Date: | 2021-11-25 16:06:27 |
| Message-ID: | 950df639-0447-17c3-89c4-d651cad63915@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/24/21 22:57, Andres Freund wrote:
>
>> Which things does it break exactly?
> -Bsymbolic causes symbols that are defined and referenced within one shared
> library to use that definition. E.g. if a shared lib has a function
> "do_something()" and some of its code calls do_something(), you cannot use
> LD_PRELOAD (or a definition in the main binary) to redirect the call to
> do_something() inside the shared library to something else.
>
> I.e. if a shared library calls a function that's *not* defined within that
> shared library, -Bsymbolic doesn't have an effect for that symbol.
>
>
>> I have a case where a library that
>> is LD_PRELOADed calls PQsetSSLKeyPassHook_OpenSSL() in its constructor
>> function. I'd be very unhappy if that stopped working (and so would our
>> client).
> Bsymbolic shouldn't affect that at all.
>
Thanks for the explanation.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2021-11-25 17:15:19 | Re: XMAX_LOCK_ONLY and XMAX_COMMITTED (fk/multixact code) |
| Previous Message | Zhihong Yu | 2021-11-25 15:46:51 | Re: Non-decimal integer literals |