I noticed a sentence in sepgsql says 180-degree opposite at: When <literal>DROP</> command is executed, <literal>drop</> will be checked on the object being removed for each object types. Permissions "will not be" checked for objects dropped indirectly via <literal>CASCADE</>.
This should be "will also be", as our implementation doing. I'm not sure why I described such a wrong stuff. Anyway, the attached patch will fix it. Thanks, -- KaiGai Kohei <kai...@kaigai.gr.jp>
pgsql-v9.2-sepgsql-document-fixup.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
