| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
| Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, Tristan Partin <tristan(at)partin(dot)io>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Proposal: new file format for hba/ident/hosts configuration? |
| Date: | 2026-07-11 12:43:26 |
| Message-ID: | CAD5tBcLsS==7zUZKJuD8bd=UTCTJYCJrTRUSPCWrm+UMkRDpWQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 9, 2026 at 5:43 PM Jacob Champion <
jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> On Thu, Jul 9, 2026 at 2:19 PM Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> >> Freeze the parsing of old-style files; new features and changes go only
> in the new format. This should eliminate (well, almost eliminate) the
> maintenance burden associated with having two file formats.
> >
> > That's the scenario Tom warned against upthread.
>
> But if, hypothetically, a new format were indeed a big improvement for
> people, it's probably what we should do.
>
>
>
I think the bar is going to be fairly high. And just jumping to a new
format is going to create a world of pain for users. We'd need to carry the
old format for a while as well, I think, and also provide some conversion
tools.
I do agree that sometimes the formats can make expressiveness very clumsy.
A recent example is the log_min_messages work.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ZizhuanLiu X-MAN | 2026-07-11 14:28:02 | Re: support create index on virtual generated column. |
| Previous Message | Alexander Korotkov | 2026-07-11 12:18:56 | Re: SQL/JSON json_table plan clause |