Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Mon, 31 Jul 2006 08:24:58 -0600
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
- Follow-Ups:
- Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- From: Tom Lane
- Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- Prev by Date: Re: Connection limit and Superuser
- Next by Date: Re: Relation locking and relcache load (was Re: Going for "all green" buildfarm results)
- Previous by thread: User-defined typle similar to char(length) varchar(length)
- Next by thread: Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- Indexes: