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