Skip site navigation (1) Skip section navigation (2)

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: 2006-07-31 16:15:51
Message-ID: 20060731161551.GA66938@winnie.fuhr.org (view raw or flat)
Thread:
Lists: pgsql-hackers
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

In response to

Responses

pgsql-hackers by date

Next:From: Jim C. NasbyDate: 2006-07-31 16:20:32
Subject: Re: Going for "all green" buildfarm results
Previous:From: Rod TaylorDate: 2006-07-31 16:08:22
Subject: Re: [PATCHES] extension for sql update

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group