| 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 02:00:52 |
| Message-ID: | 000401bffdb7$d191d0a0$2801007e@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
>
> "Hiroshi Inoue" <Inoue(at)tpf(dot)co(dot)jp> writes:
>
> > In addition,SQL functions has returned a TupleTableSlot not a tuple
> > if the return type is a compound type.
>
> Right, the Datum representation of a tuple type is a pointer to a
> TupleTableSlot, so that's what this new FieldSelect node would expect
> to see at runtime. I don't see any need to change that.
>
I see. Fieldselect node could expect to see the tuple descriptor used
to store the HeapTuple.
BTW,AFAIK PL/pgSQL functions return a HeapTuple directly.
Regards.
Hiroshi Inoue
Inoue(at)tpf(dot)co(dot)jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-08-04 02:41:21 | RE: Raw constraint & pg_relcheck.rcsrc |
| Previous Message | Roland Roberts | 2000-08-04 01:36:49 | RH 6.1, PostgreSQL 7.0.2, ipcclean madness |