Separators in pg_hosts.conf fields
Noah Misch <noah@leadboat.com>
From: Noah Misch <noah@leadboat.com>
To: daniel@yesql.se
Cc: pgsql-hackers@postgresql.org
Date: 2026-04-26T21:32:52Z
Lists: pgsql-hackers
Attachments
- comma-test-sni-v1.patch (text/plain) patch v1
If the build directory name contains a comma, src/test/modules/ssl_passphrase_callback fails on master since commit 4f43302. It fails because hba.c:next_token() treats a comma as a token separator: * Tokens can be delimited by double quotes (this allows the inclusion of * commas, blanks, and '#', but not newlines). As in SQL, write two * double-quotes to represent a double quote. Commit 4f43302 documented the pg_hosts.conf hostname field as a comma-separated list, but not the other fields. Should other pg_hosts.conf fields continue to require quoting around commas, or not?
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix new test with comma in build directory.
- f9c638054c5b 19 (unreleased) landed
-
ssl: Serverside SNI support for libpq
- 4f433025f666 19 (unreleased) cited