From: | "Arcadius A(dot)" <ahouans(at)sh(dot)cvut(dot)cz_!!!NOSPAM!!!> |
---|---|
To: | pgsql-advocacy(at)postgresql(dot)org |
Subject: | Re: pg_hba |
Date: | 2003-10-17 08:46:58 |
Message-ID: | bmoaa0$30dh$1@news.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy |
Christopher Browne wrote:
> "Arcadius A." <ahouans(at)sh(dot)cvut(dot)cz_!!!NOSPAM!!!> writes:
>
>>Once, I've asked about the pg_hb.conf file ....
>>IMHO, writing an app for parsing/editing that file *may* be a problem
>>for those who develop control panels used by web hosting companies ....
>>
>>IMHO, moving the info in pg_hb.conf into the DB itself may attract
>>control panel developers.
>
>
> ... Then create a table, along with a trigger/procedure that can dump
> the contents out to pg_hba.conf, and initiate a "kill -HUP".
>
> Shouldn't be /too/ terribly difficult to implement.
>
> And that would indeed be somewhat useful.
Christopher, thanks for the input :-)
But when you have 100+ user accounts in the RDBMS, is It secure to be
dumping a DB to a text file?(remember, system can fail while data is
being written to the text file .... )
And do not forget that there is a defined order for the rules in the
pg_hba.conf file, so,it's not obvious to just dump a DB into it...
BTW: assuming that your trigger/procedure works well without corrupting
pg_hba.conf, then what's the point of keeping the pg_hba.conf file and
duplicating data since all the info are already available in the RDBMS?
Regards.
Arcadius.
From | Date | Subject | |
---|---|---|---|
Next Message | Arcadius A. | 2003-10-17 10:23:02 | Re: MySQL interview, no mention of PostgreSQL |
Previous Message | Jean-Michel POURE | 2003-10-17 08:10:26 | Mapping Oracle types to PostgreSQL types |