From: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
---|---|
To: | rod(at)iol(dot)ie |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgresql for a CEP app |
Date: | 2010-09-29 10:21:39 |
Message-ID: | 665251.96009.qm@web29019.mail.ird.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> In pl/pgsql at any rate, functions which return a set of rows build up
> the entire result set in memory and then return the set in one go:
Ok, then pl/pgsql and pl/python (which can't return SETOF) are ruled out.
(Thank you for pointing that out).
But pl/perl seems to do the trick:
"PL/Perl functions can also return sets of either scalar or composite types.
Usually you'll want to return rows one at a time, both to speed up startup
time and to keep from queueing up the entire result set in memory"
Any other issues anyone can think about?
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-09-29 10:29:27 | Re: Optimizing postgresql.conf for dedicated windows server 2003 x64 standard edition |
Previous Message | Andrus | 2010-09-29 10:11:50 | Optimizing postgresql.conf for dedicated windows server 2003 x64 standard edition |