Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal: - Mailing list pgsql-patches

From Tom Lane
Subject Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Date
Msg-id 14214.1041210337@sss.pgh.pa.us
Whole thread Raw
In response to Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:  (Joe Conway <mail@joeconway.com>)
Responses Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:  (Joe Conway <mail@joeconway.com>)
List pgsql-patches
Joe Conway <mail@joeconway.com> writes:
> Tom Lane wrote:
>> Agreed.  The Berkeley code (or more accurately, the descendant code
>> that's in our source tree) generates the cross product of the rows
>> output by the SRFs, but I've never understood why that should be a good
>> approach to take.  I could live with just rejecting multiple SRFs in the
>> same targetlist --- at least till someone comes up with a convincing
>> semantics for such a thing.

> I would like to start spending some time digging in to this. Any pointers or
> thoughts on the best way to implement it? A little direction might save me
> days of wheel spinning :-).

Implement what exactly?

The code that presently does the dirty work is in ExecTargetList(), if
that's what you're looking for...

            regards, tom lane

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Next
From: Joe Conway
Date:
Subject: Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal: