Remove no-longer-appropriate notes about lack of CASCADE/RESTRICT behavior.

doc/src/sgml/ref/drop_domain.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_domain.sgml,v 1.7 2002/07/12 18:43:13 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_domain.sgml,v 1.8 2002/07/14 22:47:56 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -117,20 +117,6 @@ ERROR:  RemoveDomain: type '<replaceable class="parameter">domainname</replaceab
   </para>
  </refsect1>
 
- <refsect1 id="SQL-DROPDOMAIN-notes">
-  <title>Notes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     It is the user's responsibility to remove any operators,
-     functions, aggregates, access methods, and tables that
-     use a deleted domain.
-    </para>
-   </listitem>
-  </itemizedlist>
- </refsect1>
-
  <refsect1 id="SQL-DROPDOMAIN-examples">
   <title>Examples</title>
   <para>

doc/src/sgml/ref/drop_function.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.21 2002/07/12 18:43:13 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_function.sgml,v 1.22 2002/07/14 22:47:56 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -131,11 +131,6 @@ WARNING:  RemoveFunction: Function "<replaceable class="parameter">name</replace
     <xref linkend="sql-createfunction">
     for information on creating functions.
    </para>
-
-   <para>
-    No checks are made to ensure that types, operators, access
-    methods, or triggers that rely on the function have been removed first.
-   </para>
  </refsect1>
 
  <refsect1 id="SQL-DROPFUNCTION-examples">

doc/src/sgml/ref/drop_table.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.16 2002/07/12 18:43:13 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_table.sgml,v 1.17 2002/07/14 22:47:56 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -111,13 +111,11 @@ ERROR: table "<replaceable class="parameter">name</replaceable>" does not exist
    destroyed, by using <command>DELETE</command>.
   </para>
   <para>
-   If a table being destroyed has secondary indexes on it,
-   they will be removed first. The removal of just a
-   secondary index will not affect the contents of the underlying table.
-  </para>
-  <para>
-   <command>DROP TABLE</command> will also remove any rules or triggers
-   that exist for the target table.
+   <command>DROP TABLE</command> always removes any indexes, rules,
+   triggers, and constraints that exist for the target table.  However,
+   to drop a table that is referenced by a foreign-key constraint of another
+   table, CASCADE must be specified. (CASCADE will remove the foreign-key
+   constraint, not the other table itself.)
   </para>
 
   <refsect2 id="R2-SQL-DROPTABLE-3">

doc/src/sgml/ref/drop_type.sgml

 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.18 2002/07/12 18:43:13 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/drop_type.sgml,v 1.19 2002/07/14 22:47:56 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -114,29 +114,6 @@ ERROR:  RemoveType: type '<replaceable class="parameter">typename</replaceable>'
    Only the owner of a type can remove it.
   </para>
  </refsect1>
-
- <refsect1 id="SQL-DROPTYPE-notes">
-  <title>Notes</title>
-
-  <itemizedlist>
-   <listitem>
-    <para>
-     It is the user's responsibility to remove any operators,
-     functions, aggregates, access methods, subtypes, and tables that
-     use a deleted type.  However, the associated array data type
-     (which was automatically created by <command>CREATE TYPE</command>)
-     will be removed automatically.
-    </para>
-   </listitem>
-
-   <listitem>
-    <para>
-     If a built-in type is removed, the behavior of the server is
-     unpredictable.
-    </para>
-   </listitem>
-  </itemizedlist>
- </refsect1>
   
  <refsect1 id="SQL-DROPTYPE-examples">
   <title>Examples</title>