| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "Arcadius A(dot)" <ahouans(at)sh(dot)cvut(dot)cz>, pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: Why pg_hba.conf ? |
| Date: | 2003-07-19 18:10:07 |
| Message-ID: | 200307191110.07176.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
Arcadius,
> But the annoying thing is that, to allow connection for a new host/user, I
> have to manually edit the "pg_hba.conf" file.
> Wouldn't it be better/easier if the information about users/host are kept
> in a PostgreSQL DB instead?
And then what would you do if you accidentally locked yourself out of the
database? How would you connect in order to change the permissions?
> BTW: Perhaps,it's one of the reasons why most control panels for web
> hosting companies support MySQL only and just ignore PostgreSQL?
No, it's because MySQL requires less DBA knowledge to set up, and is targeted
specifcially at web developers, including ignoring many portions of the
SQL92/99 standard that web developers find onerous.
--
Josh Berkus
Aglio Database Solutions
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-07-20 01:20:17 | Re: Advocacy TODO |
| Previous Message | Arcadius A. | 2003-07-19 15:58:56 | Why pg_hba.conf ? |