> On 3 May 2024, at 21:21, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Peter Eisentraut <peter@eisentraut.org> writes:
>> On 03.05.24 10:39, Daniel Gustafsson wrote:
>>> They are no-ops when linking against v18, but writing an extension which
>>> targets all supported versions of postgres along with their respective
>>> supported OpenSSL versions make them still required, or am I missing something?
>
>> I don't think extensions come into play here, since this is libpq, so
>> only the shared library interface compatibility matters.
>
> Yeah, server-side extensions don't really seem to be at hazard,
> but doesn't the argument apply to client-side applications and
> libraries that want to work across different PG/OpenSSL versions?
Right, I was using "extension" a bit carelessly, what I meant was client-side
applications using libpq.
--
Daniel Gustafsson