Re: SRF in SFRM_ValuePerCall mode - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: SRF in SFRM_ValuePerCall mode
Date
Msg-id 4815AD52.40707@enterprisedb.com
Whole thread Raw
In response to SRF in SFRM_ValuePerCall mode  ("dv @ nabble" <dvnabble@gmail.com>)
Responses Re: SRF in SFRM_ValuePerCall mode  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: SRF in SFRM_ValuePerCall mode  ("dv @ nabble" <dvnabble@gmail.com>)
List pgsql-hackers
dv @ nabble wrote:
> I am working on implementation of custom "C" SRF for our team. The SRF uses
> SFRM_ValuePerCall mode. I know that sometimes even in SFRM_ValuePerCall 
> mode
> all the rows returned from SRF are "materialized" (for performing JOINs, 
> for
> example).

Yep, they are unfortunately always materialized. Back when set returning 
functions were implemented, the original patch did actually support true 
"value per call" mode, where the whole result set was not materialized. 
However, it was dropped because of some issues I can't remember off the 
top of my head. The value-per-call API was committed, so that it was 
already in place when someone gets around to implement the backend 
support for it.

However, no-one has bothered to do that to this date. Hannu Krosing 
showed some interest in it recently, though: 
http://archives.postgresql.org/pgsql-hackers/2008-04/msg00345.php. I 
would love to see it happen.

--   Heikki Linnakangas  EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: "dv @ nabble"
Date:
Subject: SRF in SFRM_ValuePerCall mode
Next
From: "Tom Dunstan"
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing