Robert Treat wrote:
> On Thursday 17 May 2007 17:54, Joshua D. Drake wrote:
>> Magnus Hagander wrote:
>>> Gavin M. Roy wrote:
>>>> I think for one, mysql uses tables for all of its access control.
>>>> Coding plesk/cpanel to modify pg_hba.conf and rehup postgres would take
>>>> a bit more work, I would imagine.
>>> In a lot of environments, it'd certainly be impossible, at least until
>>> we make it possible to edit the config files remote... (oops, recap of
>>> endless amounts of discussions on letting pgadmin do that..)
>
> Really this is already pretty doable at this point if your willing to be
> intrusive about things (which I think the plesk people probably are).
>
>> Well more to the point. There really is zero reason why we can't have a
>> table representation of pg_hba_conf that is the pg_hba.conf file that
>> has triggers that right out the file.
>>
>
> It's not quite that simple, since tables are conceptually unordered, but the
> pg_hba uses order to make it work, but this could probably be worked out if
> you could get people to agree that user management in the db was acceptable.
You just have a sort order within the table that the function that
writes out the file understands.
> Personally if you're just going to stick with a system tied to the
> pg_hba.conf, I don't think this step is really needed.
>
True enough.
>> I am however advocating that it is pretty dumb that our conf files are
>> *required* as a little text file on the filesystem and can not be
>> managed via the database.
>>
>
> agreed.
>
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/