From: | "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | RE: Anyone particularly wedded to func_tlist mechanism? |
Date: | 2000-08-04 00:43:50 |
Message-ID: | 000301bffdad$0ebcffa0$2801007e@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane
>
> The "target list" that's added to function-call nodes in expressions
> has bugged me for a long time, because it seems to clutter expression
> trees quite a bit (thus wasting space in stored rules, for example)
> without really being used for much.
>
> I've now dug around and determined that the only thing it is used for
> is selecting out a single field from a function that returns a tuple.
I don't understand details about current fmgr changes,sorry.
If I remember correctly,this has been only in case of SQL functions.
In addition,SQL functions has returned a TupleTableSlot not a tuple
if the return type is a compound type. Has it been changed already ?
Or would it be changed ?
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-08-04 00:54:02 | pg_dump/restore to convert BLOBs to LZTEXT (optional!) |
Previous Message | Chris Bitmead | 2000-08-04 00:21:28 | Re: Anyone particularly wedded to func_tlist mechanism? |