Re: Memory leaks using refcursors
От | Guillaume Smet |
---|---|
Тема | Re: Memory leaks using refcursors |
Дата | |
Msg-id | 1d4e0c10701190526k3282d919l41e5d0d081b9ee25@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Memory leaks using refcursors (Dave Cramer <pg@fastcrypt.com>) |
Ответы |
Re: Memory leaks using refcursors
Re: Memory leaks using refcursors |
Список | 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 по дате отправления: