Re: Out of memory error on huge resultset
От | Michael Paesold |
---|---|
Тема | Re: Out of memory error on huge resultset |
Дата | |
Msg-id | 00e601c27134$b9260570$4201a8c0@beeblebrox обсуждение исходный текст |
Ответ на | Re: Out of memory error on huge resultset (Aaron Mulder <ammulder@alumni.princeton.edu>) |
Ответы |
Re: Out of memory error on huge resultset
|
Список | pgsql-jdbc |
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 по дате отправления: