From 9652b79ae417cd10aa611b3cfdc9c8e6225555cc Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 20 Jul 2006 18:00:03 +0000
Subject: [PATCH] Update documentation on GRANT SCEMA USAGE, again.

---
 doc/src/sgml/ref/grant.sgml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/doc/src/sgml/ref/grant.sgml b/doc/src/sgml/ref/grant.sgml
index e7ca4d1ba9..9b1ed1aeba 100644
--- a/doc/src/sgml/ref/grant.sgml
+++ b/doc/src/sgml/ref/grant.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.58 2006/07/19 18:42:31 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/ref/grant.sgml,v 1.59 2006/07/20 18:00:03 momjian Exp $
 PostgreSQL documentation
 -->
 
@@ -276,8 +276,10 @@ GRANT <replaceable class="PARAMETER">role</replaceable> [, ...]
        schema (assuming that the objects' own privilege requirements are
        also met).  Essentially this allows the grantee to <quote>look up</>
        objects within the schema.  Without this permission, it is still
-       possible to see the object names, e.g. by querying the system tables,
-       so this is not a completely secure way to prevent object access.
+       possible to see the object names, e.g. by querying the system tables.
+       Also, after revoking this permission, existing backends might have
+       statements that have previously performed this lookup, so this is not
+       a completely secure way to prevent object access.
       </para>
       <para>
        For sequences, this privilege allows the use of the