Postgres Pro
Downloads
Home   >   mailing lists

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

From Michael Fuhr
Subject Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?
Date
Msg-id 20060731161551.GA66938@winnie.fuhr.org
Whole thread Raw
In response to Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: tg_trigtuple not NULL in AFTER STATEMENT triggers?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tree view 
On Mon, Jul 31, 2006 at 11:12:14AM -0400, Tom Lane wrote:
> Michael Fuhr <mike@fuhr.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

pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: [PATCHES] extension for sql update
Next
From: "Jim C. Nasby"
Date:
Subject: Re: Going for "all green" buildfarm results