OOM on large SELECT

From: Angelo Nicolosi <amenuor(at)hotmail(dot)com>
To: <pgsql-jdbc(at)postgresql(dot)org>
Subject: OOM on large SELECT
Date: 2009-09-16 13:26:36
Message-ID: SNT114-W4952152D7DBA88FD891FAFA0E20@phx.gbl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc


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.
_________________________________________________________________
Gossip, Sport, Notizie... Accendi la Messenger TV!
http://www.messenger.it/messengerTV.aspx

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Oliver Jowett 2009-09-16 15:14:31 Re: OOM on large SELECT
Previous Message Craig Ringer 2009-09-16 02:10:35 Re: BUG #5058: [jdbc] Silent failure with executeUpdate()