Skip site navigation (1) Skip section navigation (2)

RE: Anyone particularly wedded to func_tlist mechanism?

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$ (view raw, whole thread or download thread mbox)
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.


Hiroshi Inoue

In response to

pgsql-hackers by date

Next:From: Hiroshi InoueDate: 2000-08-04 02:41:21
Subject: RE: Raw constraint & pg_relcheck.rcsrc
Previous:From: Roland RobertsDate: 2000-08-04 01:36:49
Subject: RH 6.1, PostgreSQL 7.0.2, ipcclean madness

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group