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 d9b4e615e09e04fe13576102033d9653f51e4aac..0deca0988be19c3b188e5b68fd8b1fdcdec52896 100644 (file)
--- a/doc/src/sgml/plpgsql.sgml
+++ b/doc/src/sgml/plpgsql.sgml
@@ -3373,8 +3373,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
       
        Data type RECORD; variable holding the new
        database row for INSERT/UPDATE operations in row-level
-       triggers. This variable is NULL in statement-level triggers
-       and for DELETE operations.
+       triggers. This variable is not defined in statement-level triggers
+       or DELETE operations.
       
      
     
@@ -3385,8 +3385,8 @@ RAISE unique_violation USING MESSAGE = 'Duplicate user ID: ' || user_id;
       
        Data type RECORD; variable holding the old
        database row for UPDATE/DELETE operations in row-level
-       triggers. This variable is NULL in statement-level triggers
-       and for INSERT operations.
+       triggers. This variable is not defined in statement-level triggers
+       or INSERT operations.