Re: [HACKERS] ALTER SYSTEM for pg_hba.conf - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] ALTER SYSTEM for pg_hba.conf
Date
Msg-id 28418.1483561847@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] ALTER SYSTEM for pg_hba.conf  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] ALTER SYSTEM for pg_hba.conf  (Simon Riggs <simon@2ndquadrant.com>)
Re: [HACKERS] ALTER SYSTEM for pg_hba.conf  (Robert Haas <robertmhaas@gmail.com>)
Re: [HACKERS] ALTER SYSTEM for pg_hba.conf  (Euler Taveira <euler@timbira.com.br>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> My next thought is ALTER SYSTEM support for pg_hba.conf, especially
> since that would make it easier to do a formal test of Haribabu's
> pg_hba view patch by adding each of the options one by one and then
> juggling them.

It's quite unclear from this spec what you have in mind to control the
entry order.  Also, I'd personally be -1 on inventing a pile of new SQL
keywords for this.  Why not do it with a function, instead?  Or for extra
credit, finish the pg_hba view work first and then make it an updatable
view.

> ....and we can then have a nice simple
> ALTER SYSTEM ENABLE REMOTE ACCESS FOR REPLICATION USING md5;

I am minus a lot more than 1 on inventing a new SQL statement every time
somebody thinks of a new way in which they'd like to frob pg_hba.conf.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] PassDownLimitBound for ForeignScan/CustomScan [take-2]
Next
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] generating fmgr prototypes automatically