> > If I remember correctly,this has been only in case of SQL functions.
>
> True, the tlist is ignored except in SQL functions --- another reason
> why attaching it to all function nodes is a waste. I believe that's
> itself a bug, since it seems like PL functions ought to be capable
> of returning tuples (whether they actually can or not is
> another story,
> but it sure seems like plpgsql ought to be close to being able to).
> By separating the fieldselect operation into another node, we can fix
> that bug too, since it wouldn't matter what the function's
> implementation language is.
Sounds like a huge win !
Andreas
