Silvio Bierman wrote:
> Can anyone explain why the PostgreSQL JDBC driver caches the result of a
> select statement in memory even though I have set a fetch size. Only
> setting autocommit to off will prevent this but that seems very
> Any explanations?
Incremental retrieval of results relies on using a v3 protocol portal
(similar to a cursor). These portals are implicitly closed at the end of
a transaction; that includes the end of the implicit transaction created
for each statement when autocommit is on. So you have to have a
long-lived transaction for incremental retrieval to be useful, i.e.
autocommit must be off.
In response to
pgsql-jdbc by date
|Next:||From: Kris Jurka||Date: 2008-10-29 17:54:23|
|Subject: Re: Re: Connection hanging on INSERT apparently due to large
batch size and 4 CPU cores|
|Previous:||From: Silvio Bierman||Date: 2008-10-29 09:16:49|
|Subject: Driver memory usage on select and autocommit|