From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Date: Wed, 26 Feb 2020 22:57:14 +0000 (-0300)
Subject: Fix docs regarding AFTER triggers on partitioned tables
X-Git-Tag: REL_13_BETA1~660
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=3acfe6b089a5283c2961eb2ff135106e23b89263;p=thirdparty%2Fpostgresql.git

Fix docs regarding AFTER triggers on partitioned tables

In commit 86f575948c77 I forgot to update the trigger.sgml paragraph
that needs to explain that AFTER triggers are allowed in partitioned
tables.  Do so now.

Discussion: https://postgr.es/m/20200224185850.GA30899@alvherre.pgsql
---

diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index ba94acad696..6f323a903b5 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -115,8 +115,10 @@
     <literal>BEFORE</literal> triggers fire immediately before a particular row is
     operated on, while row-level <literal>AFTER</literal> triggers fire at the end of
     the statement (but before any statement-level <literal>AFTER</literal> triggers).
-    These types of triggers may only be defined on non-partitioned tables and
-    foreign tables, not views.  <literal>INSTEAD OF</literal> triggers may only be
+    These types of triggers may only be defined on tables and
+    foreign tables, not views; <literal>BEFORE</literal> row-level triggers may not
+    be defined on partitioned tables.
+    <literal>INSTEAD OF</literal> triggers may only be
     defined on views, and only at row level; they fire immediately as each
     row in the view is identified as needing to be operated on.
    </para>