Re: [COMMITTERS] pgsql: Handle policies during DROP OWNED BY

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [COMMITTERS] pgsql: Handle policies during DROP OWNED BY
Date: 2015-12-12 20:25:24
Message-ID: 566C82B4.5050000@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 12/11/15 4:12 PM, Stephen Frost wrote:
> As with ACLs, the DROP OWNED BY caller must have permission to modify
> the policy or a WARNING is thrown and no change is made to the policy.

That warning doesn't tell the user anything about how to fix the
situation or whether or why the situation is a problem and what to do
about it.

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Stephen Frost 2015-12-12 21:35:32 Re: [COMMITTERS] pgsql: Handle policies during DROP OWNED BY
Previous Message Peter Eisentraut 2015-12-12 16:32:41 pgsql: doc: Add some markup

Browse pgsql-hackers by date

  From Date Subject
Next Message Andreas Seltenreich 2015-12-12 20:30:17 Re: [sqlsmith] Failed to generate plan on lateral subqueries
Previous Message Peter Geoghegan 2015-12-12 19:50:00 Re: Should TIDs be typbyval = FLOAT8PASSBYVAL to speed up CREATE INDEX CONCURRENTLY?