Given the amount of damage a person with write access to a table can get
into it seems pointless to not allow them to analyze the table after their
updates - since best practices would say that normal work with a table
should not be performed by an owner.

I should the check for whether a given user can or cannot analyze a table
should be whether the user has INSERT, UPDATE, or DELETE privileges.

I suppose row-level-security might come into play here...

David J.

Reply via email to