Re: pgsql: Default to hidden visibility for extension libraries where possi

From: Andres Freund <andres(at)anarazel(dot)de>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Default to hidden visibility for extension libraries where possi
Date: 2022-07-19 22:44:35
Message-ID: 20220719224435.yhqb6yygirit7xuf@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Hi,

On 2022-07-19 08:31:49 -0700, Andres Freund wrote:
> But I think we probably should err on the side of adding more
> declarations, rather than the oposite.

To see if there's other declarations that should be added, I used
https://codesearch.debian.net/search?q=load_external_function&literal=1&perpkg=1

which shows plpgsql_check and hstore_pllua. All the hstore symbols for
the latter are exported already.

Greetings,

Andres Freund

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2022-07-20 00:36:09 pgsql: Add regression test for TRUNCATE on foreign table not supporting
Previous Message Andres Freund 2022-07-19 22:39:30 Re: pgsql: Default to hidden visibility for extension libraries where possi

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-07-19 23:08:55 Re: Convert planner's AggInfo and AggTransInfo to Nodes
Previous Message Andres Freund 2022-07-19 22:39:30 Re: pgsql: Default to hidden visibility for extension libraries where possi