Re: Memory leaks using refcursors

Just a post to answer to the question of Dave Cramer on IRC and have a
comprehensive thread:
23:07 <dcramer> how would it know the cursor was open ?

AFAICS there's code in the driver to deal with the refcursor,
especially to get the cursor name and fetch all the results to a
result set.
Isn't there a way to keep the cursor name and close it automatically
when the statement or the resulting result set is closed?

I don't see an easy way to do it in the application directly (but any
tip is welcome) and ISTM it should be dealt by the driver directly to
prevent the memory usage of the backend growing dramatically during
the transaction.

--
Guillaume