summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2019-11-12 22:04:31 -0500
committerBruce Momjian <bruce@momjian.us>2019-11-12 22:04:31 -0500
commit5f2cfe7f5fbd90f0d6ffef26c90808f4bd3e1d51 (patch)
tree921d49542f595fdb898057a91fd75393e06181df
parent578a551f82f7ad746b36d98c401bdc92c136d664 (diff)
docs: clarify that only INSERT and UPDATE triggers can mod. NEW
The point is that DELETE triggers cannot modify any values. Reported-by: Eugen Konkov, Liudmila Mantrova Discussion: https://postgr.es/m/919823407.20191029175436@yandex.ru Backpatch-through: 12 only, where commit as missing
-rw-r--r--doc/src/sgml/trigger.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
index 67e1861e061..f62f420c192 100644
--- a/doc/src/sgml/trigger.sgml
+++ b/doc/src/sgml/trigger.sgml
@@ -230,7 +230,7 @@
used to signal that the trigger performed the necessary data
modifications in the view. This will cause the count of the number
of rows affected by the command to be incremented. For
- <command>INSERT</command> and <command>UPDATE</command> operations, the trigger
+ <command>INSERT</command> and <command>UPDATE</command> operations only, the trigger
may modify the <varname>NEW</varname> row before returning it. This will
change the data returned by
<command>INSERT RETURNING</command> or <command>UPDATE RETURNING</command>,