| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tristan Partin <tristan(at)partin(dot)io>, Andrew Dunstan <andrew(at)dunslane(dot)net>, 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-09 17:23:23 |
| Message-ID: | CAKAnmmJPg=FiD5o3xzXg3Em8o+kras8pHHwsp4VotZ1jreh3Ug@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jul 8, 2026 at 11:42 AM Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
wrote:
> In pg_hba, we already have a way too long "options" column at the end,
> where we store most of the details about external auth providers. If
> an editor doesn't add line breaks, a significant part of the
> configuration is invisible without scrolling right.
But we support backslashes, so there is no need to squash everything onto a
single line, e.g.
host all all 127.0.0.1/32 ldap \
ldapserver=localhost \
ldapbinddn="CN=admin,DC=testy,DC=com" \
ldapbindpasswd="mysecretpass" \
ldapbasedn="OU=Users,DC=testy,DC=com" \
ldapsearchfilter="(&(uid=$username)(memberOf=CN=pg_admins,OU=Groups,DC=testy,DC=com))"
All in all, I am super wary of this whole idea. Not that pg_hba is pretty,
or intuitive, but I second the motion to see what a converted one would
look like. Can the proponents of format X show what our standard default
pg_hba.conf would look like in the new format?
--
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-07-09 17:41:38 | Re: Per-table resync for logical replication subscriptions |
| Previous Message | Daniel Gustafsson | 2026-07-09 17:03:22 | Re: libpq: Process buffered SSL read bytes to support records >8kB on async API |