From: | Brian Hurt <bhurt(at)janestcapital(dot)com> |
---|---|
To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
Cc: | pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: drupal.org MySQL database issues |
Date: | 2007-05-18 14:40:50 |
Message-ID: | 464DBAF2.8080002@janestcapital.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
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..)
>
>
> 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.
There are two advantages to having pg_hba.conf a file and not a table:
1) It allows me to configure access permissions *before* bringing up the
database, and
2) If I screw up and forget the postgres password, I can set local host
to "trust", log in, and change it.
Brian
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2007-05-18 14:51:23 | Re: drupal.org MySQL database issues |
Previous Message | Dave Page | 2007-05-18 14:34:13 | Re: drupal.org MySQL database issues |