Re: Memory leaks using refcursors

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)com>
Cc: "PostgreSQL JDBC" <pgsql-jdbc(at)postgresql(dot)org>, thierry(dot)buffet(at)fr(dot)nurun(dot)com
Subject: Re: Memory leaks using refcursors
Date: 2007-01-17 22:31:15
Message-ID: 6135.1169073075@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

"Guillaume Smet" <guillaume(dot)smet(at)gmail(dot)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

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Guillaume Smet 2007-01-17 23:27:53 Re: Memory leaks using refcursors
Previous Message Guillaume Smet 2007-01-17 22:22:54 Re: Memory leaks using refcursors