Re: Out of memory error on huge resultset
Michael Paesold <mpaesold@gmx.at>
From: "Michael Paesold" <mpaesold@gmx.at>
To: "Dave Cramer" <Dave@micro-automation.net>, "Aaron Mulder" <ammulder@alumni.princeton.edu>
Cc: "pgsql-jdbc" <pgsql-jdbc@postgresql.org>
Date: 2002-10-11T14:44:36Z
Lists: pgsql-hackers, pgsql-general
Dave Cramer <Dave@micro-automation.net> wrote: > No disadvantage, in fact that is what we would like to do. > > > setFetchSize(size) turns on cursor support, otherwise fetch normally > > Dave > > On Fri, 2002-10-11 at 10:30, Aaron Mulder wrote: > > What would be the disadvantage of making the JDBC driver use a > > cursor under the covers (always)? Is it significantly slower or more > > resource-intensive than fetching all the data at once? Certainly it seems > > like it would save memory in some cases. > > > > Aaron Well, using a cursor based result set *always* is not going to work. Cursors will not be held over a commit, whereas a buffer result set will. So the setFetchSize.. Regards, Michael Paesold