From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Jerry Sievers <gsievers19(at)comcast(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: HBA files w/include support? |
Date: | 2014-02-15 20:15:01 |
Message-ID: | 20140215201501.GA21910@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Feb 14, 2014 at 11:10:48AM -0500, Tom Lane wrote:
> The argument about wanting to assemble a pg_hba file from separately
> managed configuration pieces seems to have some merit, but the weak
> spot there is how do you define the search order? Or are you planning
> to just cross your fingers and hope it doesn't matter too much?
Well, in my case since the only auth method used is md5 the order
really doesn't matter. Besides the point that each combination of
dbname and username only appears once.
But for a general use feature I can imagine it would be a concern.
This is not an important feature for me though: the config file is
generated by puppet with a bunch of loops and an include directory
would not really reduce the amount of work.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> He who writes carelessly confesses thereby at the very outset that he does
> not attach much importance to his own thoughts.
-- Arthur Schopenhauer
From | Date | Subject | |
---|---|---|---|
Next Message | Marco Atzeri | 2014-02-15 20:49:43 | Re: narwhal and PGDLLIMPORT |
Previous Message | Andres Freund | 2014-02-15 19:49:54 | Re: narwhal and PGDLLIMPORT |