Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Joe Conway <mail(at)joeconway(dot)com>
Cc: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Date: 2002-12-30 01:05:37
Message-ID: 14214.1041210337@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Joe Conway <mail(at)joeconway(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2002-12-30 01:18:08 Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Previous Message Joe Conway 2002-12-30 00:58:00 Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:

Browse pgsql-patches by date

  From Date Subject
Next Message Joe Conway 2002-12-30 01:18:08 Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Previous Message Joe Conway 2002-12-30 00:58:00 Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal: