tg_trigtuple not NULL in AFTER STATEMENT triggers?

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: pgsql-hackers(at)postgresql(dot)org
Subject: tg_trigtuple not NULL in AFTER STATEMENT triggers?
Date: 2006-07-31 14:24:58
Message-ID: 20060731142458.GA65794@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I've noticed that tg_trigtuple and tg_newtuple aren't cleared to
NULL in AFTER STATEMENT triggers. Is that an oversight, or does
the code intentionally not bother because trigger functions shouldn't
be referencing those members in statement-level triggers anyway, or
is there some other reason?

--
Michael Fuhr

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-07-31 14:35:15 Re: Relation locking and relcache load (was Re: Going for "all green" buildfarm results)
Previous Message Stephen Frost 2006-07-31 14:18:47 Re: Relation locking and relcache load (was Re: Going for "all green" buildfarm results)