| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | daniel(at)yesql(dot)se |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Separators in pg_hosts.conf fields |
| Date: | 2026-04-26 21:32:52 |
| Message-ID: | 20260426213252.7a@rfd.leadboat.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
| Attachment | Content-Type | Size |
|---|---|---|
| comma-test-sni-v1.patch | text/plain | 1.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-04-26 21:40:13 | Re: Separators in pg_hosts.conf fields |
| Previous Message | Robert Haas | 2026-04-26 17:12:06 | Re: Use log_newpage_range in HASH index build |