diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2012-10-04 13:41:12 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2012-10-04 13:41:12 -0400 |
| commit | 0f6d0119f2b3e0957c67e6cb5ec84e669718bd27 (patch) | |
| tree | dcdd42fe44fbea2158a1e70c23381fa7079fd434 /doc/src/sgml/ref/create_schema.sgml | |
| parent | bec6e6cdfaa8987e82c328bf72cdc30d517e09f1 (diff) | |
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to create
a database or schema owned by a different role. That was true before 8.1,
but it was changed in commits aa1110624c08298393dfce996f7b21809d98d3fd and
f91370cd2faf1fd35a1ac74d84652a85ed841919 to allow assignment of ownership
to any role you are a member of. However, at the time we were thinking of
that primarily as a change to the ALTER OWNER rules, so the need to touch
these two CREATE ref pages got missed.
Diffstat (limited to 'doc/src/sgml/ref/create_schema.sgml')
| -rw-r--r-- | doc/src/sgml/ref/create_schema.sgml | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/doc/src/sgml/ref/create_schema.sgml b/doc/src/sgml/ref/create_schema.sgml index 0df736877f7..2cdf705328c 100644 --- a/doc/src/sgml/ref/create_schema.sgml +++ b/doc/src/sgml/ref/create_schema.sgml @@ -65,7 +65,8 @@ CREATE SCHEMA AUTHORIZATION <replaceable class="parameter">user_name</replaceabl <term><replaceable class="parameter">schema_name</replaceable></term> <listitem> <para> - The name of a schema to be created. If this is omitted, the user name + The name of a schema to be created. If this is omitted, the + <replaceable class="parameter">user_name</replaceable> is used as the schema name. The name cannot begin with <literal>pg_</literal>, as such names are reserved for system schemas. @@ -77,9 +78,10 @@ CREATE SCHEMA AUTHORIZATION <replaceable class="parameter">user_name</replaceabl <term><replaceable class="parameter">user_name</replaceable></term> <listitem> <para> - The name of the user who will own the schema. If omitted, - defaults to the user executing the command. Only superusers - can create schemas owned by users other than themselves. + The role name of the user who will own the new schema. If omitted, + defaults to the user executing the command. To create a schema + owned by another role, you must be a direct or indirect member of + that role, or be a superuser. </para> </listitem> </varlistentry> @@ -176,7 +178,8 @@ CREATE VIEW hollywood.winners AS all objects within it. <productname>PostgreSQL</productname> allows schemas to contain objects owned by users other than the schema owner. This can happen only if the schema owner grants the - <literal>CREATE</> privilege on his schema to someone else. + <literal>CREATE</> privilege on his schema to someone else, or a + superuser chooses to create objects in it. </para> </refsect1> |