From: | Jim Nasby <jim(at)nasby(dot)net> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Jerry Sievers <gsievers19(at)comcast(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: HBA files w/include support? |
Date: | 2014-02-16 20:43:11 |
Message-ID: | 530122DF.5040508@nasby.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/14/14, 1:06 PM, Jeff Janes wrote:
> On Fri, Feb 14, 2014 at 6:33 AM, Bruce Momjian <bruce(at)momjian(dot)us <mailto:bruce(at)momjian(dot)us>> wrote:
>
> On Fri, Feb 14, 2014 at 03:28:23AM -0500, Stephen Frost wrote:
> > Bruce,
>
> > 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?
>
>
> If we are assembling a wish-list, I've often wanted the opposite of an include. I want the ability to encapsulate the contents of pg_hba.conf directly into postgresql.conf. So instead of giving a filename to hba_file, optionally give a multi-lined string with some kind of here-doc like mechanism, or something like that.
>
> When I set up a forked dev environment and then eventually want to compare the diverged dev setup back to production, I often forget to compare the pg_hba.conf file.
So is this just to avoid having to diff 2 files instead of one?
On it's face, I'm not seeing the value of putting pg_hba.conf inside postgresql.conf... what am I missing?
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2014-02-16 20:56:54 | Re: HBA files w/include support? |
Previous Message | Tom Lane | 2014-02-16 20:41:17 | Draft release notes up for review |