Re: Memory leaks using refcursors

"Guillaume Smet" <guillaume.smet@gmail.com> writes:
> Isn't there a way to keep the cursor name and close it automatically
> when the statement or the resulting result set is closed?

While I agree that the driver probably should do that, I'm not sure why
you are having a problem.  A cursor doesn't normally accumulate its
result set in memory on the backend side, so I wouldn't have expected
all that big a memory leak.  What queries are you executing?

            regards, tom lane