diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml
new file mode 100644
index 6e1f370..0615f8a
*** a/doc/src/sgml/trigger.sgml
--- b/doc/src/sgml/trigger.sgml
***************
*** 140,160 ****
! If an INSERT contains an ON CONFLICT
! DO UPDATE clause, it is possible that the effects of
! row-level BEFORE INSERT triggers and
! row-level BEFORE UPDATE triggers can
! both be applied in a way that is apparent from the final state of
! the updated row, if an EXCLUDED column is referenced.
! There need not be an EXCLUDED column reference for
! both sets of row-level BEFORE triggers to execute,
! though. The
! possibility of surprising outcomes should be considered when there
! are both BEFORE INSERT and
! BEFORE UPDATE row-level triggers
! that change a row being inserted/updated (this can be
! problematic even if the modifications are more or less equivalent, if
! they're not also idempotent). Note that statement-level
UPDATE triggers are executed when ON
CONFLICT DO UPDATE is specified, regardless of whether or not
any rows were affected by the UPDATE (and
--- 140,158 ----
! If an INSERT contains an ON
! CONFLICT DO UPDATE clause, it is possible for both
! row-level BEFORE INSERT and
! BEFORE UPDATE triggers to be
! executed on the same row. The possibility of surprising outcomes
! should be considered when they change rows being inserted/updated
! (this can be problematic even if the modifications are more or less
! equivalent, if they're not also idempotent). The modification of
! EXCLUDED columns has similar interactions.
!
!
!
! Note that statement-level
UPDATE triggers are executed when ON
CONFLICT DO UPDATE is specified, regardless of whether or not
any rows were affected by the UPDATE (and