MIME-Version: 1.0
References: 
 <CAN4CZFNXdKL4eb_GwT_h-vUuUV+CbPCk_8-+S3kV8iFmNmUw7A@mail.gmail.com>
 <DJSICZEWRJBC.XT5U5929XT0N@partin.io>
 <CAD5tBc+ki9ynMuFRkFCCXVtyOO7HaEU7EEdGKA1LWgofNgdNOQ@mail.gmail.com>
 <CAOYmi+m8PrWyhY7diTA+UTGNNzQ8eCZZLRA07LTuzj4VCBaudA@mail.gmail.com>
 <CAN4CZFPQiNvfX2k35zYi9eZ7-kC5vEeQtiM_nOce3MNpK4Ai_w@mail.gmail.com>
 <CAD5tBcLFQvaV7+-onng6DUAJFZY9KFvP4w3XOxQp6X0_AHi+YQ@mail.gmail.com>
In-Reply-To: 
 <CAD5tBcLFQvaV7+-onng6DUAJFZY9KFvP4w3XOxQp6X0_AHi+YQ@mail.gmail.com>
From: Zsolt Parragi <zsolt.parragi@percona.com>
Date: Thu, 9 Jul 2026 14:31:34 +0100
Message-ID: 
 <CAN4CZFPT0zwQU4PMqR0+g9bpTD9oC_VH5AE9yZV7J_j08a2JhA@mail.gmail.com>
Subject: Re: Proposal: new file format for hba/ident/hosts configuration?
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Jacob Champion <jacob.champion@enterprisedb.com>,
 Tristan Partin <tristan@partin.io>,
	PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: 
 <https://www.postgresql.org/message-id/CAN4CZFPT0zwQU4PMqR0%2Bg9bpTD9oC_VH5AE9yZV7J_j08a2JhA%40mail.gmail.com>
Precedence: bulk

> Just for kicks I asked my new best friend (<weg>) to allow for json5 on the RD parser. The actual parser changes are minimal. Most of the changes are in the lexer. I didn't implement it for the incremental parser, and I skipped the new numeric formats.

I also have a patchset for that, which also includes a JSON5 SQL type.
I plan to start another thread about that, as it could be useful
independent to the configuration file changes.