Re: Out of memory error on huge resultset - Mailing list pgsql-jdbc

From Dave Cramer
Subject Re: Out of memory error on huge resultset
Date
Msg-id 1034347722.2777.81.camel@inspiron.cramers
Whole thread Raw
In response to Re: Out of memory error on huge resultset  ("Michael Paesold" <mpaesold@gmx.at>)
List pgsql-jdbc
Michael,

You are correct, commit will effectively close the cursor.

This is the only way to deal with large result sets however.

Dave
On Fri, 2002-10-11 at 10:44, Michael Paesold wrote:
> 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
>
>



pgsql-jdbc by date:

Previous
From: nferrier@tapsellferrier.co.uk
Date:
Subject: Re: Out of memory error on huge resultset
Next
From: Dave Cramer
Date:
Subject: Re: Out of memory error on huge resultset