mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-08-30 00:37:19 +02:00
Fix docs regarding AFTER triggers on partitioned tables
In commit 86f575948c
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
This commit is contained in:
parent
a8beece956
commit
902f40dc77
@ -115,8 +115,10 @@
|
|||||||
<literal>BEFORE</literal> triggers fire immediately before a particular row is
|
<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
|
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).
|
the statement (but before any statement-level <literal>AFTER</literal> triggers).
|
||||||
These types of triggers may only be defined on non-partitioned tables and
|
These types of triggers may only be defined on tables and
|
||||||
foreign tables, not views. <literal>INSTEAD OF</literal> triggers may only be
|
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
|
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.
|
row in the view is identified as needing to be operated on.
|
||||||
</para>
|
</para>
|
||||||
|
Loading…
Reference in New Issue
Block a user