| From: | Agent M <agentm(at)themactionfaction(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: control pg_hba.conf via SQL |
| Date: | 2006-04-01 18:14:57 |
| Message-ID: | 5559f4a765951fcbed3fc23756b6618c@themactionfaction.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
But there is still no way to verify that the information in the file is
what postgres saw last. DBAs make mistakes too. A simple way to view
the current access state would be much appreciated.
On Apr 1, 2006, at 1:01 PM, Andrew Dunstan wrote:
>
> Er, how can the file be changed behind the scenes? Only if you have
> opened up permission to the directory to someone else, or you don't
> trust your sysadmins.
>
> Either way you would then have much bigger problems than this.
>
> cheers
>
> andrew
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
AgentM
agentm(at)themactionfaction(dot)com
¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬ ¬
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Volkan YAZICI | 2006-04-01 18:39:44 | libpq Describe Extension [WAS: Bytea and perl] |
| Previous Message | Andrew Dunstan | 2006-04-01 18:01:23 | Re: control pg_hba.conf via SQL |