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

Re: Stack not being popped correctly (was: Re: [HACKERS] plpgsql lacks generic identifier for record in triggers...)

From: Sean Chittenden <sean(at)chittenden(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PGBugs List <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Stack not being popped correctly (was: Re: [HACKERS] plpgsql lacks generic identifier for record in triggers...)
Date: 2004-11-25 04:53:11
Message-ID: E8AEA4ED-3E9D-11D9-841B-000A95C705DC@chittenden.org (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
>> Which, doesn't work as expected as it seems as though there's 
>> something
>> left behind on the stack that shouldn't be.  Here's the case to
>> reproduce (doesn't involve pgmemcache):
>
>> test=# CREATE FUNCTION t5_func() RETURNS TRIGGER AS 'BEGIN EXECUTE
>> TRUE; RETURN NULL; END;' LANGUAGE 'plpgsql';
>
> What are you expecting "execute true" to do?

Behave the same as PERFORM?  Ugh, how humiliating.  When writing my 
pgmemcache presentation, I erroneously wrote EXECUTE instead of 
PERFORM.  When sending off that little flurry of emails, I was updating 
my pgmemcache presentation and subconsciously propagated the error w/o 
even thinking about it.  :-/  Thanks, I'll take that pumpkin pie on my 
face.  -sc

-- 
Sean Chittenden


In response to

pgsql-hackers by date

Next:From: Neil ConwayDate: 2004-11-25 06:04:16
Subject: Re: lwlocks and starvation
Previous:From: Tom LaneDate: 2004-11-25 04:30:46
Subject: Re: lwlocks and starvation

pgsql-bugs by date

Next:From: Andrzej WojtaszekDate: 2004-11-25 07:53:25
Subject: interval conversion bug
Previous:From: Tom LaneDate: 2004-11-25 03:52:56
Subject: Re: equal operator fails on two identical strings if initdb

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