Re: Memory leaks using refcursors - Mailing list pgsql-jdbc

From Guillaume Smet
Subject Re: Memory leaks using refcursors
Date
Msg-id 1d4e0c10701190526k3282d919l41e5d0d081b9ee25@mail.gmail.com
Whole thread Raw
In response to Re: Memory leaks using refcursors  (Dave Cramer <pg@fastcrypt.com>)
Responses Re: Memory leaks using refcursors
Re: Memory leaks using refcursors
List pgsql-jdbc
Hi Dave,

On 1/19/07, Dave Cramer <pg@fastcrypt.com> wrote:
> I've asked Guillaume to test this hypothesis with his test case that
> does not use XA to see if the memory "leak" still exists without XA

Perhaps I was not clear when I explained the remaining problem. I
don't have any memory leak left. The attached file is a test case
which shows the new problem.

The commit is done before closing the resultset and so the close()
method can't find the portal which results in an exception (the portal
is closed on commit).
It's probably not something we should do but before there was no error
in this case and now it throws an exception which is not really clear
for the end user:
An exception has occured.ERROR: cursor "<unnamed portal 1>" does not exist
org.postgresql.util.PSQLException: ERROR: cursor "<unnamed portal 1>"
does not exist

--
Guillaume

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Memory leaks using refcursors
Next
From: "Guillaume Smet"
Date:
Subject: Re: Memory leaks using refcursors