Re: JDBC driver's (non-)handling of InputStream:s

From: Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>
To: pg(at)fastcrypt(dot)com
Cc: PostgreSQL JDBC Mailing List <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: JDBC driver's (non-)handling of InputStream:s
Date: 2004-03-30 10:55:58
Message-ID: 200403301255.58193.peter.schuller@infidyne.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hello,

> It would be great if you could supply a test case which exhibits this
> behaviour.

I can probably do that relatively easily (though of course subject to the
behavior of the VM memory manager), though given Oliver Jowett's response it
seems pretty obvious what is happening - allocating a 5 MB byte array is
failing and/or the byte array is constructed in a tight loop allocating
incrementally larger arrays until the data fits.

Allocating such large arrays is bound to be unreliable in any case, so as long
as that is what's happening I fully understand it and there's probably not
much to be done...

--
/ Peter Schuller, InfiDyne Technologies HB

PGP userID: 0xE9758B7D or 'Peter Schuller <peter(dot)schuller(at)infidyne(dot)com>'
Key retrieval: Send an E-Mail to getpgpkey(at)scode(dot)org
E-Mail: peter(dot)schuller(at)infidyne(dot)com Web: http://www.scode.org

In response to

Browse pgsql-jdbc by date

  From Date Subject
Next Message Guido Fiala 2004-03-30 12:16:28 Re: OutOfMemory
Previous Message Peter Schuller 2004-03-30 10:48:09 Re: JDBC driver's (non-)handling of InputStream:s