| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix permissions explanations in CREATE DATABASE and CREATE SCHEM |
| Date: | 2012-10-04 17:41:42 |
| Message-ID: | E1TJpQc-0000kP-F1@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
Branch
------
REL9_2_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/cb4083dfbbda97eb2b23111a3093c417d8a7d41a
Modified Files
--------------
doc/src/sgml/ref/create_database.sgml | 14 ++++----------
doc/src/sgml/ref/create_schema.sgml | 13 ++++++++-----
2 files changed, 12 insertions(+), 15 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-10-04 21:15:48 | pgsql: Fix parse location tracking for lists that can be empty. |
| Previous Message | Heikki Linnakangas | 2012-10-04 07:36:43 | pgsql: Fix typo in comment, and reword it slightly while we're at it. |