postgres.git / summary / log / commit / refs

commit    902f40dc774b00fe906aca594df42278d832681d
Author:   Alvaro Herrera <alvherre@alvh.no-ip.org>
Date:     Wed Feb 26 22:57:14 2020 +0000
First released in: 13.0, 11.8, 12.3

    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


 doc/src/sgml/trigger.sgml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

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>


[parent: a8beece956eb]