Re: Out of memory error on huge resultset
Dave Cramer <dave@micro-automation.net>
From: Dave Cramer <Dave@micro-automation.net>
To: nferrier@tapsellferrier.co.uk
Cc: Aaron Mulder <ammulder@alumni.princeton.edu>, pgsql-jdbc <pgsql-jdbc@postgresql.org>
Date: 2002-10-11T14:52:34Z
Lists: pgsql-hackers, pgsql-general
Just so you know this isn't implemented yet. My reference to setFetchSize below was just a suggestion as to how to implement it Dave On Fri, 2002-10-11 at 10:52, nferrier@tapsellferrier.co.uk wrote: > Dave Cramer <Dave@micro-automation.net> writes: > > > No disadvantage, in fact that is what we would like to do. > > > > > > setFetchSize(size) turns on cursor support, otherwise fetch > > normally > > I love PostgreSQL's default behaviour: it's great to know > that a server side cursor resource is probably not hanging around for > simple querys. > > > > Nic > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > >