Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit0f6d011

Browse files
committed
Fix permissions explanations in CREATE DATABASE and CREATE SCHEMA docs.
These reference pages still claimed that you have to be superuser to createa database or schema owned by a different role. That was true before 8.1,but it was changed in commitsaa11106 andf91370c to allow assignment of ownershipto any role you are a member of. However, at the time we were thinking ofthat primarily as a change to the ALTER OWNER rules, so the need to touchthese two CREATE ref pages got missed.
1 parentbec6e6c commit0f6d011

File tree

2 files changed

+13
-16
lines changed

2 files changed

+13
-16
lines changed

‎doc/src/sgml/ref/create_database.sgml‎

Lines changed: 5 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -46,14 +46,6 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
4646
See <xref linkend="SQL-CREATEUSER">.
4747
</para>
4848

49-
<para>
50-
Normally, the creator becomes the owner of the new database.
51-
Superusers can create databases owned by other users, by using the
52-
<literal>OWNER</> clause. They can even create databases owned by
53-
users with no special privileges. Non-superusers with <literal>CREATEDB</>
54-
privilege can only create databases owned by themselves.
55-
</para>
56-
5749
<para>
5850
By default, the new database will be created by cloning the standard
5951
system database <literal>template1</>. A different template can be
@@ -81,12 +73,14 @@ CREATE DATABASE <replaceable class="PARAMETER">name</replaceable>
8173
</listitem>
8274
</varlistentry>
8375
<varlistentry>
84-
<term><replaceable class="parameter">use_name</replaceable></term>
76+
<term><replaceable class="parameter">user_name</replaceable></term>
8577
<listitem>
8678
<para>
87-
The name of the database user who will own the new database,
79+
Therolename of the user who will own the new database,
8880
or <literal>DEFAULT</literal> to use the default (namely, the
89-
user executing the command).
81+
user executing the command). To create a database owned by another
82+
role, you must be a direct or indirect member of that role,
83+
or be a superuser.
9084
</para>
9185
</listitem>
9286
</varlistentry>

‎doc/src/sgml/ref/create_schema.sgml‎

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,8 @@ CREATE SCHEMA AUTHORIZATION <replaceable class="parameter">user_name</replaceabl
6565
<term><replaceable class="parameter">schema_name</replaceable></term>
6666
<listitem>
6767
<para>
68-
The name of a schema to be created. If this is omitted, the user name
68+
The name of a schema to be created. If this is omitted, the
69+
<replaceable class="parameter">user_name</replaceable>
6970
is used as the schema name. The name cannot
7071
begin with <literal>pg_</literal>, as such names
7172
are reserved for system schemas.
@@ -77,9 +78,10 @@ CREATE SCHEMA AUTHORIZATION <replaceable class="parameter">user_name</replaceabl
7778
<term><replaceable class="parameter">user_name</replaceable></term>
7879
<listitem>
7980
<para>
80-
The name of the user who will own the schema. If omitted,
81-
defaults to the user executing the command. Only superusers
82-
can create schemas owned by users other than themselves.
81+
The role name of the user who will own the new schema. If omitted,
82+
defaults to the user executing the command. To create a schema
83+
owned by another role, you must be a direct or indirect member of
84+
that role, or be a superuser.
8385
</para>
8486
</listitem>
8587
</varlistentry>
@@ -176,7 +178,8 @@ CREATE VIEW hollywood.winners AS
176178
all objects within it. <productname>PostgreSQL</productname>
177179
allows schemas to contain objects owned by users other than the
178180
schema owner. This can happen only if the schema owner grants the
179-
<literal>CREATE</> privilege on his schema to someone else.
181+
<literal>CREATE</> privilege on his schema to someone else, or a
182+
superuser chooses to create objects in it.
180183
</para>
181184
</refsect1>
182185

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp