On Fri, Feb 14, 2014 at 03:28:23AM -0500, Stephen Frost wrote: > Bruce, > > * Bruce Momjian (br...@momjian.us) wrote: > > On Thu, Feb 13, 2014 at 08:24:27PM -0600, Jerry Sievers wrote: > > > I'm aware of how a pg_hba.conf file can refer to other files for > > > including @lists of users, etc. > > > > > > But there is currently no support for being able to pull in entire file > > > segments as can be done for postgresql.conf via the include directive. > > > > > > In the environment that I'm managing, we are using a makefile to stick > > > together a common header with a custom section for any of several > > > clusters and may extend this further to permit additional includes for > > > hba rules common to groupings of clusters. > > > > > > Anyway, please advise. I don't recall hearing anything like this > > > discussed. > > > > > > Has been proposed, discussed and voted down? Or never mentioned? > > > > I have never heard of anyone request this. > > I've brought it up on various threads before, including both the ALTER > SYSTEM thread and the postgresql.conf 'includes' thread, though I don't > feel like going back and hunting down the specific emails right now. > > Having @include and directory.d-style capabilities for pg_hba.conf *and* > pg_ident.conf would make managing larger environments much better. > There has been some talk about providing those capabilities via tables > in the catalog, but I'm not aware of anyone working on it and it'd > certainly be quite a bit more work than adding include/dir.d options.
Do we want a TODO for this? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
