Re: [JDBC] Re: no way in LargeObject API to detect short read?

From: aoki(at)acm(dot)org (Paul M(dot) Aoki)
To: Peter T Mount <peter(at)retep(dot)org(dot)uk>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org, PostgreSQL jdbc list <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: [JDBC] Re: no way in LargeObject API to detect short read?
Date: 2001-01-26 19:12:44
Message-ID: 200101261912.f0QJCj728572@faerie.CS.Berkeley.EDU
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-jdbc

Peter T Mount <peter(at)retep(dot)org(dot)uk> writes:
> Hmmm, what's the performance issues with this? Is there going to be a problem
> with very large LargeObject's?

you could probably be smarter about caching previous tell() state, if
that's what you mean.

jun's hack doesn't actually add any extra buffers or copies.
--
Paul M. Aoki / Xerox Palo Alto Research Center / 3333 Coyote Hill Road
aoki(at)acm(dot)org / Computer Science Laboratory / Palo Alto, CA 94304-1314

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2001-01-26 20:10:02 Re: JDBC driver throws SQLException while parsing timestamp
Previous Message Michael Davis 2001-01-26 17:50:17 Bug with foreign keys and importing from a pg_dump file?

Browse pgsql-jdbc by date

  From Date Subject
Next Message Bruce Momjian 2001-01-26 20:15:47 Re: Re: [JDBC] Open 7.1 items
Previous Message Peter Eisentraut 2001-01-26 15:07:27 Re: Open 7.1 items