| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | jennie browne <jiebe(at)hotmail(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Prepared Statement Memory Size |
| Date: | 2006-07-18 17:06:24 |
| Message-ID: | Pine.BSO.4.63.0607181205001.11227@leary2.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Tue, 18 Jul 2006, jennie browne wrote:
> We have a prepared statement example below:
>
> With no dynamic parameters populated during runtime it will return
> roughly 1million rows. During execution of the query the
> preparedStatment grows in size up to 80MB and beyond.
>
> We have the fetchSize set to 1000
> And autocommit set to false.
>
> And the following params set
>
> stmt =
> conn.prepareStatement(query,ResultSet.TYPE_SCROLL_INSENSITIVE,ResultSet.CONCUR_READ_ONLY);
>
setFetchSize will only work with ResultSet.TYPE_FORWARD_ONLY. It has no
effect on scrollable ResultSets.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2006-07-18 17:25:16 | Re: Prepared Statement Memory Size |
| Previous Message | jennie browne | 2006-07-18 16:42:35 | Prepared Statement Memory Size |