Postgres Pro
Downloads
Home   >   mailing lists

tg_trigtuple not NULL in AFTER STATEMENT triggers? - Mailing list pgsql-hackers

From Michael Fuhr
Subject tg_trigtuple not NULL in AFTER STATEMENT triggers?
Date
Msg-id 20060731142458.GA65794@winnie.fuhr.org
Whole thread Raw
Responses Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
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

pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: Connection limit and Superuser
Next
From: Tom Lane
Date:
Subject: Re: Relation locking and relcache load (was Re: Going for "all green" buildfarm results)