From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Pgsql Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Serverside SNI support in libpq |
Date: | 2025-08-27 19:49:34 |
Message-ID: | F585452A-1F69-4658-A7E8-D1273AC663ED@yesql.se |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 13 May 2025, at 15:46, Andres Freund <andres(at)anarazel(dot)de> wrote:
> This is not passing CI on windows...
> https://cirrus-ci.com/build/4765059278176256
When looking into why the SNI tests failed on Windows I think I found a
pre-existing issue that we didn't have tests for, which my patch added tests
for and thus broke.
The test I added was to check restarting and reloading with ssl passphrase
commands (which we do have testcoverage for) with a subsequent connection test
to ensure it didn't just work to start the cluster.
When ssl_passphrase_command_supports_reload is set to 'off', the cluster should
allow connections until a reload has been issued. That works fine except on
Windows where our process-model is such that a new connection will re-run the
passphrase command, which inevitably fails as it's not configured for reload.
The test in my patch exposed this out of (happy) accident, but it can be
reproduced in HEAD as well. The attached version modifies the ssl tests to
cover this with a connection attempt. If I'm not mistaken though, there should
probably be a docs patch to make it clear how this works on Windows.
No codechanges on top of the test fix.
--
Daniel Gustafsson
Attachment | Content-Type | Size |
---|---|---|
v8-0001-Serverside-SNI-support-for-libpq.patch | application/octet-stream | 56.1 KB |
From | Date | Subject | |
---|---|---|---|
Previous Message | Greg Burd | 2025-08-27 19:42:48 | Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock |