Document that TRUNCATE ignores user-defined ON DELETE triggers.

diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index aa27890f47eb6f40ae2b7bd5ba0cb889d0a7fe64..158875903528c185f2e9f00b502baf9117176f93 100644 (file)
--- a/doc/src/sgml/ref/truncate.sgml
+++ b/doc/src/sgml/ref/truncate.sgml
@@ -1,5 +1,5 @@
 <!--
-$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.14 2003/09/19 21:04:19 tgl Exp $
+$Header: /cvsroot/pgsql/doc/src/sgml/ref/truncate.sgml,v 1.15 2003/09/19 21:06:39 tgl Exp $
 PostgreSQL documentation
 -->
 
@@ -58,6 +58,11 @@ TRUNCATE [ TABLE ] <replaceable class="PARAMETER">name</replaceable>
    to the table from other tables.  Checking validity in such cases would
    require table scans, and the whole point is not to do one.
   </para>
+
+  <para>
+   <command>TRUNCATE</> will not run any user-defined ON DELETE triggers
+   that might exist for the table.
+  </para>
  </refsect1>
 
  <refsect1>