From 0d81bd9cc88ac417d3035600d2251452fd9dabaa Mon Sep 17 00:00:00 2001 From: Peter Geoghegan Date: Fri, 24 Apr 2015 18:40:36 -0700 Subject: [PATCH] Polish trigger documentation --- doc/src/sgml/trigger.sgml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/doc/src/sgml/trigger.sgml b/doc/src/sgml/trigger.sgml index 5141690877e9b..962c55b9bae97 100644 --- a/doc/src/sgml/trigger.sgml +++ b/doc/src/sgml/trigger.sgml @@ -138,17 +138,17 @@ idempotent). Note that statement-level UPDATE triggers are executed when ON CONFLICT UPDATE is specified, regardless of whether or not any rows were affected by - the UPDATE. An INSERT with - an ON CONFLICT UPDATE clause will execute - statement-level BEFORE INSERT - triggers first, then statement-level BEFORE - UPDATE triggers, followed by statement-level - AFTER UPDATE triggers and finally - statement-level AFTER INSERT - triggers. ON CONFLICT UPDATE is not supported on - views (Only ON CONFLICT IGNORE is supported on - updatable views); therefore, unpredictable interactions with - INSTEAD OF triggers are not possible. + the UPDATE (and regardless of whether the + alternative UPDATE path was ever taken). An + INSERT with an ON CONFLICT UPDATE + clause will execute statement-level BEFORE + INSERT triggers first, then statement-level + BEFORE UPDATE triggers, followed by + statement-level AFTER UPDATE + triggers and finally statement-level AFTER + INSERT triggers. ON CONFLICT + UPDATE is not supported on views (only ON CONFLICT + IGNORE is supported on updatable views).