diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-06-09 15:26:40 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-06-09 15:26:40 -0400 |
| commit | f3839ea117fba6fdb69c75a1fe145aa86a4c8ae3 (patch) | |
| tree | a9f477f972f6897d5b1fef01a1c4eaa1b93fd29e /doc/src | |
| parent | 007556bf08e6153c442fe3742adb3685fca3a0e0 (diff) | |
| download | postgresql-f3839ea117fba6fdb69c75a1fe145aa86a4c8ae3.tar.gz postgresql-f3839ea117fba6fdb69c75a1fe145aa86a4c8ae3.zip | |
Remove ALTER DEFAULT PRIVILEGES' requirement of schema CREATE permissions.
Per discussion, this restriction isn't needed for any real security reason,
and it seems to confuse people more often than it helps them. It could
also result in some database states being unrestorable. So just drop it.
Back-patch to 9.0, where ALTER DEFAULT PRIVILEGES was introduced.
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/ref/alter_default_privileges.sgml | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/sgml/ref/alter_default_privileges.sgml b/doc/src/sgml/ref/alter_default_privileges.sgml index b5c8bb3a36b..fdd9c83800e 100644 --- a/doc/src/sgml/ref/alter_default_privileges.sgml +++ b/doc/src/sgml/ref/alter_default_privileges.sgml @@ -121,8 +121,8 @@ REVOKE [ GRANT OPTION FOR ] <term><replaceable>schema_name</replaceable></term> <listitem> <para> - The name of an existing schema. Each <replaceable>target_role</> - must have <literal>CREATE</> privileges for each specified schema. + The name of an existing schema. If specified, the default privileges + are altered for objects later created in that schema. If <literal>IN SCHEMA</> is omitted, the global default privileges are altered. </para> |