| From: | Gevik Babakhani <pgdev(at)xs4all(dot)nl> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| 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 15:12:18 |
| Message-ID: | 1145977938.31215.31.camel@voyager.truesoftware.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 2006-04-25 at 08:53 -0400, Alvaro Herrera wrote:
> Gevik Babakhani wrote:
> 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.)
This is no problem :) I will remove the cancellation part and change
the warning.
Could someone please provide a suitable warning message :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-25 15:17:14 | Re: TODO Item: ACL_CONNECT |
| Previous Message | Jim C. Nasby | 2006-04-25 15:09:10 | Re: Google SoC--Idea Request |