@@ -4561,6 +4561,10 @@ SELECT * FROM pg_attribute
45614561 <primary>trigger</primary>
45624562 </indexterm>
45634563
4564+ <indexterm zone="datatype-pseudo">
4565+ <primary>event_trigger</primary>
4566+ </indexterm>
4567+
45644568 <indexterm zone="datatype-pseudo">
45654569 <primary>language_handler</primary>
45664570 </indexterm>
@@ -4665,14 +4669,19 @@ SELECT * FROM pg_attribute
46654669
46664670 <row>
46674671 <entry><type>record</></entry>
4668- <entry>Identifies a function returning an unspecified row type.</entry>
4672+ <entry>Identifies a function taking or returning an unspecified row type.</entry>
46694673 </row>
46704674
46714675 <row>
46724676 <entry><type>trigger</></entry>
46734677 <entry>A trigger function is declared to return <type>trigger.</></entry>
46744678 </row>
46754679
4680+ <row>
4681+ <entry><type>event_trigger</></entry>
4682+ <entry>An event trigger function is declared to return <type>event_trigger.</></entry>
4683+ </row>
4684+
46764685 <row>
46774686 <entry><type>void</></entry>
46784687 <entry>Indicates that a function returns no value.</entry>
@@ -4695,10 +4704,11 @@ SELECT * FROM pg_attribute
46954704
46964705 <para>
46974706 Functions coded in procedural languages can use pseudo-types only as
4698- allowed by their implementation languages. At present the procedural
4699- languages all forbid use of a pseudo-type as argument type, and allow
4707+ allowed by their implementation languages. At present most procedural
4708+ languages forbid use of a pseudo-type as an argument type, and allow
47004709 only <type>void</> and <type>record</> as a result type (plus
4701- <type>trigger</> when the function is used as a trigger). Some also
4710+ <type>trigger</> or <type>event_trigger</> when the function is used
4711+ as a trigger or event trigger). Some also
47024712 support polymorphic functions using the types <type>anyelement</>,
47034713 <type>anyarray</>, <type>anynonarray</>, <type>anyenum</>, and
47044714 <type>anyrange</>.
0 commit comments