From: Bruce Momjian <bruce@momjian.us>
Date: Wed, 7 Sep 2011 02:54:18 +0000 (-0400)
Subject: Properly document the existance of OLD/NEW trigger pl/pgsql trigger
X-Git-Tag: REL9_1_0~10
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=e4d59f35366964298b0c9d4847f0a7efd3ddf830;p=postgresql

Properly document the existance of OLD/NEW trigger pl/pgsql trigger
fields.

Backpatch to 9.0 and 9.1.

Report from Pavel Stehule, patch from Josh Kupershmidt
---

diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml
index 0a9d71ef41..d82a003fe9 100644
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3282,8 +3282,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
       <para>
        Data type <type>RECORD</type>; variable holding the new
        database row for <command>INSERT</>/<command>UPDATE</> operations in row-level
-       triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
-       and for <command>DELETE</command> operations.
+       triggers. This variable is not defined in statement-level triggers
+       or <command>DELETE</command> operations.
       </para>
      </listitem>
     </varlistentry>
@@ -3294,8 +3294,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
       <para>
        Data type <type>RECORD</type>; variable holding the old
        database row for <command>UPDATE</>/<command>DELETE</> operations in row-level
-       triggers. This variable is <symbol>NULL</symbol> in statement-level triggers
-       and for <command>INSERT</command> operations.
+       triggers. This variable is not defined in statement-level triggers
+       or <command>INSERT</command> operations.
       </para>
      </listitem>
     </varlistentry>