Re: Serverside SNI support in libpq

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Serverside SNI support in libpq
Date: 2026-10-06 14:57:35
Message-ID: CAOYmi+keJ3xYDXNn1pvmW8EeQfKa58DMi=+FQrBcVnLbjYMvnw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Oct 3, 2026 at 12:49 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> Zsolt also reported two small issues off-list which are solved in 0004 and
> 0005. On a failed reload of non-SNI configuration we could be left with
> dangling pointers to the previous config GUC values.

Hm. (Are we going to need to build an atomicity system for GUC itself?
It sure seems like we should have the toolset for it...)

--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Manu 2026-10-06 15:07:54 Re: Logical replication: lost updates/deletes and invalid log messages caused by SnapshotDirty + concurrent updates
Previous Message Robert Haas 2026-10-06 14:49:45 Re: pgsql: Teach expr_is_nonnullable() to handle more expression types