Re: JDBC driver's (non-)handling of InputStream:s - Mailing list pgsql-jdbc

From Peter Schuller
Subject Re: JDBC driver's (non-)handling of InputStream:s
Date
Msg-id 200403301255.58193.peter.schuller@infidyne.com
Whole thread Raw
In response to Re: JDBC driver's (non-)handling of InputStream:s  (Dave Cramer <pg@fastcrypt.com>)
List 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.schuller@infidyne.com>'
Key retrieval: Send an E-Mail to getpgpkey@scode.org
E-Mail: peter.schuller@infidyne.com Web: http://www.scode.org


pgsql-jdbc by date:

Previous
From: Andrea Aime
Date:
Subject: Re: V3 protocol, batch statements and binary transfer
Next
From: Alan Stange
Date:
Subject: Re: V3 protocol, batch statements and binary transfer