From: Bruce Momjian Date: Wed, 7 Sep 2011 02:54:19 +0000 (-0400) Subject: Properly document the existance of OLD/NEW trigger pl/pgsql trigger X-Git-Tag: REL9_0_5~10 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a443343ccf2d7b105ce550b5746d993151569d93;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 b3016aed54..ab9fdc0542 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -3072,8 +3072,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. @@ -3084,8 +3084,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.