Re: Providing catalog view to pg_hba.conf file - Patch submission - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Providing catalog view to pg_hba.conf file - Patch submission
Date
Msg-id CAM-w4HP=e5qj-9SZrbHr0ay9FiONrgLH1mP248m3C0MTVN4FdA@mail.gmail.com
Whole thread Raw
In response to Re: Providing catalog view to pg_hba.conf file - Patch submission  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
On Wed, Mar 4, 2015 at 12:17 AM, Jim Nasby <Jim.Nasby@bluetreble.com> wrote:
> I can make these changes if you want.

Personally I'm just not convinced this is worth it. It makes the
catalogs harder for people to read and use and only benefits people
who have users named "all" or databases named "all", "sameuser", or
"samerole" which I can't really imagine would be anyone.

If this were going to be the infrastructure on which lots of tools
rested rather than just a read-only view that was mostly going to be
read by humans that might be different. Are you envisioning a tool
that would look at this view, offer a gui for users to make changes
based on that information, and build a new pg_hba.conf to replace it?

-- 
greg



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Combining Aggregates
Next
From: Greg Stark
Date:
Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission