<br /><br /> Peter Eisentraut wrote:<br /><blockquote
cite="midPine.LNX.4.44.0302131909260.2646-100000@peter.localdomain"type="cite"><pre wrap="">mlw writes:
</pre><blockquote type="cite"><pre wrap="">AFAIK it wasn't actually done. It was more of a, "we should do something
different" argument. At one point it was talked about rewriting the
configuration system to allow "include" and other things. </pre></blockquote><pre wrap="">
The core of the problem was, and continues to be, this: If you move
postgresql.conf somewhere else, then someone else will also want to move
pg_hba.conf and all the rest. And that opens up a number of security and
cumbersome-to-install problems.
Just having an option that says, the configuration file is "there", is a
first step but not a complete solution.</pre></blockquote> The location of pg_hba.conf and pg_ident.conf can be
specifiedwithin the postgresql.conf file if desired.<br /><br /> I don't understand the security concerns, what
securityissues can there be?<br /><br /><blockquote cite="midPine.LNX.4.44.0302131909260.2646-100000@peter.localdomain"
type="cite"><prewrap=""> </pre></blockquote>
