From: | Chris Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: About pg_hba.conf |
Date: | 2006-04-06 14:37:47 |
Message-ID: | 60bqven51g.fsf@dba2.int.libertyrms.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
gevik(at)xs4all(dot)nl ("Gevik Babakhani") writes:
> This may be a dumb question but please bear a moment with me. About
> the TODO item %Allow pg_hba.conf settings to be controlled via
> SQL: If in the future we could configure the settings by SQL
> commands, assuming the settings are saved in an internal table, what
> would be the need for a pg_hba.conf file anymore. (except for the
> backward compatibility of cource)
It's a frequently asked question...
The trouble is, what if you accidentally lock all of the users out?
How do you fix that, if nobody can connect to submit SQL commands?
--
(reverse (concatenate 'string "moc.enworbbc" "@" "enworbbc"))
http://www.ntlug.org/~cbbrowne/lsf.html
"Ahhh. A man with a sharp wit. Someone ought to take it away from him
before he cuts himself." -- Peter da Silva
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-04-06 14:41:15 | Re: Support Parallel Query Execution in Executor |
Previous Message | Tino Wildenhain | 2006-04-06 14:33:54 | Re: About pg_hba.conf |