Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: TODO Item: ACL_CONNECT


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • Cc: Gevik Babakhani <pgdev(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org
  • Subject: Re: TODO Item: ACL_CONNECT
  • Date: Tue, 25 Apr 2006 11:17:14 -0400
  • Message-id: <19391(dot)1145978234(at)sss(dot)pgh(dot)pa(dot)us>

Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> No other object type has the ability to require you to stop the server
> and start a standalone backend to fix the mistake, which is what makes
> this thing unique.

This one doesn't either.  I already pointed out two reasons why not:
1. you can connect to a different database (eg template1 or postgres)
and fix the problem from there.
2. the restriction won't be enforced against superusers anyway.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group