Update documentation about pseudo-types.

Tone down an overly strong statement about which pseudo-types PLs are
likely to allow.  Add "event_trigger" to the list, as well as
"pg_ddl_command" in 9.5/HEAD.  Back-patch to 9.3 where event_trigger
was added.

diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 87f424e076fb4fdde711d0c57b4ae0f832b60357..2b043b0d6388c825ee342e8cf62825d657fa4048 100644 (file)
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -4561,6 +4561,10 @@ SELECT * FROM pg_attribute
     trigger
    
 
+   
+    event_trigger
+   
+
    
     language_handler
    
@@ -4665,7 +4669,7 @@ SELECT * FROM pg_attribute
 
        
         record
-        Identifies a function returning an unspecified row type.
+        Identifies a function taking or returning an unspecified row type.
        
 
        
@@ -4673,6 +4677,11 @@ SELECT * FROM pg_attribute
         A trigger function is declared to return trigger.
        
 
+       
+        event_trigger
+        An event trigger function is declared to return event_trigger.
+       
+
        
         void
         Indicates that a function returns no value.
@@ -4695,10 +4704,11 @@ SELECT * FROM pg_attribute
 
    
     Functions coded in procedural languages can use pseudo-types only as
-    allowed by their implementation languages.  At present the procedural
-    languages all forbid use of a pseudo-type as argument type, and allow
+    allowed by their implementation languages.  At present most procedural
+    languages forbid use of a pseudo-type as an argument type, and allow
     only void and record as a result type (plus
-    trigger when the function is used as a trigger).  Some also
+    trigger or event_trigger when the function is used
+    as a trigger or event trigger).  Some also
     support polymorphic functions using the types anyelement,
     anyarray, anynonarray, anyenum, and
     anyrange.