From: | Jim Davis <j(dot)a(dot)davis(at)larc(dot)nasa(dot)gov> |
---|---|
To: | Roland Walter <rwa(at)mosaic-ag(dot)com> |
Cc: | <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: Exception in thread "main" java.lang.OutOfMemoryError: |
Date: | 2006-08-25 12:10:06 |
Message-ID: | 44EEE89E.8060506@larcb.ecs.nasa.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
Jim Davis wrote:
I changed the executeUpdate to just an execute, saved, re-ran java
application and received the same
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
error.
Roland Walter wrote:
> Jim Davis schrieb:
>
>> I am not a java programmer, so it is possible I am doing something
>> wrong:
>>
>> I saw this problem initially on my test system using sequoia jdbc
>> driver with my postgresql 8.1.4 database servers trying
>> to create an index on a 27 million row table. After many suggestions
>> and tests, It was suggested I try using the postgresql
>> jdbc driver to perform the create index to try and isolate where the
>> out of memory condition is occurring. So I edited a
>> java application I was testing with and pointed it to the postgresql
>> jdbc driver. I used version postgresql-.2dev-503.jdbc3.jar
>> the first time and postgresql-9.2dev-503.jdbc3.jar the second time
>> with the same results: Exception in thread "main"
>> java.lang.OutOfMemoryError: Java heap space
>>
> I have no idea, why this happens. I would not expect that. But i saw
> in your code example that you use executeUpdate for a defining sql
> statement. I would use just the execute method. A cursor should not
> be needed.
>
> Regards,
> Roland.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Audette | 2006-08-25 12:21:00 | Re: [ADMIN] CMS - portal server Question |
Previous Message | Bradley Kieser | 2006-08-25 11:48:17 | Re: CMS - portal server Question |