Re: Serverside SNI support in libpq

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Dewei Dai <daidewei1970(at)163(dot)com>, "li(dot)evan(dot)chao" <li(dot)evan(dot)chao(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de>, Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Serverside SNI support in libpq
Date: 2026-03-18 19:03:49
Message-ID: 01773724-A4E8-4A9D-B596-900DCEF3FE56@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 18 Mar 2026, at 19:39, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> 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.
>
> Nope, it was still on 1.1.1a.

Wow, that was almost an Antiques Roadshow material candidate =)

> I've now updated it to 3.0.19,
> which appears to be the oldest available-to-the-public supported
> version. I doubt that continuing to test 1.1.1-anything is really
> useful.

I don't disagree, 1.1.1 went EOL a long time ago, but since we still support
1.1.1 we need to test it somewhere. I believe we have sufficient coverage
though, and I personally test on 1.1.1 through 3.6 (and will start testing 4
soon).

> ... and longfin is now green.

Great, thanks!

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Davis 2026-03-18 19:06:48 Re: [19] CREATE SUBSCRIPTION ... SERVER
Previous Message Lukas Fittl 2026-03-18 18:59:46 Re: pg_plan_advice