Re: SRF in SFRM_ValuePerCall mode
От | dv @ nabble |
---|---|
Тема | Re: SRF in SFRM_ValuePerCall mode |
Дата | |
Msg-id | B86969222F0149D59791DF1C82B25D2A@dvhome обсуждение исходный текст |
Ответ на | Re: SRF in SFRM_ValuePerCall mode ("Heikki Linnakangas" <heikki@enterprisedb.com>) |
Список | pgsql-hackers |
OK, Thank you for the explanation, I hope this will be implemented in future. We will try and find a workaround to this issue until then. Denis ----- Original Message ----- From: "Heikki Linnakangas" <heikki@enterprisedb.com> To: "dv @ nabble" <dvnabble@gmail.com> Cc: "pgsql-hackers list" <pgsql-hackers@postgresql.org> Sent: Monday, April 28, 2008 1:56 PM Subject: Re: [HACKERS] SRF in SFRM_ValuePerCall mode > 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 по дате отправления: