=?iso-8859-1?Q?Fran=E7ois_Beausoleil?= <franc...@teksol.info> writes:
> Le 2013-06-06 à 17:59, Tom Lane a écrit :
>> Note where the fine manual says:
>>
>> schema_name
>> The name of an existing schema. Each target_role must have CREATE privileges
>> for each specified schema.
>>
>> There was some debate previously about whether that restriction was a
>> good idea at all; and given this example, it seems like we definitely
>> shouldn't require it during a REVOKE.
> I may not have read that section carefully enough. I'll try again, by adding
> postgres back with create privileges on the public schema.
FYI, after some further discussion on pgsql-hackers we've decided to
drop this permission check altogether. Future PG releases won't behave
this way, so there won't be any ordering dependency between doing ALTER
DEFAULT PRIVILEGES and doing GRANT/REVOKE CREATE ON SCHEMA.
regards, tom lane
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
