Re: BUG #1240: memory leak in JDBC driver build 215

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: BUG #1240: memory leak in JDBC driver build 215
Дата
Msg-id Pine.LNX.4.61.0409061745020.2431@sablons.cri.ensmp.fr
обсуждение исходный текст
Ответ на BUG #1240: memory leak in JDBC driver build 215  ("PostgreSQL Bugs List" <pgsql-bugs@postgresql.org>)
Ответы Re: BUG #1240: memory leak in JDBC driver build 215  (Roland Walter <rwa@mosaic-ag.com>)
Список pgsql-bugs
> 328   [main] DEBUG com.mosaicag.rwa.dbutil.standard.DefaultCsvExport  -
> executing SQL-Stmt: SELECT * FROM transaction WHERE transaction_date >=
> to_timestamp('01.01.2002', 'DD.MM.YYYY') AND transaction_date <
> to_timestamp('01.01.2003', 'DD.MM.YYYY')
> java.lang.OutOfMemoryError
> Exception in thread "main"

Maybe the JDBC drivier tries to allocate the whole result of the query?
If so, it is not a memory leak, it's a big memory need;-)

You might try using a cursor manually (well, if it is the problem, then it
just shows that jdbc should do it by default). Something like:

DECLARE CURSOR foo FOR your-select-query...;
FETCH FORWARD 10 FROM foo;
FETCH FORWARD 10 FROM foo;
FETCH FORWARD 10 FROM foo;
...
CLOSE foo;

Hope this help.

--
Fabien Coelho - coelho@cri.ensmp.fr

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

Предыдущее
От: "PostgreSQL Bugs List"
Дата:
Сообщение: BUG #1240: memory leak in JDBC driver build 215
Следующее
От: Fabien COELHO
Дата:
Сообщение: error in simple sql function breaks connection