Re: PLPGSQL and FOUND stange behaviour after EXECUTE - Mailing list pgsql-bugs

From Neil Conway
Subject Re: PLPGSQL and FOUND stange behaviour after EXECUTE
Date
Msg-id 4160F96F.3060809@samurai.com
Whole thread Raw
In response to Re: PLPGSQL and FOUND stange behaviour after EXECUTE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PLPGSQL and FOUND stange behaviour after EXECUTE  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tom Lane wrote:
> Yeah, this has been on my to-do list for awhile...

Ah, ok. Is this something you want to handle, or should I take a look?

> One question here is whether Oracle's PL/SQL has a
> precedent, and if so which way does it point?

I did some limited testing of this, and it appears that PL/SQL's EXECUTE
IMMEDIATE modifies SQL%FOUND.

-Neil

pgsql-bugs by date:

Previous
From: Sean Chittenden
Date:
Subject: bgwriter interfering with consistent view of system tables?
Next
From: Sean Chittenden
Date:
Subject: Denial of service via VACUUM, all backends exit and restart...