Re: Serverside SNI support in libpq
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Pgsql Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-12-04T13:44:18Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
ssl: Serverside SNI support for libpq
- 4f433025f666 19 (unreleased) landed
-
ssl: Add tests for client CA
- 25e568ba7ce7 19 (unreleased) landed
Attachments
- v3-0001-Serverside-SNI-support-for-libpq.patch (application/octet-stream) patch v3-0001
> On 4 Dec 2024, at 01:43, Jacob Champion <jacob.champion@enterprisedb.com> wrote: > > On Tue, Dec 3, 2024 at 5:58 AM Daniel Gustafsson <daniel@yesql.se> wrote: >>> Have you seen any weird behavior like this on your end? I'm starting >>> to doubt my test setup... >> >> I've not been able to reproduce any behaviour like what you describe. > > Hm, v2 is different enough that I'm going to need to check my notes > and try to reproduce again. At first glance, I am still seeing strange > reload behavior (e.g. issuing `pg_ctl reload` a couple of times in a > row leads to the server disappearing without any log messages > indicating why). > >>> On the plus side, I now have a handful of >>> debugging patches for a future commitfest. >> >> Do you have them handy for running tests on this version? > > I'll work on cleaning them up. I'd meant to contribute them > individually by now, but I got a bit sidetracked... No worries, I know you have a big path on your plate right now. The attached v3 fixes a small buglet in the tests and adds silly reload testing to try and stress out any issues. -- Daniel Gustafsson