Add documentation:

>>>I think a more accurate description would be "permissions not
>>>inherited by children," and that isn't necessarily a bug.
>>
>>I agree it may not be a bug - but it's more than the permissions not
>>being inherited: the parent is affected.
>
>
> Not really, once you understand what's happening.  Unless you use
> FROM ONLY, selecting from the parent selects from the parent *and*
> its children.  The parent itself isn't affected, as queries with
> FROM ONLY should demonstrate.  I understand what you're saying --
> that there's an apparent effect on the parent -- but there really
> isn't.

Sean Burlington

diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml
index abe3b58201676df3beef25787d26b895f8088a93..f3a0129778e6d74552b940e667acec5932163ed3 100644 (file)
--- a/doc/src/sgml/ddl.sgml
+++ b/doc/src/sgml/ddl.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.43 2005/08/12 01:35:53 tgl Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.44 2005/08/13 01:55:41 momjian Exp $ -->
 
 <chapter id="ddl">
  <title>Data Definition</title>
@@ -1122,6 +1122,17 @@ SELECT name, altitude
    support this <quote>ONLY</quote> notation.
   </para>
 
+
+<note>
+  <title>Inheritance and Permissions</title>
+  <para>
+  Because permissions are not inherited automatically a user attempting to access
+  a parent table must either have at least the same permission for the child table
+  or must use the <quote>ONLY</quote> notation. If creating a new inheritance 
+  relationship in an existing system be careful that this does not create problems.
+  </para>
+</note>
+  
   <note>
    <title>Deprecated</title> 
    <para>