| From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC gripe list |
| Date: | 2011-03-27 15:19:45 |
| Message-ID: | imnki7$u0f$1@dough.gmane.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Oliver Jowett wrote on 27.03.2011 16:15:
>> At the top of my list is the need to use a cursor to avoid
>> materializing the entire result set in heap during execution of an
>> execute method. Pulling data off the wire should be done in
>> ResultSet.next() method.
>
> Do you mean something beyond the batching you can do by setting a
> suitable fetchsize?
> Or do you mean you want to lift the restrictions on when that batching
> can actually be used?
> Or something else?
>
I agree with Dave here.
Having a default that prevent the entire result to be loaded into the client memory does make a lot of sense to me.
Regards
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2011-03-27 16:37:26 | Re: JDBC gripe list |
| Previous Message | Dave Cramer | 2011-03-27 15:14:38 | Re: JDBC gripe list |