Re: BUG #14131: BUG, schema owner can drop otheruser's object in it's schema

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: 德哥 <digoal(at)126(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #14131: BUG, schema owner can drop otheruser's object in it's schema
Date: 2016-05-10 14:18:46
Message-ID: CAKFQuwaYKC8Kn--A2Hq2PA78XwBhfqd90TQ9qkrCLwu6uUc_kA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, May 10, 2016 at 6:12 AM, <digoal(at)126(dot)com> wrote:

> The following bug has been logged on the website:
>
> Bug reference: 14131
> Logged by: digoal
> Email address: digoal(at)126(dot)com
> PostgreSQL version: 9.5.2
> Operating system: CentOS 6.x x64
> Description:
>
> According to the SQL standard, the owner of a schema always owns all
> objects
> within it. PostgreSQL allows schemas to contain objects owned by users
> other
> than the schema owner. This can happen only if the schema owner grants the
> CREATE privilege on his schema to someone else, or a superuser chooses to
> create objects in it.
>

Yeah, PostgreSQL provides for more flexability - standard conformance is up
to the DBA to enforce. Its not a bug to deviate from the standard - and
while there is some downside to be more flexible this particular dynamic
doesn't even seem that egregious compared to other areas where we deviate.

​David J.​

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message 德哥 2016-05-10 15:44:54 Re: BUG #14131: BUG, schema owner can drop otheruser's object in it's schema
Previous Message Tom Lane 2016-05-10 13:59:13 Re: BUG #14131: BUG, schema owner can drop otheruser's object in it's schema