Re: Workarounds for getBinaryStream returning ByteArrayInputStream on bytea

From: Александър Шопов <lists(at)kambanaria(dot)org>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Workarounds for getBinaryStream returning ByteArrayInputStream on bytea
Date: 2010-11-24 22:53:31
Message-ID: 1290639211.3659.15.camel@dalgonosko
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-jdbc

В 16:04 -0600 на 24.11.2010 (ср), Radosław Smogura написа:
> I see only two possibilities
> 1. Decrease fetch size, e.g. to 1.
Even if I do, bytea is potentially 1GB. Plus peaks in usage can still
smash the heap.
So refactoring to BLOBs is perhaps the only way out.
Will the JDBC driver always present bytea InputStream as
ByteArrayInputStream? No plans to change that? (even if there are, I
will still have to refactor meanwhile).
Perhaps this behaviour should be better communicated to DB schema
designers.
It seems to me from the Npgsql2.0.11 readme.txt that reading in chunks
is provided for .Net.
Is there need to perhaps make patches for this in the jdbc driver?
Kind regards:
al_shopov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-11-24 22:54:31 Re: pgsql: Remove useless whitespace at end of lines
Previous Message Tom Lane 2010-11-24 22:49:42 Re: profiling pgbench

Browse pgsql-jdbc by date

  From Date Subject
Next Message vwu98034 2010-11-24 23:59:01 Do anyone know the cause of this exception?
Previous Message Radosław Smogura 2010-11-24 22:04:49 Re: Workarounds for getBinaryStream returning ByteArrayInputStream on bytea