Improvement to CREATE TRIGGER and catalog documentation.

Neil Conway

diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml
index 5921f476b73dc9a736723964062ab9e76c7ab7e8..af8dee9f565f1b2a38904f89d8337f3f61e63e16 100644 (file)
--- a/doc/src/sgml/catalogs.sgml
+++ b/doc/src/sgml/catalogs.sgml
@@ -1,6 +1,6 @@
 
 
 
@@ -1068,9 +1068,12 @@
       relhasindex
       bool
       
-      True if this is a table and it has (or recently had) any indexes.
-       This is set by CREATE INDEX, but not cleared immediately by DROP INDEX.
-       VACUUM clears relhasindex if it finds the table has no indexes.
+      
+       True if this is a table and it has (or recently had) any
+       indexes. This is set by CREATE INDEX, but
+       not cleared immediately by DROP INDEX.
+       VACUUM clears relhasindex if it finds the
+       table has no indexes.
       
      
 
@@ -2049,11 +2052,11 @@
       bool
       
       
-       This is false for internal languages (such as SQL) and true for
-       user-defined languages.  Currently,
-       pg_dump still uses this to determine
-       which languages need to be dumped, but this may be replaced by
-       a different mechanism sometime.
+       This is false for internal languages (such as
+       SQL) and true for user-defined languages.
+       Currently, pg_dump still uses this
+       to determine which languages need to be dumped, but this may be
+       replaced by a different mechanism sometime.
       
      
 

diff --git a/doc/src/sgml/ref/create_trigger.sgml b/doc/src/sgml/ref/create_trigger.sgml
index ac8309af2e1da79263a4d86cce404bf3a743ae54..2917050b789774a45f2c383c9b408e98f985906f 100644 (file)
--- a/doc/src/sgml/ref/create_trigger.sgml
+++ b/doc/src/sgml/ref/create_trigger.sgml
@@ -1,5 +1,5 @@
 
 
@@ -21,9 +21,8 @@ PostgreSQL documentation
    2000-03-25
   
   
-CREATE TRIGGER name {
-    BEFORE | AFTER } { event [ OR ... ] }
-    ON table [ FOR EACH { ROW | STATEMENT } ]
+CREATE TRIGGER name { BEFORE | AFTER } { event [ OR ... ] }
+    ON table [ FOR [ EACH ] { ROW | STATEMENT } ]
     EXECUTE PROCEDURE func ( arguments )
   
   
@@ -186,7 +185,9 @@ CREATE TRIGGER
    deleted tuple. In contrast, a trigger that executes FOR
    EACH STATEMENT of the specified operation only executes
    once for any given operation, regardless of how many rows it
-   modifies.
+   modifies (in particular, an operation that modifies zero rows will
+   still result in the execution of any applicable FOR EACH
+   STATEMENT triggers).
   
 
   
@@ -330,6 +331,12 @@ CREATE TABLE distributors (
       time-of-creation order.  PostgreSQL
       uses name order, which was judged more convenient to work with.
      
+
+     
+      The ability to specify multiple actions for a single trigger
+      using OR is a PostgreSQL
+      extension of the SQL standard.
+