From 731dfc7d5f07fac2c3c72f47c29a947e363acee9 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Mon, 28 Dec 2015 11:04:42 -0500 Subject: [PATCH] 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. --- doc/src/sgml/datatype.sgml | 27 +++++++++++++++++++++++---- 1 file changed, 23 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml index b5191f4536..d1db0d26a2 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -4616,6 +4616,14 @@ SELECT * FROM pg_attribute trigger + + event_trigger + + + + pg_ddl_command + + language_handler @@ -4729,7 +4737,7 @@ SELECT * FROM pg_attribute record - Identifies a function returning an unspecified row type. + Identifies a function taking or returning an unspecified row type. @@ -4737,6 +4745,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. @@ -4759,10 +4777,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. -- 2.40.0