Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TJbtj-0004ut-8q for pgsql-docs@postgreSQL.org; Thu, 04 Oct 2012 03:14:51 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TJbth-0001lC-Gz for pgsql-docs@postgreSQL.org; Thu, 04 Oct 2012 03:14:50 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.5/8.14.5) with ESMTP id q943EmP1014052 for ; Wed, 3 Oct 2012 23:14:48 -0400 (EDT) From: Tom Lane To: pgsql-docs@postgreSQL.org Subject: Docs issue for CREATE SCHEMA ... AUTHORIZATION permissions Date: Wed, 03 Oct 2012 23:14:48 -0400 Message-ID: <14051.1349320488@sss.pgh.pa.us> X-Pg-Spam-Score: -4.0 (----) X-Archive-Number: 201210/2 X-Sequence-Number: 7482 The CREATE SCHEMA reference page says "Only superusers can create schemas owned by users other than themselves". ISTM this is incorrect, or at least not the whole truth, because the test that is actually in the code is check_is_member_of_role(), that is whether the current user is allowed to SET ROLE to the target. In the SET ROLE reference page we say "The specified role_name must be a role that the current session user is a member of. (If the session user is a superuser, any role can be selected.)" Is that good wording to use in CREATE SCHEMA too, or would somebody like to wordsmith it? regards, tom lane