Re: Accessing original TupleDesc from SRF - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Accessing original TupleDesc from SRF
Date
Msg-id 896.1030720598@sss.pgh.pa.us
Whole thread Raw
In response to Re: Accessing original TupleDesc from SRF  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
Joe Conway <mail@joeconway.com> writes:
> John Gray wrote:
>> Does this sound completely crazy?

> Not crazy at all. I asked the same question a few days ago:
> http://archives.postgresql.org/pgsql-hackers/2002-08/msg01914.php

I've been thinking more about this, and wondering if we should not
only make the tupdesc available but rely more heavily on it than we
do.  Most of the C-coded functions do fairly substantial pushups to
construct tupdescs that are just going to duplicate what
nodeFunctionscan already has in its back pocket.  They could save some
time by just picking that up and using it.

On the other hand, your experience yesterday with debugging a mismatched
function declaration suggests that it's still a good idea to make the
functions build the tupdesc they think they are returning.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [7.3devl] Using PGPASSWORDFILE with psql requires -U
Next
From: Tom Lane
Date:
Subject: Re: Accessing original TupleDesc from SRF