Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers

From: Josh Kupershmidt <schmiddy(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-docs <pgsql-docs(at)postgresql(dot)org>
Subject: Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers
Date: 2011-09-07 13:21:06
Message-ID: CAK3UJRH+cQwHr9EBUYBx3VVhD6fur6v8w28PzjhWohNKYV-rbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-docs

On Tue, Sep 6, 2011 at 10:54 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Josh Kupershmidt wrote:
>> How about a doc tweak like the attached?
>
> Perfect.  Applied to 9.0, 9.1, and head.  Thanks.  Sorry for the delay.

Err, as Tom's first comment in this thread explains, Pavel and I were
both wrong: the variables in question are indeed NULL, not undefined.
I think the docs were fine the way they were.

Josh

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2011-09-07 13:24:27 Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers
Previous Message Rodriguez Fernando 2011-09-07 11:50:46 Re: In Windows Server 2008 PostgreSQL8.3 service on Local Computer started and then stopped.

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2011-09-07 13:24:27 Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers
Previous Message Bruce Momjian 2011-09-07 02:54:39 Re: [BUGS] documentation bug - behave of NEW a OLD in plpgsql's triggers