Tom Lane writes:
> Hmm. So the real story here is that the permissions set up by initdb
> for PUBLIC are actually an illegal state: postgres has granted
> permissions to public that it isn't allowed to.
Yes, the way the permissions are initialized in the catalog templates
DATA(insert OID = 11 (
Rod Taylor <[EMAIL PROTECTED]> writes:
>>> ERROR: dependent privileges exist (use CASCADE to revoke them too)
>>
>> I saw that a couple weeks ago, and then was unable to reproduce it later
> Seems to be by design. Create an empty schema with no permissions.
> First REVOKE sees lack of permission
On Sun, 2003-02-23 at 00:36, Tom Lane wrote:
> Rod Taylor <[EMAIL PROTECTED]> writes:
> > ERROR: dependent privileges exist (use CASCADE to revoke them too)
>
> I saw that a couple weeks ago, and then was unable to reproduce it later
> (and still can't today). I suspect there may be some kind of
Rod Taylor <[EMAIL PROTECTED]> writes:
> ERROR: dependent privileges exist (use CASCADE to revoke them too)
I saw that a couple weeks ago, and then was unable to reproduce it later
(and still can't today). I suspect there may be some kind of
uninitialized-variable bug, or something else with not
bash-2.05b$ ./psql newempty < file.txt
SET
You are now connected as new user rbt.
SET
REVOKE
GRANT
ERROR: dependent privileges exist (use CASCADE to revoke them too)
The above is from the result of loading the attached file (empty
database) into "newempty" which is a different empty database.
-
