Re: Clarity Bug for Schema Permissions, Potential Vulnerability? - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: Clarity Bug for Schema Permissions, Potential Vulnerability?
Date
Msg-id CAKFQuwbkD5eStnCSsZZiRWZoWBviWG5x-0jz6L-ZmBg2T6tmjw@mail.gmail.com
Whole thread Raw
In response to Re: Clarity Bug for Schema Permissions, Potential Vulnerability?  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-bugs
On Wed, May 6, 2020 at 6:38 AM Jeff Janes <jeff.janes@gmail.com> wrote:
I think a more useful change (if any) would be a NOTICE or WARNING when granting privs on a object in a schema, to a user who does not already have privs on the schema itself.

Definitely not a warning but maybe a notice.  But if that's the extent of things I don't really see enough value to warrant having a command targeting one object go looking around the system for other related state to comment upon.  If one revokes usage on a schema should we inform the user of any remaining grants on contained objects?  I suspect there are other useful notices to consider beyond those two.  It feels like something better left to a third-party tool rather than something built into core.

David J.

pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Clarity Bug for Schema Permissions, Potential Vulnerability?
Next
From: PG Bug reporting form
Date:
Subject: BUG #16419: wrong parsing BC year in to_date() function