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 <kaigai(at)kaigai(dot)gr(dot)jp>