comma-test-sni-v1.patch
text/plain
Filename: comma-test-sni-v1.patch
Type: text/plain
Part: 0
Message:
Separators in pg_hosts.conf fields
Patch
Same data as JSON:
GET /api/v1/attachments/:id/patch
the parsed metadata as JSON — format, series position, per-file stats; never the diff bytes.
API reference →
Format: unified
Series: patch v1
| File | + | − |
|---|---|---|
| src/test/modules/ssl_passphrase_callback/t/001_testfunc.pl | 2 | 2 |
commit 4649408 (HEAD, master)
Author: Noah Misch <noah@leadboat.com>
AuthorDate: Sun Apr 26 13:56:22 2026 -0700
Commit: Noah Misch <noah@leadboat.com>
CommitDate: Sun Apr 26 14:26:08 2026 -0700
Fix new test under comma in build directory.
Quote pg_hosts.conf fields derived from the build directory, since
hba.c:next_token() treats a comma as a token separator. Commit
4f433025f666fa4a6209f0e847715767fb1c7ace introduced pg_hosts.conf and
this test. A build directory name containing a comma worked before that
commit. A build directory name containing a quote character has not
worked, so don't handle that.
---
src/test/modules/ssl_passphrase_callback/t/001_testfunc.pl | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/test/modules/ssl_passphrase_callback/t/001_testfunc.pl b/src/test/modules/ssl_passphrase_callback/t/001_testfunc.pl
index 09ff536..d8b07d4 100644
--- a/src/test/modules/ssl_passphrase_callback/t/001_testfunc.pl
+++ b/src/test/modules/ssl_passphrase_callback/t/001_testfunc.pl
@@ -90,8 +90,8 @@ ssl_sni = on
});
$node->append_conf(
'pg_hosts.conf', qq{
-example.org $ddir/server.crt $ddir/server.key "" "echo FooBaR1" on
-example.com $ddir/server.crt $ddir/server.key "" "echo FooBaR1" on
+example.org "$ddir/server.crt" "$ddir/server.key" "" "echo FooBaR1" on
+example.com "$ddir/server.crt" "$ddir/server.key" "" "echo FooBaR1" on
});
# If the servers starts and runs, the bad ssl_passphrase.passphrase was