Re: Proposal: new file format for hba/ident/hosts configuration?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Tristan Partin" <tristan(at)partin(dot)io>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Zsolt Parragi" <zsolt(dot)parragi(at)percona(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Daniel Gustafsson" <daniel(at)yesql(dot)se>
Subject: Re: Proposal: new file format for hba/ident/hosts configuration?
Date: 2026-07-07 21:58:30
Message-ID: 1878371.1783461510@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm noticing a distinct lack of focus on what would be the benefits
to *end users* of Postgres. I can't see proceeding with a project
like this unless there are strong benefits that would entice people
to convert their configuration files of their own accord [*].
And really I don't think any of the benefits enumerated at the top of
the thread are going to sell very many users on doing that. It's
not their problem if we're having issues shoehorning new features
into the existing format.

regards, tom lane

[*] If we try to force it, even by such weak means as not implementing
new features in the old format, we will have mobs of villagers with
pitchforks on our doorsteps.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2026-07-07 22:17:25 Re: heapam_tuple_complete_speculative : remove unnecessary tuple fetch
Previous Message Jacob Champion 2026-07-07 21:48:16 Re: Proposal: new file format for hba/ident/hosts configuration?