diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 6e7717dfb3..61b562da97 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -4591,6 +4591,14 @@ SELECT * FROM pg_attribute
trigger
+
+ event_trigger
+
+
+
+ pg_ddl_command
+
+
language_handler
@@ -4704,7 +4712,7 @@ SELECT * FROM pg_attribute
record>
- Identifies a function returning an unspecified row type.
+ Identifies a function taking or returning an unspecified row type.
@@ -4712,6 +4720,16 @@ SELECT * FROM pg_attribute
A trigger function is declared to return trigger.>
+
+ event_trigger>
+ An event trigger function is declared to return event_trigger.>
+
+
+
+ pg_ddl_command>
+ Identifies a represention of DDL commands that is available to event triggers.
+
+
void>
Indicates that a function returns no value.
@@ -4734,10 +4752,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>.