Skip site navigation (1) Skip section navigation (2)

Re: OutOfMemoryError - bug or human error?

From: Kris Jurka <books(at)ejurka(dot)com>
To: Fischer Krisztián <fischer(at)borganization(dot)com>
Cc: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: OutOfMemoryError - bug or human error?
Date: 2004-01-26 13:40:56
Message-ID: Pine.LNX.4.33.0401260838010.18726-100000@leary.csoft.net (view raw or flat)
Thread:
Lists: pgsql-jdbc

On Mon, 26 Jan 2004, [ISO-8859-2] Fischer Krisztin wrote:

> Hi all!
>
> I execute a select on a table which contains large rows. None the less i
> use the setFetchSize() method i get an OutOfMemeoryError.
> In my test I craeted a table with an 'int' and a 'text' column. The text
> column - in each row - is filled with a string constructed of 65536
> characters. The problem is there even if I use a fetch size of 2 rows!

The problem is that the fetch size is ignored when using a ResultSet of
TYPE_SCROLL_INSENSITIVE.  This only works for TYPE_FORWARD_ONLY.

Kris Jurka


In response to

pgsql-jdbc by date

Next:From: Barry LindDate: 2004-01-26 14:24:58
Subject: Re: Using gettext for JDBC translations
Previous:From: Fischer KrisztiánDate: 2004-01-26 13:19:31
Subject: Re: executeUpdate() deadlock

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group