Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: jdbc and large binary files
- From: Oliver Jowett <oliver(at)opencloud(dot)com>
- To: Warren Little <wlittle(at)securitylending(dot)com>
- Cc: pgsql-jdbc(at)postgresql(dot)org
- Subject: Re: jdbc and large binary files
- Date: Sun, 29 Aug 2004 11:53:03 +1200
- Message-id: <41311ADF.9060207@opencloud.com> <text/plain>
Warren Little wrote:
Hello, I'm currently using the LO api with the oid data type for storing large objects. I would like to switch to bytea data. When I last tested this idea (over 8 months ago) I experienced massive memory bloat in the JDBC application. I recall seeing some threads on fixing this problem. Can anyone tell me if this issue has been addressed in the latest driver?
PreparedStatement.setBinaryStream() will now stream data directly to the server with no additional heap storage needed. setBytes() takes a copy of the bytearray it is given, but otherwise behaves like setBinaryStream().
ResultSet still stores the whole value on heap. To avoid this requires protocol modifications.
-O
- References:
- jdbc and large binary files
- From: Warren Little
- jdbc and large binary files
- Prev by Date: jdbc and large binary files
- Next by Date: Re: broken docmentation link
- Previous by thread: jdbc and large binary files
- Next by thread: JNDI Datasource configuration
- Indexes: