Re: Serverside SNI support in libpq - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Serverside SNI support in libpq
Date
Msg-id 0DFFD93E-9930-48B1-8282-98816D9F99D9@yesql.se
Whole thread Raw
In response to Re: Serverside SNI support in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Serverside SNI support in libpq
List pgsql-hackers
> On 18 Mar 2026, at 16:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Daniel Gustafsson <daniel@yesql.se> writes:
>> On 18 Mar 2026, at 15:33, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> IIRC longfin is using some fairly old hand-built openssl installation.
>
>> Thanks for confirming, that matches with my local repro which required building
>> 1.1.1 on macOS. Did you build with Apple clang or a a stock clang/gcc?
>
> It's been awhile, but I can't imagine that I didn't use Apple's
> compiler of the time.  [ Checks longfin's host... ]  The files
> in that openssl tree are all dated Nov 20 2018, so it's probably
> due for a refresh in any case.

I've done more testing now and I can only reproduce this with downgraded
versions of OpenSSL 1.1.1, when running the latest 1.1.1x the error goes away
and the error is reported as expected.  Can you try to upgrade your machine,
which I assume isn't running bleeding edge 1.1.1 by the sounds of it.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_plan_advice
Next
From: Fujii Masao
Date:
Subject: Re: Use SIGTERM instead of SIGUSR1 for slotsync worker to exit during promotion?