plpgsql EXECUTE will not set FOUND

From: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
To: PGDG <pgsql-hackers(at)postgresql(dot)org>
Subject: plpgsql EXECUTE will not set FOUND
Date: 2009-10-22 20:34:53
Message-ID: m2tyxr5frm.fsf@hi-media.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


But it will set GET DIAGNOSTIC ... = ROW_COUNT, am I being told on IRC.

I was really suprised FOUND is not set by EXECUTE in 8.3 when doing a
partitioning UPDATE trigger (we partition a summary table and have to
see about doing UPSERT).

As I wouldn't have figured GET DIAGNOSTIC was the way to go, I had to
resort to unclean method, namely EXECUTE ... RETURNING ... INTO then
checking the variable against NULL.

Why isn't that a bug again, that GET DIAGNOSTIC and FOUND are not
exposing the same reality?
--
dim

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Marko Tiikkaja 2009-10-22 22:08:21 Writeable CTEs, again
Previous Message Greg Stark 2009-10-22 20:25:22 Re: per table random-page-cost?