Improve docs on updatable views

Introduce the options before going into details, and add a link to the
CREATE TRIGGER documentation.

Author: David Johnston
Reviewed-By: Anastasia Lubennikova
Discussion: https://postgr.es/m/CAKFQuwYLLRhheo0_Y4Jp=vJ_YDsz1KoRuTpX1A_bUxmHTmLe-A@mail.gmail.com

diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml
index aa172d102b6f8dc7141d07622d866d71040bd321..b017d3122e39e141b446aca797415213dda80619 100644 (file)
--- a/doc/src/sgml/rules.sgml
+++ b/doc/src/sgml/rules.sgml
@@ -797,6 +797,10 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a;
     relation points at a subquery range-table entry, which will not
     work.  There are several ways in which PostgreSQL
     can support the appearance of updating a view, however.
+    In order of user-experienced complexity those are: automatically substitute
+    in the underlying table for the view, execute a user-defined trigger,
+    or rewrite the query per a user-defined rule.
+    These options are discussed below.
 
 
 
@@ -812,7 +816,8 @@ SELECT t1.a, t2.b, t1.ctid FROM t1, t2 WHERE t1.a = t2.a;
 
 
     Alternatively, the operation may be handled by a user-provided
-    INSTEAD OF trigger on the view.
+    INSTEAD OF trigger on the view
+    (see ).
     Rewriting works slightly differently
     in this case.  For INSERT, the rewriter does
     nothing at all with the view, leaving it as the result relation