В 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
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?
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-11-24 22:54:31|
|Subject: Re: pgsql: Remove useless whitespace at end of lines |
|Previous:||From: Tom Lane||Date: 2010-11-24 22:49:42|
|Subject: Re: profiling pgbench |
pgsql-jdbc by date
|Next:||From: vwu98034||Date: 2010-11-24 23:59:01|
|Subject: Do anyone know the cause of this exception?|
|Previous:||From: Radosław Smogura||Date: 2010-11-24 22:04:49|
|Subject: Re: Workarounds for getBinaryStream returning ByteArrayInputStream