From ab2d907a25e8c59326dc4d4194578e95eeceae89 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 24 Jan 2013 21:21:50 -0500
Subject: [PATCH] doc: correct sepgsql doc about permission checking of
CASCADE
Backpatch to 9.2.
Patch from Kohei KaiGai
---
doc/src/sgml/sepgsql.sgml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml
index ff083a06596..27bc2e62190 100644
--- a/doc/src/sgml/sepgsql.sgml
+++ b/doc/src/sgml/sepgsql.sgml
@@ -443,7 +443,7 @@ UPDATE t1 SET x = 2, y = md5sum(y) WHERE z = 100;
<para>
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</>.
+ will be also checked for objects dropped indirectly via <literal>CASCADE</>.
Deletion of objects contained within a particular schema (tables, views,
sequences and procedures) additionally requires
<literal>remove_name</> on the schema.
--
GitLab