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

From Sean Chittenden
Subject Re: Stack not being popped correctly (was: Re: [HACKERS] plpgsql lacks generic identifier for record in triggers...)
Date
Msg-id E8AEA4ED-3E9D-11D9-841B-000A95C705DC@chittenden.org
Whole thread Raw
In response to Re: Stack not being popped correctly (was: Re: [HACKERS] plpgsql lacks generic identifier for record in triggers...)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
>> 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

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: equal operator fails on two identical strings if initdb
Next
From: Mehul Doshi-A20614
Date:
Subject: Installation fails for postgresql-8.0.0-beta4 on WindowsXP SP1