diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index d6e2905a49b..fb074c2983f 100644
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/src/sgml/ref/create_trigger.sgml
@@ -1,5 +1,5 @@
@@ -117,20 +117,22 @@ CREATE
- The trigger can be specified to fire either before BEFORE the
- operation is attempted on a tuple (before constraints
- are checked and the INSERT, UPDATE or
- DELETE is attempted) or
- AFTER the operation has been attempted (e.g., after constraints
- are checked and the INSERT,
- UPDATE or DELETE has
- completed). If the
- trigger fires before the event, the trigger may
- skip the operation for the current tuple, or change the tuple
- being inserted (for INSERT and
- UPDATE operations only). If
- the trigger fires after the event, all changes, including the
- last insertion, update, or deletion, are visible
to the trigger.
+ The trigger can be specified to fire either before BEFORE the
+ operation is attempted on a tuple (before constraints are checked and
+ the INSERT, UPDATE or
+ DELETE is attempted) or AFTER the operation has
+ been attempted (e.g., after constraints are checked and the
+ INSERT, UPDATE or
+ DELETE has completed). If the trigger fires before
+ the event, the trigger may skip the operation for the current tuple,
+ or change the tuple being inserted (for INSERT and
+ UPDATE operations only). If the trigger fires
+ after the event, all changes, including the last insertion, update,
+ or deletion, are visible
to the trigger.
+
+
+ SELECT does not modify any rows so you can not
+ create SELECT triggers.