Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 3acfe6b

Browse filesBrowse files
committed
Fix docs regarding AFTER triggers on partitioned tables
In commit 86f5759 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
1 parent 2d8a6fa commit 3acfe6b
Copy full SHA for 3acfe6b

File tree

Expand file treeCollapse file tree

1 file changed

+4
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+4
-2
lines changed

‎doc/src/sgml/trigger.sgml

Copy file name to clipboardExpand all lines: doc/src/sgml/trigger.sgml
+4-2Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -115,8 +115,10 @@
115115
<literal>BEFORE</literal> triggers fire immediately before a particular row is
116116
operated on, while row-level <literal>AFTER</literal> triggers fire at the end of
117117
the statement (but before any statement-level <literal>AFTER</literal> triggers).
118-
These types of triggers may only be defined on non-partitioned tables and
119-
foreign tables, not views. <literal>INSTEAD OF</literal> triggers may only be
118+
These types of triggers may only be defined on tables and
119+
foreign tables, not views; <literal>BEFORE</literal> row-level triggers may not
120+
be defined on partitioned tables.
121+
<literal>INSTEAD OF</literal> triggers may only be
120122
defined on views, and only at row level; they fire immediately as each
121123
row in the view is identified as needing to be operated on.
122124
</para>

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.