Skip to content
Snippets Groups Projects
Commit ab2d907a authored by Bruce Momjian's avatar Bruce Momjian
Browse files

doc: correct sepgsql doc about permission checking of CASCADE 

Backpatch to 9.2.

Patch from Kohei KaiGai
parent ecfd9941
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
doc/src/sgml/sepgsql.sgml
+ 1
− 1
View file @ ab2d907a
...@@ -443,7 +443,7 @@ UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100; ...@@ -443,7 +443,7 @@ UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100;
<para> <para>
When <literal>DROP</> command is executed, <literal>drop</> will be When <literal>DROP</> command is executed, <literal>drop</> will be
checked on the object being removed for each object types. Permissions checked on the object being removed for each object types. Permissions
will not be checked for objects dropped indirectly via <literal>CASCADE</>. will be also checked for objects dropped indirectly via <literal>CASCADE</>.
Deletion of objects contained within a particular schema (tables, views, Deletion of objects contained within a particular schema (tables, views,
sequences and procedures) additionally requires sequences and procedures) additionally requires
<literal>remove_name</> on the schema. <literal>remove_name</> on the schema.
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment