Re: SRF in SFRM_ValuePerCall mode

Поиск
Список
Период
Сортировка
От Heikki Linnakangas
Тема Re: SRF in SFRM_ValuePerCall mode
Дата
Msg-id 4815AD52.40707@enterprisedb.com
обсуждение исходный текст
Ответ на SRF in SFRM_ValuePerCall mode  ("dv @ nabble" <dvnabble@gmail.com>)
Ответы Re: SRF in SFRM_ValuePerCall mode  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: SRF in SFRM_ValuePerCall mode  ("dv @ nabble" <dvnabble@gmail.com>)
Список 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 по дате отправления:

Предыдущее
От: "dv @ nabble"
Дата:
Сообщение: SRF in SFRM_ValuePerCall mode
Следующее
От: "Tom Dunstan"
Дата:
Сообщение: Re: Re: [COMMITTERS] pgsql: Update: < * Allow adding enumerated values to an existing