Re: Out of memory error on huge resultset

From: "Michael Paesold" <mpaesold(at)gmx(dot)at>
To: "Dave Cramer" <Dave(at)micro-automation(dot)net>, "Aaron Mulder" <ammulder(at)alumni(dot)princeton(dot)edu>
Cc: "pgsql-jdbc" <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: Out of memory error on huge resultset
Date: 2002-10-11 14:44:36
Message-ID: 00e601c27134$b9260570$4201a8c0@beeblebrox
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-jdbc

Dave Cramer <Dave(at)micro-automation(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Dave Cramer 2002-10-11 14:48:41 Re: Out of memory error on huge resultset
Previous Message Greg Copeland 2002-10-11 14:42:12 Re: MySQL vs PostgreSQL.

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Cramer 2002-10-11 14:48:41 Re: Out of memory error on huge resultset
Previous Message Greg Copeland 2002-10-11 14:42:12 Re: MySQL vs PostgreSQL.

Browse pgsql-jdbc by date

  From Date Subject
Next Message Dave Cramer 2002-10-11 14:48:41 Re: Out of memory error on huge resultset
Previous Message Jeffrey Duffy 2002-10-11 14:44:14 Re: NullPointer error returned from ResultSet.java