Search Postgresql Archives

return next

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'm attempting to make a table function that starts returning to the
client before the entire result set is constructed.

>From the docs on plperl:
"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. You can do this with return_next as illustrated below."

However, when I do a simple plperl function:

create or replace function itab(int) returns setof int as $$
for (0..$_[0]-1) {
    return_next $_;
}
return undef;
$$ language plperlu;

It seems to always try to build the entire result first. For example, if
I put a "sleep 1" in the loop and do "select * from itab(10) limit 1" it
takes 10 seconds rather than 1 second. Same if I use a cursor and just
fetch one.

Am I misunderstanding the docs? How do I just return one tuple at a time
without PostgreSQL continuing the loop?

I'm using PostgreSQL 8.1.

Regards,
	Jeff Davis

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux