From: Tom Lane Date: Mon, 28 Dec 2015 16:04:42 +0000 (-0500) Subject: Update documentation about pseudo-types. X-Git-Tag: REL9_3_11~35 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e12c74401bf3ad1fbeaa41a435c16227b602fb86;p=postgresql 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 10e668a85d..151a49037e 100644 --- a/doc/src/sgml/datatype.sgml +++ b/doc/src/sgml/datatype.sgml @@ -4525,6 +4525,10 @@ SELECT * FROM pg_attribute trigger + + event_trigger + + language_handler @@ -4629,7 +4633,7 @@ SELECT * FROM pg_attribute record - Identifies a function returning an unspecified row type. + Identifies a function taking or returning an unspecified row type. @@ -4637,6 +4641,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. @@ -4659,10 +4668,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.