Re: ALTER SYSTEM for pg_hba.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER SYSTEM for pg_hba.conf
Date: 2017-01-04 20:30:47
Message-ID: 28418.1483561847@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-01-04 20:35:41 Re: generating fmgr prototypes automatically
Previous Message Robert Haas 2017-01-04 20:29:02 Re: PassDownLimitBound for ForeignScan/CustomScan [take-2]