Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.2\))
Subject: Re: Separators in pg_hosts.conf fields
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <20260426215425.82@rfd.leadboat.com>
Date: Mon, 27 Apr 2026 00:01:03 +0200
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8E3354F-C838-4509-95D3-8A347B1B24E1@yesql.se>
References: <20260426213252.7a@rfd.leadboat.com>
 <9E767D01-08A1-4DF1-8122-B11AD932C8BA@yesql.se>
 <20260426215425.82@rfd.leadboat.com>
To: Noah Misch <noah@leadboat.com>
Archived-At: 
 <https://www.postgresql.org/message-id/B8E3354F-C838-4509-95D3-8A347B1B24E1%40yesql.se>
Precedence: bulk

> On 26 Apr 2026, at 23:54, Noah Misch <noah@leadboat.com> wrote:
> On Sun, Apr 26, 2026 at 11:40:13PM +0200, Daniel Gustafsson wrote:

>> Yes, only the hostname field is a comma-separated list.  I think this =
should be
>> added to the documentation as well on top of the test fix in your =
patch.
>=20
> Do you anticipate docs like "this isn't a list, but the file's general =
parsing
> rules require quotes if there's a comma"?  Or something different?

Something along those lines yes.

>> Do you want me to take care of both parts?
>=20
> That's fine.  I also don't mind pushing what I sent.

+1, please do.

--
Daniel Gustafsson