Horton
Menu

Re: Serverside SNI support in libpq

Daniel Gustafsson <daniel@yesql.se>

View thread
From: Daniel Gustafsson <daniel@yesql.se>
To: Michael Banck <mbanck@gmx.net>
Cc: Zsolt Parragi <zsolt.parragi@percona.com>, Jacob Champion <jacob.champion@enterprisedb.com>, Jelte Fennema-Nio <postgres@jeltef.nl>, Heikki Linnakangas <hlinnaka@iki.fi>, Dewei Dai <daidewei1970@163.com>, "li.evan.chao" <li.evan.chao@gmail.com>, Michael Paquier <michael@paquier.xyz>, Andres Freund <andres@anarazel.de>, Pgsql Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2026-03-19T09:45:07Z
Lists: pgsql-hackers 
> On 19 Mar 2026, at 10:39, Michael Banck <mbanck@gmx.net> wrote:

> I'm really late to the part, but I did not see it discussed elsewhere on
> a quick glance: Isn't pg_hosts.conf a really (too) generic name for this
> feature? I don't want to open a huge bikeshedding sub-thread, but was a
> more specific filename considered?

I don't recall any discussion on that, and I don't really see a problem off the
cuff.  As it is a config file for defining hostnames and their config, in which
way do you feel its too generic and what would "claiming that name" for this
prevent (or how would it confuse)? Do you have any alternative suggestions?

--
Daniel Gustafsson

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Declare load_hosts() as returning HostsFileLoadResult.

  2. ssl: Skip passphrase reload tests in EXEC_BACKEND builds

  3. ssl: Serverside SNI support for libpq

  4. ssl: Add tests for client CA