| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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-09 21:43:17 |
| Message-ID: | CAOYmi+=jc2v38sXm_nG5HFw04ud9so28Qh5brWpisjBOVFdsBw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--Jacob
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-07-09 21:52:44 | Re: Introduce XID age based replication slot invalidation |
| Previous Message | Andrew Dunstan | 2026-07-09 21:19:30 | Re: Proposal: new file format for hba/ident/hosts configuration? |