From: Robert Haas <rhaas@postgresql.org>
Date: Wed, 10 May 2017 03:49:20 +0000 (-0400)
Subject: Document trigger-firing behavior for inheritance/partitioning.
X-Git-Tag: REL_10_BETA1~56
X-Git-Url: http://git.postgresql.org/gitweb/?a=commitdiff_plain;h=e17628145ac33bf271b3f575b52cdbe9dde0bb80;p=postgresql.git

Document trigger-firing behavior for inheritance/partitioning.

Amit Langote, reviewed Thomas Munro and by me.

Discussion: http://postgr.es/m/CA+Tgmoadpcs3=mMgdyqVX7L7L_PwO_Dn5j-98a6Tj7ByBuimUQ@mail.gmail.com
---

diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index 6f8416dda7e..ce76a1f0420 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -122,6 +122,14 @@
     identified as needing to be operated on.
    </para>
 
+   <para>
+    A statement that targets a parent table in a inheritance or partitioning
+    hierarchy does not cause the statement-level triggers of affected child
+    tables to be fired; only the parent table's statement-level triggers are
+    fired.  However, row-level triggers of any affected child tables will be
+    fired.
+   </para>
+
    <para>
     If an <command>INSERT</command> contains an <literal>ON CONFLICT
     DO UPDATE</> clause, it is possible that the effects of all