Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- From: Michael Fuhr <mike(at)fuhr(dot)org>
- To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- Cc: pgsql-hackers(at)postgresql(dot)org
- Subject: Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- Date: Mon, 31 Jul 2006 10:15:51 -0600
On Mon, Jul 31, 2006 at 11:12:14AM -0400, Tom Lane wrote: > Michael Fuhr <mike(at)fuhr(dot)org> writes: > > I've noticed that tg_trigtuple and tg_newtuple aren't cleared to > > NULL in AFTER STATEMENT triggers. Is that an oversight, > > Probably. Send a patch? Sure. Is the switch in AfterTriggerExecute() around line 2116 in commands/trigger.c close to where I should be looking? -- 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?
- References:
- tg_trigtuple not NULL in AFTER STATEMENT triggers?
- From: Michael Fuhr
- Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- From: Tom Lane
- tg_trigtuple not NULL in AFTER STATEMENT triggers?
- Prev by Date: Re: [PATCHES] extension for sql update
- Next by Date: Re: Going for "all green" buildfarm results
- Previous by thread: Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- Next by thread: Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
- Indexes: