From 8421253e54237248a1aa0d30669d22509b5d7e4e Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Fri, 19 Sep 2003 21:06:39 +0000
Subject: [PATCH] Document that TRUNCATE ignores user-defined ON DELETE
triggers.
---
doc/src/sgml/ref/truncate.sgml | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/doc/src/sgml/ref/truncate.sgml b/doc/src/sgml/ref/truncate.sgml
index aa27890f47e..15887590352 100644
--- 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>
--
GitLab