It's at the moment probably more efficient to not use a stored  
procedure but query the cursor from your application instead (saves  
one of the two seqscans). That has it's own disadvantages of course.  
I've used something like that (as a function in our PHP application)  
on a medium-sized data set before, and it performed adequately.

Alban Hertroys

--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.



!DSPAM:737,49cb5930129747428277249!