From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | AW: Anyone particularly wedded to func_tlist mechanism? |
Date: | 2000-08-07 16:15:59 |
Message-ID: | 11C1E6749A55D411A9670001FA687963368043@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > If I remember correctly,this has been only in case of SQL functions.
>
> True, the tlist is ignored except in SQL functions --- another reason
> why attaching it to all function nodes is a waste. I believe that's
> itself a bug, since it seems like PL functions ought to be capable
> of returning tuples (whether they actually can or not is
> another story,
> but it sure seems like plpgsql ought to be close to being able to).
> By separating the fieldselect operation into another node, we can fix
> that bug too, since it wouldn't matter what the function's
> implementation language is.
Sounds like a huge win !
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2000-08-07 16:28:37 | Re: [HACKERS] Re: Trouble with float4 afterupgrading from 6.5.3 to 7.0.2 |
Previous Message | Philip Warner | 2000-08-07 16:15:45 | Re: [HACKERS] Re: Trouble with float4 after upgrading from 6.5.3 to 7.0.2 |