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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, 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-20 14:20:04
Message-ID: 1699248.1658326804@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> I suppose you're probably thinking of commit 53ef6c40f1e7; that didn't
> expose functions directly, but through plpgsql_plugin_ptr. Maybe that
> one does need to be made PGDLLEXPORT, since currently it isn't.

Hm. Not sure if the rules are the same for global variables as
they are for functions, but if so, yeah ...

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Justin Pryzby 2022-07-20 14:52:21 [PATCH] Renumber confusing value for GUC_UNIT_BYTE
Previous Message Tom Lane 2022-07-20 14:15:55 Re: Re: pgsql: Default to hidden visibility for extension libraries where possi

Browse pgsql-hackers by date

  From Date Subject
Next Message Önder Kalacı 2022-07-20 14:49:32 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Previous Message Tom Lane 2022-07-20 14:15:55 Re: Re: pgsql: Default to hidden visibility for extension libraries where possi