| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: TODO Item: ACL_CONNECT |
| Date: | 2006-04-25 12:53:15 |
| Message-ID: | 20060425125315.GE24421@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Gevik Babakhani wrote:
> Hi
>
> On Mon, 2006-04-24 at 23:07 -0400, Alvaro Herrera wrote:
> > Gevik Babakhani wrote:
> >
> > > If one is going to revoke the last ACL_CONNECT, a warning is going to
> > > issued then that part of the REVOKE gets canceled.
> >
> > Humm, no, the WARNING is issued but the REVOKE is executed anyway.
>
> I have tested this by applying the patch-0.4.diff of a new src tree.
My point is that the behavior you describe is broken. The warning
should be issued but the command should be executed anyway. That way
the user executing it knows that he has locked everyone out of the
database (but he can lock everyone out of the database if he wants to.)
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2006-04-25 12:57:31 | Re: TODO Item: ACL_CONNECT |
| Previous Message | Alvaro Herrera | 2006-04-25 12:51:08 | Re: TODO Item: ACL_CONNECT |