OOM on large SELECT

Поиск
Список
Период
Сортировка
Искать
От
Angelo Nicolosi
Тема
OOM on large SELECT
Дата
Msg-id
SNT114-W4952152D7DBA88FD891FAFA0E20@phx.gbl
Список
Дерево обсуждения
OOM on large SELECT Angelo Nicolosi <amenuor@hotmail.com>
Re: OOM on large SELECT Oliver Jowett <oliver@opencloud.com>
Re: OOM on large SELECT Angelo Nicolosi <amenuor@hotmail.com>
Re: OOM on large SELECT John R Pierce <pierce@hogranch.com>
Re: OOM on large SELECT Angelo Nicolosi <amenuor@hotmail.com>
Re: OOM on large SELECT Hannu Krosing <hannu@2ndQuadrant.com>
Re: OOM on large SELECT Angelo Nicolosi <amenuor@hotmail.com>
Re: OOM on large SELECT John R Pierce <pierce@hogranch.com>
Re: OOM on large SELECT Oliver Jowett <oliver@opencloud.com>
Hello,
I'm Angelo and I'm new in this list.
I'm a student in computer science and I'm working on a project with the postgres.
I wrote some C-Language functions, added on a database and a client, written in Java, has to use them.
There was the problem that if the table on which the client was working was larger than 10000 entries, the postgres was killed by the OOM. Surfing on internet for a solution I found that one of disable the Auto-commit when the client make the big SELECTs.
But the problem remain.
The dmesg command says:

Out of memory: Killed process 22592 (postgres).

And the only thing that the client outputs is: Killed.
On various web pages some people said that the problem could be a bug of the JDBC driver, because it doesn't really close the ResultSets. Is this true? There is some way to resolve the problem?
Thank you in advance for your help.

Cheers,
Angelo.


Una risposta istantanea? Usa Messenger da Hotmail
В списке pgsql-jdbc по дате отправления
От: Oliver Jowett
Дата:
От: Oliver Jowett
Дата:
Сообщение: Re: OOM on large SELECT
FAQ