Re: Memroy leak with jdbc

Поиск
Список
Период
Сортировка
От Joseph Shraibman
Тема Re: Memroy leak with jdbc
Дата
Msg-id 3EB70BB7.1010307@selectacast.net
обсуждение исходный текст
Ответ на Re: Memroy leak with jdbc  (Oliver Jowett <oliver@opencloud.com>)
Список pgsql-jdbc
Specifically, this code in QueryExecutor:


    case 'N':    // Error Notification
                        connection.addWarning(pgStream.ReceiveString(connection.getEncoding()));
                        break;

At that point the ResultSet doesn't necc. exist, but the Statement does.  There are a few
approaches to fixing this:

1) Clear the warnings before executing the query
2) Appeneding the warnings to the Statement
3) Keeping our own warnings chain, then appending the whole chain after the ResultSet is
created.

Personally I perfer #3, but could there be a case where the ResultSet isn't created
because of some other error, and then we don't want to lose the warning?


В списке pgsql-jdbc по дате отправления:

Предыдущее
От: Joseph Shraibman
Дата:
Сообщение: Re: Memroy leak with jdbc
Следующее
От: "Dirk Bromberg"
Дата:
Сообщение: Re: Memory footprint for a single connection