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-w4HMN1Mg9Xawms35grfw7kGPLCn_mtu4d_Le6AQNe3T1E0A@mail.gmail.com
Whole thread Raw
In response to Re: Providing catalog view to pg_hba.conf file - Patch submission  ("David G. Johnston" <david.g.johnston@gmail.com>)
Responses Re: Providing catalog view to pg_hba.conf file - Patch submission
List pgsql-hackers

On Mon, Mar 16, 2015 at 5:46 PM, David G. Johnston <david.g.johnston@gmail.com> wrote:
​Why not just leave the double-quoting requirements intact.  An unquoted <any> or <sameuser> (etc) would represent the special keyword while the quoted version would mean that the name is used literally.

For users that would be worse than not quoting. Then if they look up users they can't say WHERE username =ANY (users). They would have to do sumersaults like CASE WHEN username = 'all' then '"all"' =ANY (users) else username =ALL (users).

The whole point of having a view should be that you don't need to know the syntax rules for pg_hba.conf to interpret the data. If you do then you might as well just write a parser and read the file.


--
greg

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Providing catalog view to pg_hba.conf file - Patch submission
Next
From: Robert Haas
Date:
Subject: Re: assessing parallel-safety