public
schema or dropping a role that still owns objects is not allowed:
s1
can drop it:
s1
requires the CREATE privilege on that schema:
USAGE
privilege on schema s1
SELECT
privilege on table s1.t1
s1
but not the table s1.t1
and lacks SELECT
privilege on s1.t1
, the operation is forbidden.
Similarly, the operation will be forbidden if owning the table s1.t1
without USAGE
privilege on schema s1
.
CONNECT
privilege was revoked after connecting.