Re: plpgsql and INSERT/UPDATE/DELETE RETURNING - Mailing list pgsql-hackers

From Tom Lane
Subject Re: plpgsql and INSERT/UPDATE/DELETE RETURNING
Date
Msg-id 26553.1155599769@sss.pgh.pa.us
Whole thread Raw
In response to Re: plpgsql and INSERT/UPDATE/DELETE RETURNING  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> Aggregates sound interesting, though I'm not sure how useful they'd
> actually be. I think something like
>    FOR v_row IN (UPDATE ... RETURNING ...)
> would be a lot more useful (if it's not already in the patch).

It's not.  I thought about it for a bit but there are some nasty gotchas
if the planner decides it needs to rescan the subquery multiple times.
I'd say that's something to leave for 8.3 ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: domains code query
Next
From: andrew@dunslane.net
Date:
Subject: Re: domains code query