| From: | nferrier(at)tapsellferrier(dot)co(dot)uk |
|---|---|
| To: | Dave Cramer <Dave(at)micro-automation(dot)net> |
| Cc: | Aaron Mulder <ammulder(at)alumni(dot)princeton(dot)edu>, pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Out of memory error on huge resultset |
| Date: | 2002-10-11 14:52:18 |
| Message-ID: | u7kgpxc2l.fsf@tapsellferrier.co.uk |
| 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> 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2002-10-11 14:52:34 | Re: Out of memory error on huge resultset |
| Previous Message | Dave Cramer | 2002-10-11 14:48:41 | Re: Out of memory error on huge resultset |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2002-10-11 14:52:34 | Re: Out of memory error on huge resultset |
| Previous Message | Greg Copeland | 2002-10-11 14:49:17 | Re: Peer to peer replication of Postgresql databases |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2002-10-11 14:52:34 | Re: Out of memory error on huge resultset |
| Previous Message | Dave Cramer | 2002-10-11 14:48:41 | Re: Out of memory error on huge resultset |