| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: C function accepting/returning cstring vs. text |
| Date: | 2010-01-27 22:46:35 |
| Message-ID: | 15719.1264632395@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> When the set-returning-function feature was written originally, years
> ago, the tuple at a time mode did really work tuple at a time. But it
> had issues and was axed out of the patch before it was committed, to
> keep it simple. The idea was to revisit it at some point, but it hasn't
> bothered anyone enough to fix it. It's basically "not implemented yet".
It depends on call context --- you're speaking of the nodeFunctionScan
context, but I believe an SRF called in the select targetlist will
operate in tuple-at-a-time mode if the function allows.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David E. Wheeler | 2010-01-27 22:51:29 | Re: make everything target |
| Previous Message | Tom Lane | 2010-01-27 22:38:37 | Re: make everything target |