MIME-Version: 1.0
In-Reply-To: <201110141511.p9EFBXq01907@momjian.us>
References: 
 <CA+TgmoaZtWR08UJfRY+3ps3=BBcDB7koXrmeAZPMkT0_Rm6Nnw@mail.gmail.com>
	<201110141511.p9EFBXq01907@momjian.us>
Date: Sat, 15 Oct 2011 06:29:14 -0400
Message-ID: 
 <CA+TgmoYTJgMpkeNV=QUr=rEL5z=fGpceTUy8Y11pPxNax9Q0yw@mail.gmail.com>
Subject: Re: DROP TABLE can be issued by schema owner as well as table owner
From: Robert Haas <robertmhaas@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Derrick Rice <derrick.rice@gmail.com>, pgsql-docs@postgresql.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 14, 2011 at 11:11 AM, Bruce Momjian <bruce@momjian.us> wrote:
> Robert Haas wrote:
>> On Thu, Oct 13, 2011 at 10:06 AM, Bruce Momjian <bruce@momjian.us> wrote=
:
>> > I applied the following documentation patch to clarify this issue, and
>> > used generic wording "user with the proper permissions".
>>
>> That doesn't seem like an improvement; what permissions are proper?
>
> No idea, but it hints that other users can do it too. =A0I thought too
> specific was too complex for this case.

I disagree.  I think it's the purpose of documentation to be specific.
 The code says:

        /* Allow DROP to either table owner or schema owner */
        if (!pg_class_ownercheck(relOid, GetUserId()) &&
            !pg_namespace_ownercheck(classform->relnamespace, GetUserId()))
            aclcheck_error(ACLCHECK_NOT_OWNER, ACL_KIND_CLASS,
                           rel->relname);

So the command can be executed by the owner of the table, the owner of
the containing schema, or the superuser.

That seems simple enough.

--=20
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company